1y ago

UPDATED: lemmony: A (better) better "All" browsing experience for small and large Lemmy instances

github.com GitHub - jheidecker/lemmony: A better "All" browsing experience for small Lemmy instances

A better "All" browsing experience for small Lemmy instances - GitHub - jheidecker/lemmony: A better "All" browsing experience for small Lemmy instances

v.0.0.6

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!

Selfhosted @lemmy.world

lemmony: A better "All" browsing experience for small Lemmy instances

github.com /jheidecker/lemmony

59 26

Fediverse @lemmy.world

lemmony: A better "All" browsing experience for small Lemmy instances

github.com /jheidecker/lemmony

91 44

You're viewing a single thread.

72 comments

The script gets all of the publicly federated communities and "makes them known" to your local instance and then subscribes to them. "All" should be populated with activity from around the Lemmyverse.
Doesn't that significantly increase the load on your instance and, if many instances use it, all instances? This system isn't designed with the idea that each instance receives everything from every other instance.
It might be better to run this on a single dedicated site which people can come to to browse. If you could learn where each user had their account, you could send their upvotes, downvotes and comments to that instance.
- 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!
  
  It is a significant difference if an instance has to federate literally every post made on the lemmyverse.
  
  Well that sounds quite reasonable then. It definitely answers a need for better discoverability of material on Lemmy. And it would be great if something like this could ultimately be integrated into Lemmy itself.
  
  I think your idea is on the right track when thinking longer term and assuming the worst case in both design and admin behavior. :)
  The whole network needs to be split into "active" and "archive." New activity (or at the very least stubs to where new activity is happening) needs to be updated regardless of where it occurs without having to capture anything extra.

72 comments