It increases load during execution. Afterward it’s not significant. My instance is heavily instrumented and monitored. The load this incurs subscribing to 24000 communities is less than adding a single, moderately active user to your instance.
It’s a huge miss if the intended design was to silo information.
What this provides, as far as I’m concerned, is essential to prevent centralization to a few instances.
Is there a better way to do it inherently in Lemmy itself? Probably, and I am excited to help with that!
UPDATED: lemmony: A (better) better "All" browsing experience for small and large Lemmy instances
v0.0.4 - Per requests and concerns: Defaults changed and options added to prevent overloading servers, hitting rate-limiting, filtering to top x communities, etc! Thanks for your support!
lemmony: A better "All" browsing experience for small Lemmy instances
I made this tool to help self-hosters, new admins, or smaller instances have more global and updated content on their instances. This is the similar to Lemmy Community Seeder [https://github.com/Fmstrat/lcs] but is designed to be run periodically to capture new communities, and include EVERYTHING by default.
Global magazine aggregator?
Federation Lag-o-meter
Netflix got rid of the $9.99 basic plan in Canada
cross-posted from: https://beehaw.org/post/764388 [https://beehaw.org/post/764388] > It’s like they are trying to irritate people into canceling their accounts. > > Imo, this one might actually be worse than the account sharing and cause people to quit. As soon as you have people messing around with their subscription version, it’s all too easy to just say “nah, I actually don’t want this anymore”.
