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.
yeah but it turns out a lot of my lemm.ee links are not actually to content that’s originating from there, but lemm.ee-view links for which if I search, there’s no result.
Fortunately I also have the title and image permanently loaded for these links, so I can find them with some manual work
A solution to this is Nostr. One identity across the entire network.
Twitter-like Platform/client dies overnight? No problem, all data still there.
Reddit-like platform/client dies overnight? No problem, all data still there.
PC dies overnight? No problem, all data still there.
Data is sync’d across multiple relays, you can run your own, and clients are interoperable.
It’s my go-to now, for everything. A person’s posts, their followers/audience, chats, etc never needs to be migrated.
Media is stored using the Blossom protocol which was created for Nostr.
V4V(Value 4 Value) is also a thing, so instead of just Likes/Reactions you can tip/Zap Sats (Bitcoin over Lightning) but that’s optional.
Centralised identity is something that Nostr does right. But it’s got a nazi bar problem
It’s not centralised though. It’s quite decentralised actually.
As for your “nazi bar problem”, I’d suggest you review the relays you connect to. That’s the beauty of free speech, and power of choice.
Damn, since I saw the warning thread I was hurrying my slow ass to back up my stuff, which I gladly did (some days ago), lemmy.zip is my new home now.
I feel sorry for the users that didn’t get the chance to backup their stuff… An auto backup feature for Lemmy backend might be worth checking out perhaps?
At the very least, social networks like this really need a two server type system: the authenticator who identifies that you are really who you say you are and handles personal settings, communication, and access to the fediverse, and the content provider that hosts the communities.
How do you ban users in this scenario?
What do you mean? The authenticator instance could ban users, the moderators and the content provider instances could ban users, content provider instances could defederate from authenticator instances and viceversa.
Not sure I’m seeing the issue you are seeing, it’s just basically forcing lemmy instances to instead of being both to just be one or the other. The benefit is that the actions on one is free from the drama on the other. One would be dedicated to hosting users, the other would be dedicated to hosting communities, less burnout overall.
Complete bans (at the home instance level) would require synchronization between the content provider instance and the authenticator instance.
Mod actions are caused by users comments on content, so the two aspects are closely intertwined, you can’t dissociate the content from the users.
At the moment, admins synchronize in a group to deal with toxic users, usually leading to the ban of those users on their home instance. Having a split between two types of admins adds an additional layer that could actually increase the admins workload.
Since he said that the authenticator is the one that handles the communication & access, I expect banning the person from the authenticator would already automatically prevent anyone using that authenticator (or any other authenticator federating with it) from seeing the content.
As I understand it, the only thing the content provider would do is hosting the data. But access to that data would be determined by the service doing the access control, in the same way current instances are doing it.
the only thing the content provider would do is hosting
Hosting involves removal of content, which is triggered by actions performed by users.
At the moment, if a Lemmy.world user spams CSAM content everywhere, other admins can reach out to the LW admins, they ban the users and purge the content.
In a users/content model, with Lemmy.users and Lemmy.world still being the content, other admins have to reach out to the Lemmy.users instance, get them banned, then to the Lemmy.world admins to trigger the purge of the content on the communities.
On top of that, it is currently recommended to mod from local accounts, as report federation will be fixed in Lemmy 1.0, not released yet: https://github.com/LemmyNet/lemmy/issues/3781
The main part of the “admin burnout” comes from the management of users. There isn’t really that much to manage on the content part that isn’t linked to users.
Hosting involves removal of content
Exactly. That means instances would not longer have that responsibility. That would be on the hosting service, meaning less pressure for the instance. Once they ban the user, the content would not be shown, it would be purged from the federating network of that instance, regardless of whether the hosting service actually deletes it or not (but I expect it would be better if the protocol makes it so banning a user sends a notification to the hosting service).
At the moment, if a Lemmy.world user spams CSAM content everywhere, other admins can reach out to the LW admins, they ban the users and purge the content.
It’s more complex than that, at the moment, because the purge also involves mirrored content in other federating instances. The interesting part is that after it’s triggered, then the process is pretty much automatic. When purging, Lemmy.world admins don’t have to manually go around asking to all the other instances to delete the content. The purge request is currently being notified automatically to instances federating with it. Why would it be any different for a content hosting service?
It’ll be greatly missed. It was nice to have an instance with a reasonable defederation policy where I could interact with anyone basically.
Nice for you, bad for the mods. Only way to do that without outsourcing mental strain to other people is to self host
Yeah I remember I few people saying modding .ee was hell because of infinite streams of users from the same instances and their refusal to defederate
🫡 you were good to us .ee, may you forever rest in peace.
Goodbye ee
You were waiting for this one for a month, aren’t you? :)
It was my first home. I thank them for bringing me in.
Deleting your account deletes your content, unlike deleting your Reddit account. Hence the linkrot.
I learnt pretty early on that saving posts using the save button was not a good way to save the information 😮💨
Not quite. If your comments federated out to an instance that either a) doesn’t get the delete request or b) ignores the delete request, your comments will very much stay out there in the fedeverse with not much you can do. Yes posts on the original instance may be gone, but anything that get pushed out via ActivityPub is a crap shoot.
Yes with ActivityPub there’s always failed federation. But Lemmy will send the delete request out when you delete your account. Other software or instances might not honour it, but the intent is there.
As opposed to reddit who do not remove comments when an account is deleted, only mark it as a comment from a deleted account.
I’m not against Lemmy’s implementation, but it does require you to collect information you need at the time not assume it will always be there.
Ah, I get where you’re going with that and understand your view. My point was more for users who think that deleting an account will really get rid of it everywhere and I didn’t want them getting their hopes up.
That’s weird. I moved over from lemm.ee and transferred data. The saved posts transferred too.
No that’s expected, as part of your profile info. But if the original authors delete the comments, then they will also be deleted in your saved items.
Ah got it!
Yeah bookmarks are a lot better than using specific save systems
Bookmarks won’t help if the content gets removed. You’ve got to copy the important information elsewhere.
I tend to use either a note app (Joplin) or a self-hosted wiki for that.
Yeah fair, most of my bookmarks aren’t really things that are important to save, just funny things I want to share later or something.
I always take a screenshot because I am lazy but just copying the text, like you say, is better
Hello world, lemmee refugee here, & first post on piefed! I had exported my settings before the ship went down, figured we could import it in another instance to save my comments and communities, but I don’t see any option to import here. Does piefed speak with Lemmy yet it’s not part of Lemmy?
Piefed speaks to Lemmy instances, yes.
You can import data here: https://piefed.social/user/settings/import_export
I’m sure I was sufficiently notified, but I am not big on reading updates on ny instace, so this came as a surpise just now.
Thanks for the server! Onwards to the next!
The original shut down thread was posted over 3 weeks ago.
RIP home server, you will be missed
I was literally filling out an application for another server when it went down. Sad day.
Unfortunately I waited too long and now I can’t see my subs that I wanted to migrate.
this you? https://lemmy.zip/u/[email protected]
Yep thats me!
The linkrot is real but not unexpected when anyone cat spin up and shut down instances. Nothing is forever
It’s mostly not because of instance shutdown though. especially on lemmy, because lots of posts are readable elsewhere after shutdown.
Out of the loop, why did they shut down?
Not enough admins, and those there were burnt out.
Furthermore, I thought that they were supposed to be a temporary instance for the reddit influx as well.
