Skip Navigation

Posts
8
Comments
284
Joined
2 yr. ago

  • The weird rage people have about this. I'm not sure where it comes from. If there are 100 communities, only the top 1-5 will contribute 90% of the content. If you have even one user subscribed to the top 20 or 50 communities, you are already likely getting 90%+ of this traffic. After subscribing to literally every community in the lemmyverse, I promise your instance will not see any meaningful increase. I'm willing to be proven wrong, but not one of the ragers has offered a credible reason other than fears based on misunderstanding. No offense.

  • So just refreshing the page one time after login fixes it? It could be something to be fixed in the code, but there might be a way to fix it with a browser-side script in the meantime.

  • In Germany they pronounce it VasMan.

  • A handy chart: https://i.pinimg.com/originals/18/a4/2f/18a42ffa5c733c7c6bb86b547fb0647f.png

    It's a cruel irony that we use an enclosure to help print materials with a higher Tg but the printer itself is printed of materials with the same or lower Tg. It makes perfect sense that your ABS parts are going to get mushy when you crank your heated bed to 100 and put the whole thing in a box. :)

  • 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.

  • 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 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 doesn’t matter. Most of the work is happening on the instance, regardless of where the script is running.

  • We probably won't find out because a majority of the fediverse will not want facebook a part of it.

  • Thanks! I'm sure you'll chime in when the lemmyverse falls over because of this irresponsible script.

  • Your argument does not gain validity by adding irrelevant verbosity:

    Federation ain’t doing great.

    The linked issue has nothing to do with this script or lemmony.

    Federated replication load scales with the number of instances multiplied by the number of communities they subscribe to.

    That's a hasty generalization that you just made up.

    Server counts are growing at ~10x per month.

    That's great! I hope they keep growing!

    The defaults of this script encourage single-user instances admins to bump their sub count ~70x from something like 100 communities to something more like 7000 communities.

    Nobody is encouraging anyone to do anything.

    Users of this script actually literally don’t understand how federation works. They think they’re proxying through to the upstream instance while they browse rather than getting firehosed with the entire lemmyverse by they’re asleep.

    That single user asked a question and got berated by a jerk.

    It doesn’t take a rocket surgeon to figure out that global federation worker queues are not in great shape, or that a default that encourages single-user instance owners who have no idea what they’re doing to bump their sub count 70x isn’t helping the situation. If you think this is in my head I can’t help you. But I can help others understand that running this script with default settings is an awful and unnecessary idea.

    You can help others understand what it is. That's a great thing to do. It would be nice if you could do that without being a dick.

  • I don't really think so, but i'm open to working with anyone if they see this happening, up to deleting the entire project.

  • It retrieves the last 10 posts and adds the community reference to your local database. It is the same as putting "!community@instance.com" in the search box and clicking search. The retrieval happens whether you look at the results or not.

  • When I discovered, I felt bad for not checking. As for the load stuff. I intended and wanted to see All the things, and I don't currently have resource problems for my instance. :) We'll see how that fairs as things continue to grow!

  • My dude, I appreciate your spirit, but we're not going to focus on your irrational fear of abuse. I'll defend myself for being accused of any such thing, or for being irresponsible. This is intended to make things better, and there's no evidence it's doing anything other than that.

    If you want to contribute, by all means, show us where there is a problem, other than in your imagination, and it will be seriously considered. Until then, your opinion is still valuable, but you are speaking with authority about something you know little of.

  • So if I’m understanding this right, the bot account you create for this is the one subscribing to every community, so it’s known to the local system, right?

    Yes

    As long as I’m not mixing up my main account and my bot account, there should be no observable change on my own account?

    Correct, I have it functioning this way and it works great.

    How is storage affected on this? If the bot account is subscribing to a number of communities across the fediverse, all that remote content is going to take up quite a bit of space, no?

    It does and it will continue to grow. This not not something the tool takes care of, not cleaning up anything old or stale. Space management and "unfollow" is on the roadmap! Currently I can only speak for myself and it is EVERYTHING and it is about 0.25 GB / day of database, and 6-10 GB / day of images.

    And will 2FA be supported at any point?

    Not on the roadmap. I don't know how api calls in general work with 2fa since I have not tested or enabled it on my instance. :( Sorry.

    EDIT: Changed database/pictures ratio after double checking actual numbers and not looking at used filesystem. :(

  • Not really. If it worked before, it should work the same, just has more options for control and granularity.

  • I think it depends on your instance. This version (same script, just updated) allows for more options IF your instance IS mass Overloaded, or you are scared it will be.