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 instantly.
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.
At the moment this looks more like NerdNet than IndieWeb.
TheOtherHobbes
Really cool!
Have you checked out Nostr as well? I prefer the mental model of Nostr, it seems to be more in line with POSSE than Mastodon and the AT protocol.
rjakobsson
Good work! Both the explainer and the implementation! I'm using indiekit which basically comes with IndieWeb batteries included! https://rmendes.net and I'm working to get it implemented on https://textcaster.app
rmdes
This intrigued me a lot! I have been searching for a way to break out of the social silos, but all the other alternatives just weren't doing it for me. They usually chased thr nostalgia of the 90s for nostalgia's sake, but apart from making me nostalgic for 10 minutes I haven't found much use of them.
This seems different. It embraces the modern web and tries to fit in, while still giving the creator full control over their yard.
I might be overly optimistic, but I'm excited for this! I will try to make my myzopotamia.dev blog join the IndieWeb as soon as I find some time
myzek
I feel like the DRY concern with RSS feeds is overstated. I can’t remember the last time I had trouble with automagically generating an RSS feed using whatever open source framework I was authoring with at the time.
ronbenton
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.
pibaker
Great writeup, and welcome aboard!
A few things I would add:
- Make it a habit to share other blogs that you love. The IndieWeb relies on word of mouth and human curation. I love "what I enjoyed this month" posts.
- Be lavish in your praise and hearty in your approval. Email your appreciation, initiate conversations. Static sites without user tracking can feel like talking to yourself at times. Reader mail feels awesome.
- Have fun! Personal sites should be personal. Allow yourself to be incomplete, to be whimsical.
- Digital gardens are great. Not everything needs to be a chronological feed. This is your space. Arrange it as you please.
nicbou
Although not explicitly part of the indieweb protocols, RSS and Atom feeds are important too.
superkuh
Were you aware that the .dev domain name belongs to Google?
inigyou
I've done, and still do, regular blogging. I have a domain, and everything I post is mine. However it can't be "indieweb" because I used Wordpress. Hence my current blog is dependent on a corporation, as were a couple of older ones that were built in Blogger (and still exist, last updated nearly a decade ago).
That dependency is because isn't feasible for me to own my own server. If I did, it would either be virtual, in amazon's or microsoft's cloud, or it would be real hardware but still in some corporate server farm. It just wouldn't be practical for me to own (and maintain) a physical server with an UPS and permanent uplink to the net.
comments (10)
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 instantly.
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.
At the moment this looks more like NerdNet than IndieWeb.
TheOtherHobbes
rjakobsson
rmdes
This seems different. It embraces the modern web and tries to fit in, while still giving the creator full control over their yard.
I might be overly optimistic, but I'm excited for this! I will try to make my myzopotamia.dev blog join the IndieWeb as soon as I find some time
myzek
ronbenton
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.
pibaker
A few things I would add:
- Make it a habit to share other blogs that you love. The IndieWeb relies on word of mouth and human curation. I love "what I enjoyed this month" posts.
- Be lavish in your praise and hearty in your approval. Email your appreciation, initiate conversations. Static sites without user tracking can feel like talking to yourself at times. Reader mail feels awesome.
- Have fun! Personal sites should be personal. Allow yourself to be incomplete, to be whimsical.
- Digital gardens are great. Not everything needs to be a chronological feed. This is your space. Arrange it as you please.
nicbou
superkuh
inigyou
That dependency is because isn't feasible for me to own my own server. If I did, it would either be virtual, in amazon's or microsoft's cloud, or it would be real hardware but still in some corporate server farm. It just wouldn't be practical for me to own (and maintain) a physical server with an UPS and permanent uplink to the net.
fernly