Live data from Hacker News

I joined the IndieWeb, here's what I learned

en.andros.dev

61–70 of 167 posts

Re: I joined the IndieWeb, here's what I learned

#61
post #51
post #44

Earlier quoted context omitted.

Indieweb is sometimes tied to self-hosting to give people configurabilty and flexibilty. It does keep indieweb for the few and not the many.

Rather than self-hosting, IndieWeb advocate for managing hosting; like GitHub Pages or similar.

ask street-bbq vendor or cleaning-lady or uber-driver what is a "GitHub"

Re: I joined the IndieWeb, here's what I learned

#62
post #51
post #44

Earlier quoted context omitted.

Indieweb is sometimes tied to self-hosting to give people configurabilty and flexibilty. It does keep indieweb for the few and not the many.

Rather than self-hosting, IndieWeb advocate for managing hosting; like GitHub Pages or similar.

GitHub Pages requires subscriptions for private repos.

use Cloudflare.

Re: I joined the IndieWeb, here's what I learned

#63
post #53
post #49

I also have my own personal homepage [1]. The content isn't that great, but I do have some curated content on there. What kind of topics and people are usually involved in the IndieWeb community? I'm thinking about joining, but I'm still debating it. [1] https://www.makonea.com/en-US

I like your website design! Next.js, React, TailwindCSS in Vercel? Is this your design? It's very nice. They have monthly and annual events; perhaps you can discover them for yourself! However, I recommend that you first understand and apply some of their philosophy!

Exactly! It's Next.js 16 + React 18. I'm using the App Router, the frontend is on Vercel, and DNS/CDN/WAF are on Cloudflare. The style is neo-brutalist, but since it wasn't well-received in Korea, I softened it into a custom UI.

The animation is the Gooey Navigation I designed myself. I'm glad you like the design.

Re: I joined the IndieWeb, here's what I learned

#65
I feel some uneasiness when I go to a website branded as "indieweb," and see a link to the author's CV prominently on the page. Sometimes you also see a professional taken headshot of the author or an enthusiastic description of his work history at prestigious institutions. And it's always a professionally made blog. You know the drill.

It feels like walking into a brightly lit clothing store in a fancy mall and seeing the anarchy symbol on all items. Look closer and you'll see an almost four digit price tag.

Re: I joined the IndieWeb, here's what I learned

#66

If IndieWeb wants content, burying it under a ton of tech soup is the exact opposite of what they claim they want. How do the developers not realise that this set of protocols is completely unworkable for 90% of users? Please stop developing systems where the engineering is front and centre. If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running inst…

They realize it's "unworkable for 90% of users" and they don't care. Part of the Indieweb philosophy, like Libre software, is to "scratch your own itch" - no one's paying you. You do the stuff that's interesting to you. It's not a business. The point is not to take over the market. The planet needs fewer marketing pinheads, not more. I would like it if we passed various laws that killed off a lot of the marketing pin…

>They realize it's "unworkable for 90% of users" and they don't care.

No, you don't understand, it's bad because it does not provide ""value""

Re: I joined the IndieWeb, here's what I learned

#67

If IndieWeb wants content, burying it under a ton of tech soup is the exact opposite of what they claim they want. How do the developers not realise that this set of protocols is completely unworkable for 90% of users? Please stop developing systems where the engineering is front and centre. If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running inst…

>If you users have to go anywhere near a command line, or Docker, or they have to hand-edit HTML or CSS, you're creating walls most users aren't going to scale.

>If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running instantly.

You clearly don't understand the IndieWeb movement, which consists of amateurs and professionals who are motivated to go the extra mile and learn this stuff. The reason the Internet is the way it is in 2026 is precisely because we’ve eliminated all friction and have cultivated the dumbest possible user.

Re: I joined the IndieWeb, here's what I learned

#68
post #65

I feel some uneasiness when I go to a website branded as "indieweb," and see a link to the author's CV prominently on the page. Sometimes you also see a professional taken headshot of the author or an enthusiastic description of his work history at prestigious institutions. And it's always a professionally made blog. You know the drill. It feels like walking into a brightly lit clothing store in a fancy mall and seei…

A CV on your personal domain is the most IndieWeb thing you can do, it means your professional identity lives under your control, not LinkedIn's. The "anarchy symbol on expensive clothes" critique works when someone claims to reject the system while feeding it. IndieWeb does not claim to reject professionalism, it claims that your content should belong to you and outlive any platform. The headshot, the CV, the polished blog... those are fine. Locking them inside a silo that can shut down, sell your data, or vanish is the thing being criticized.

Re: I joined the IndieWeb, here's what I learned

#69
post #51

Earlier quoted context omitted.

Rather than self-hosting, IndieWeb advocate for managing hosting; like GitHub Pages or similar.

ask street-bbq vendor or cleaning-lady or uber-driver what is a "GitHub"

If you can learn to make a hamburger, with or without AI, they can learn to manage their site.

Re: I joined the IndieWeb, here's what I learned

#70

If IndieWeb wants content, burying it under a ton of tech soup is the exact opposite of what they claim they want. How do the developers not realise that this set of protocols is completely unworkable for 90% of users? Please stop developing systems where the engineering is front and centre. If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running inst…

> If you users have to go anywhere near a command line, or Docker, or they have to hand-edit HTML or CSS, you're creating walls most users aren't going to scale.

Oh, no?

Post reply on HN