Selfhosted

60366 readers

558 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

211

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

submitted 3 years ago* (last edited 3 years ago) by hawkwind@lemmy.management to c/selfhosted@lemmy.world

72 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] floofloof@lemmy.ca 8 points 3 years ago* (last edited 3 years ago) (1 children)

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.

[–] hawkwind@lemmy.management -1 points 3 years ago (2 children)

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!

[–] wintermute@feddit.de 7 points 3 years ago

It is a significant difference if an instance has to federate literally every post made on the lemmyverse.

[–] floofloof@lemmy.ca 2 points 3 years ago (1 children)

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.

[–] hawkwind@lemmy.management 2 points 3 years ago

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.