Thank you!

Please feel free! Source is on GitHub, it uses Astro with the Starlight template.

Thanks, this is lovely!

That’s a great way to attract stalkers.

Setting up a Lemmy server outside of the golden path of using the Ansible template is extremely difficult. I do this professionally and I couldn’t get federation working properly when running Lemmy on my Kubernetes instance.

Figuring out why federation is failing is very, very hard.

Lemmy requires a lot of resources to run. You need a VPS that’s at least $20/mo to work adequately under any load. Disk storage requirements for the DB are also rather high.

Lemmy 0.18.2 has some horrendous N+1 DB calls, e.g. one query per language (173 of them) when you create a new community. This hamstrings databases that are not colocated onto the same machine, e.g. neon.tech’s hosted pg db. I expect this will improve with time as the codebase matures, yet…

Instance administration tools are sorely lacking.

“It’s a good filter” is often just an excuse to not improve the UX. You hear this way more from open-source technically-inclined folks than you do from folks who care about building a product that people want to use.

And there’s not a great way to suggest “you might like…” based on your current subscriptions.

Email has the benefit of legacy. Lemmy does not.

I tried to solve this a tiny little bit by giving my own instance a clean and friendly frontpage, but I think I still need to do more work to attract people who aren’t fedi-inclined.

Links between instances often don’t work as intended, and there’s no good way to redirect me from some-other-instance.pub/c/cool-community to my-instance.pub/c/cool-community@some-other-instance.pub automatically.

Maybe you should take what she says seriously.

The camera technology advances significantly every year, so it really matters if you’re a photographer.

Beware of your phone going out of support and losing security updates. Android manufacturers tend to drop devices after 2-4 years, Apple after 4-5.