this post was submitted on 07 Jul 2023
209 points (96.9% liked)

Selfhosted

40359 readers
365 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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
[–] [email protected] -2 points 1 year 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!

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

Uhh... if your script is subbing to 24k remote communities, those will continue to grow from then on, unless you start purging communities at some point. After one user subscribes to a community, all new content gets indexed and stored on your instance. Pict-rs can cache images short term (and eventually clear them out), but Postgres will start growing very quickly and never slow down until it fills up disks.

[–] [email protected] -1 points 1 year ago

Yup. 256 GB should be enough database space for anyone though.

[–] [email protected] 3 points 1 year ago

Afterward it’s not significant.

Sorry, but unfortunately, it is, forcing a instance to sync literally every single post made on the lemmyverse.