Live data from Hacker News

I joined the IndieWeb, here's what I learned

en.andros.dev

11–20 of 167 posts

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

#11
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.

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

#12
post #11

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 awes…

I really like your comments! I'll include them when I have some time. Thank you so much!

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

#14
> “Use what you make: use what you build every day. ‘If you aren't depending on it, why should anybody else?’”

Having difficulty imagining this constraint.

For example, I use my iPhone’s Note app daily for personal notes. I don’t currently host a site, but if I did I might have content/write on no more than monthly cadence, or per-project.

Does this rule suggest that I should ‘publish’ more (ie. elevate private note content to public more frequently) or build something for my private notes to be hosted on my server? Or something else?

In the first instance we’re talking about that micro commentary you get with social media sites. Becomes something like Kottke’s site. A feed of interesting things.

In the second instance you’re using your server infrastructure more, and so it’s not a machine you interact with only infrequently.

Or am I totally missing the point?

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

#16

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.

I prefer Org Social a million times over Nostr :) https://en.andros.dev/blog/8c640241/why-org-social-when-you-...

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

#17
post #16

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.

I prefer Org Social a million times over Nostr :) https://en.andros.dev/blog/8c640241/why-org-social-when-you-...

Interesting, will check out!

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

#18

> “Use what you make: use what you build every day. ‘If you aren't depending on it, why should anybody else?’” Having difficulty imagining this constraint. For example, I use my iPhone’s Note app daily for personal notes. I don’t currently host a site, but if I did I might have content/write on no more than monthly cadence, or per-project. Does this rule suggest that I should ‘publish’ more (ie. elevate private note…

Today it's quite easy to keep your private notes on your infrastructure, manage them with your iPhone, and even store them in plain text: Joplin, Syncthing, WebDAV (https://en.andros.dev/blog/9abcdcfe/your-denote-notes-on-the...)...

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

#20
post #9
post #8

Were you aware that the .dev domain name belongs to Google?

Yes, I knew that. I would have liked to obtain my personal top-level domain, but it seems complicated to me.

It's not possible. But there are more and less neutral ones.
Post reply on HN