Different experiences I suppose. Used Contabo to host an ansible setup of Lemmy, never had a single outage for 6 months.
Different experiences I suppose. Used Contabo to host an ansible setup of Lemmy, never had a single outage for 6 months.
I don’t find this any more dramatic than sh.itjust.works blocking lemmygrad.ml lol
This is correct, I can find old posts from an account I deleted ages ago from an instance that doesn’t exist still floating around those we federated with.
Lemmy is created by what many describes as “tankies”, fundamentalist communists. The lead devs are, in my impression generally supportive of the Chinese government. They run their own instances, dedicated to their own world view and interests. I don’t have the slightest problem with that.
Hopefully due to a lack of foresight their instance was presented as a flagship instance on the official landing page and other places, effectively making it the representative for Lemmy for a long time. With their moderation practices, they in large parts drove away what I consider reasonable users regardless of personal ideology.
This created an monolithic instance that dwarfed every single instance besides one; the other dev-run instance which seems like a containment instance for those too fundamentalist to stay on the “main” server. For a large part Lemmy was a downright nasty monoculture that would harass even lead developers for daring to interact with code-contributing users on instances deemed “problematic”.
With a very generous blocking practice, these monolithic instance basically shut out anybody not agreeing with them from the majority of content - including non-political. This in turn gave other instances less of a reason reason to stay on the Lemmyverse which reinforced the monoculture.
The devs did take steps to rectify this problem: they offered a year of free Lemmy hosting for anybody willing to admin a general purpose instance, recruited other general purpose instances to promote on join-lemmy.org. I respect that. But at that time it seemed too late to change the direction. When I realized the bad reputation Lemmy as a project had amongst some of the larger fediverse influencers, I realized that Lemmy would not be viable until it got a massive and sudden influx of new users to shake up the overall federated lemmy community. And now here we are!
Mastodon caches images from remote instances, Lemmy doesn’t. It links, which has it’s own issues (images disappearing from remote posts if the instance goes down). Everybody I’ve seen complaining about storage space have been open Lemmy instances with loads of users potentially uploading images to the pictrs sub-system. There’s even been requests to limit image storage for individual users.
If you’re thinking of using the YunoHost version of Lemmy, be aware that the pictrs subsystem is removed due to technical issues, I would absolutely recommend using the ansible install. But that might defeat the purpose of easy self-hosting for most YunoHost users…
From a non-technical aspect, the biggest issue (or at least used to be) on Lemmy was the ideological attacks and isolation by the fascist core community of any non-conforming instance. That had a chokehold on the lemmyverse to the point I saw no point running a Lemmy instance unless I self-censored my sometimes negative opinions of the Chinese government. Seeing the core developers being willing to hold back their own project was the biggest surprise when self-hosting Lemmy.
My RISV-V server (I have removed all binary blobs and have no closed source code ofc) is airgapped inside a Faraday cage.
For security reasons I never turn it on.
Smaller lemmy instances runs great on a raspberry pi 3 I’ve heard.