105
[Instance] Kbin.run down
(sopuli.xyz)
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
Not only did he deleted the domain (records) and his github account. But also I can't find his sponsor pages anymore on buymeacoffee.com or patreon. Meaning he removed everything.
Yeah, I was a member (the only one?) on patreon and all evidence of my membership has vanished. I'm starting to think that self-hosting might be the only real way forward for stability, but I don't know how to replicate the /all/ experience without a swarm of users and their subscriptions adding to my own.
I would not recommend single user instances in the threadiverse, they just need too many resources just to start out... There are other options available and if you do not trust the people "only" running their servers for 2 years like me and debojnced previously then go to fedia.io their admin has been actively hosting fediverse services for a lot longer
What is your definition of "too many resources"? Because running a Lemmy instance surely takes less server power than something like Mastodon, and you can find managed providers for Lemmy for ~$10/month.
Hell you can self host using yunohost of you want, although its an old version.
Used fedia today, and it looks like they never quite nailed down their 504 problem, so I think I'll give this one a go for a while.
It's showing indeed the limitations of the activitypub protocol. I'm promoting decentralization, so feel free to run your own instance. Just know that it will take some time, effort and most likely some money.
Happily, the costs (server/hypervisor, domain, static IPs, proper firewall) are ones I already needed to spend for work, so the only tricky part will be finding the time and making the effort. Maybe by then the ux issues with low population instances will be sorted lmao.