this post was submitted on 29 Jun 2025
294 points (98.7% liked)

Fediverse

20451 readers
194 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
[email protected]
[email protected]
294
lemm.ee has shut down for good (sh.itjust.works)
submitted 2 days ago* (last edited 2 days ago) by [email protected] to c/[email protected]
70 comments fedilink hide all child comments
 

lemm.ee has shut down at 00:14 UTC.

unfortunately I realized too late that I have had hundreds of saved links to posts and comments from there, so I did not have enough time to save them, but anyways it is interesting that maybe a third of the post links I could try were dead. I think linkrot is happening much faster here than on reddit, even if just counting deleted posts.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 14 hours ago (1 children)

The reason I’m in lemmy.ml and not some smaller instance is because of problems like the ones showcased here.

Quite a few instances are managed by non-profits which are much less prone to service disruptions, like https://fedecan.ca/en/ for lemmy.ca.

The local account would continue being the primary source of access to the content…

Isn't that contradictory with the users - content separation?

note that having a separate hosting service doesn’t mean that the hosting service must be the one managing access to the content.

That seems contradictory with the previous point. My understanding was that

  • users would use Lemmy.user accounts to browse content (this is the recommended way to avoid user management for the content instance admins)
  • mods would use Lemmy.content accounts to moderate communities (users would have to switch to those type of accounts from the first type if they want to start / mod a community)

Is this correct, or am I missing something?

[–] [email protected] 1 points 14 hours ago* (last edited 14 hours ago) (2 children)

Then I think we had a different understanding. My understanding was something akin to what bluesky does with the PDS, the data service just hosts data and hands it over to the other service which is the one actually doing the indexing of that data and aggregating it into communities. The data of the community might be hosted in the hosting services, but it's accessed, indexed and aggregated through the authentication service.

The access management, the accounts, the distribution of data, etc. that's still in the server managing the federation. That's the way I understood it, at least (I'm not the person that originally started this train, that was @[email protected] ).

This allows the content to potentially not be completely lost if an instance dies because it would be easier to carry your data to another instance without losing it. It's the same principle as in bluesky but applied to the fediverse.

[–] [email protected] 1 points 13 hours ago

There's several solutions, I was just stating the "at least" solution because everything needed for it is already present. You just need to remove functionality depending on the type of service you want to host.

[–] [email protected] 2 points 14 hours ago

Ah, I see. So something like https://activitypods.org/ ?

That would be an improvement indeed, but probably not something we will see any time soon.