First, these kinds of "issues" should be explained privately (as people normally do) and not publicly on Hacker News. For me, this already weakens your feedback considerably.
Second, the article is designed to be read from top to bottom.
Third, there are no hard and fast rules of good design. There's a spectrum of gray between black and white.
Fourth, thanks for your feedback. Even though it might not seem like it, I made a note of it a couple of days ago to reflect on it. But your persistence is discouraging me.
It's a false dichotomy; neither can survive in the long run. It's like asking yourself: would you prefer a car with a good engine but a bad steering wheel, or a car with good handling but a bad engine?
The mobile interaction is similar; it's not a bug, it's by design. If you were able to read the article without any problems, I'm satisfied. Thanks for the feedback.
I'm sorry, but I disagree. The lowest interaction cost is scrolling; it's a natural, continuous, and almost involuntary gesture. Having to click or tap a button requires the user to stop, evaluate whether the title interests them, and decide to make the effort to tap. The interactions you're describing are intentional and measured. I'm sorry but if the content is truly all you care about, I recommend the previous option or activating your browser's reading mode.
If you want to eliminate any friction, I recommend enabling JavaScript.
Otherwise, you can read it in terminal mode with: curl -H "Accept: text/markdown" [URL]
GUIs cannot be built either before or during the specification of a protocol. In fact, this is the part that should have the least weight. There are important steps, such as system auditing or making design decisions (like certificate rotation), that are not addressed. However, the goal is not to replace SMTP/IMAP, but rather to show how modern tools, when properly assembled, can replace older protocols with serious design flaws.
JMAP is flexible, mature, and easy to connect with current technologies. It's a better option.
I accept your apology; it must have been a misunderstanding.
I believe that in my case, the use of JavaScript is justified because it's information that doesn't require a separate page; there are just a couple of configuration buttons. On the other hand, the page is rendered using HTML over WebSockets, and what you're experiencing is the vanilla SEO version... hut of course, that's just my opinion.
If you don't want limitations, host your social.org site yourself, or move it to GitHub Pages or similar services. org-social-host is a free hosting service I offer openly to help you get started, but it's not unlimited.
Yes, there are people who want their own host (The IndieWeb or Gemini communities are a clear example). The problem is that convenience is always the priority; there are no incentives.
By the way, what you're saying isn't true. That link isn't present in either the HTML or the JS, the URL is sent via WebSockets. You had to open the modal to see it.
Thanks for the advice, but I intentionally removed `<link rel="alternate">`. I think if you take some time to explore the feed modal, you'll understand why I did it.
That's why I created a modal that explains the different RSS feeds for subscribing and their possibilities.
My blog is over a decade old, and I've never used advertising, had sponsored articles, or tried to monetize it (except for asking for donations to maintain the server). I've written freely, sharing knowledge, creating tutorials, and developing courses. Your comment makes me lose the motivation to keep doing it.
First, you're assuming my entire website should work without JavaScript. You don't understand my design reasoning, nor have you asked about the underlying cause.
Second, for a modal, I should use a `<dialog>` that opens via a `<button>`, which it already does. JavaScript does the magic. Not a `<a>` as you suggested.
Finally, if it's a bug, which I find very strange because it's a very simple piece of code and no one has reported it, you're not posting it in the right place. An email or the contact form would have been more appropriate.
Managing or owning your own server is already a way to decentralize the network.
You can always do it like in the old days and ask your friends to add your IP to your host file.
IndieWeb wasn't born as an anti-capitalist movement, but rather at a time when protocols were more prevalent than content. If you review its core principles, everything revolves around creating, sharing, and persevering over time. Companies aren't the enemy.