• 1 Post
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle



  • That would still create a fragmented comment situation. Ideally, the server should be aware of “sister communities”, so it could merge the comment threads, or at least tell the client to do so. But that has all kinds of moderation implications, as noted elsewhere.

    In the end you’re either doing federation on community level (which would require another level of federation administration - you can’t just merge like-named communities from Any instance), or you’d have to convince 1 community to go read only and refer to the “defacto” community.

    The first one has a lot of technical hurdles (servers and clients would have to adapt, and then community admins would be responsible for deciding who to federate their communities with). The second depends on mods giving up their community, which is unlikely and undesirable in case of defederation. Or option 3: keep the status quo, of course.
















  • Generally speaking, lemmy is much more cpu bound than it is bound by bandwidth - so the added bytes don’t matter that much. The example above was just for 1 community. Now imagine the user is subscribed to a dozen communities, but doesn’t even browse lemmy that day. That’s probably thousands of api calls made to keep his server on sync, and 0 requests saved.

    Like the big instances have literally hundreds of thousands of workers running in order to get all the updates out. If one of those calls fails, it gets put back into the queue for retry.

    OP asked if having his server added to the lemmiverse would alleviate the load “Like with torrent”. That is demonstrably not the case - it only adds more workload on the other servers, with a break even point that’s highly variable. Yes, your server will be nice and snappy, but the origin servers have to pay the price - death by a thousand papercuts synchronisation calls.


  • So you need just 15 more users on your instance to break even, if you have 17 in total, you’ve saved 10 calls.

    In this particular example, yes. But only if those 15 people subscribe to the exact same communities. If they don’t, the calculation gets even more complicated.

    I’m not sure why exactly you’re opposed to federation when that’s one of the biggest points of fediverse.

    Some people seem to be under the impression that setting up their own personal server is relieving the pressure on the network. What I trying to get across is that’s not the case, unless it’s being used by a reasonable amount of people.

    I can’t tell you what the sweet spot is - but my guess would be that it’s only going to be at least several dozen, more if their interests (subscriptions) don’t overlap very well.