deejay4am

These men are soyjacks, Donny

I also notice that the job you apply for seems to be a different value than what is displayed on the page. Seems like the documentation needs updating as well 😔

Some say he’s still searching to this day…

It would have been funnier if you put in “\e;D5c1-7” or whatever the fuck VT-100 gobbledegook

IT guys

posts SDI bank from a studio or broadcast truck

Memmy doesn’t do well with it either.

Of course it doesn’t bode well for the instance itself that it’s throwing so many…but it’s unclear if that’s an operator problem or a code base problem.

Iterative at best

Also this post from GitHub explaining why this entire premise is wrong:

Great presentation and write up - but this is just not how any of this works. The whole thing is based on a premise that just isn’t true.

Reposting my reply from lemmy:

The way federation actually works:

A user on lemmy.ml subscribes to a community on lemmy.world. Say, !funny@lemmy.world

Assume that this user is the first lemmy.ml user to do so - basically what happens is the lemmy.world community sees that a member of a never before seen instance just subscribed. !funny@lemmy.world then adds lemmy.ml to its list of instances it needs to tell whenever something happens in the community.

No matter how many users of lemmy.ml subscribe, this only happens once.

Now when a user of sh.itjust.works upvotes a post on !funny@lemmy.world, the sh.itjust.works instance then tells !funny@lemmy.world of this change. It accepts the change, then tells everyone on its list of instances that have subscribers on them.

So essentially, sh.itjust.works talks to lemmy.world, lemmy.world tells everyone else. There is no “full mesh”. The instance hosting the community is the “hub”, everything else is a spoke.

So if there’s 10,000 instances, and they all just so happen to have at least one subscriber to some community, each change will be sent out 9,999 times. Your “50 million” premise is just completely wrong and I’m not sure where it’s coming from.