Blaze (he/him)

  • 120 Posts
  • 1.43K Comments
Joined 2 years ago
cake
Cake day: August 9th, 2023

help-circle














  • lemm.ee told you the reason they were shutting down - not enough people to keep the place running and burnout. I can’t force you to see how minimizing and distributing responsibility helps those issues if you don’t want to. Less responsibility, easier for people not to ditch projects or end them.

    Lemm.ee had the option to close their registration at any time. But registrations are only one source of user management.

    In a scenario where Lemm.ee would have become a content instance, but kept their federation policy, they would still have received all the reports about posts on the communities they hosted, wherever the reported user comes from.

    Lemm.ee was the instance with the most active communities after LW, there’s no way to avoid a certain level of responsibility.





  • I addressed a few of your points in the parallel thread with @Ferk@lemmy.ml (actually, it seems like you read it as you commented below)

    As I stated in one of the comments

    At that point, the content instances would be merely storage. This model is already possible now, but the vast majority of instances host both users and content, because it is more interesting to have users to build a local community than just being a storage server.

    If some admins were interested in only being storage servers, you would see more instances not allowing user registrations, but all the 35th most active instances allow them: https://lemmy.fediverse.observer/list

    I had a second look, and instances not allowing sign up are either going to shutdown (lemmy.one) are false positives (https://bookwormstory.social/signup) or are single-person instances:

    Your vision is possible now, but it seems like almost no one wants to implement it.