You broke your links while posting here
Natanael
joined 9 months ago
My native language doesn't have separate words for the two, we just specify "penna" (pen) or "bläckpenna" (ink pen)
T'was a joke
Currently Lemmy is leaking likes via the API even if they only should be available to the user's host and community host server
https://quoteinvestigator.com/2012/04/28/shorter-letter/
If I Had More Time, I Would Have Written a Shorter Letter
It will be even easier to carry the loot since you'll be dropping weight from your coin purse
The pens are also very consistent with each other, despite different angles. Probably Photoshop
I had an old laptop where graphics worked in the LiveCD installer but not once installed.
Tldr it took a bunch of bootloader config changes to make it work again
On Mastodon, your instance doesn't receive posts until somebody on your instance interacts with the account posting it (following the poster, browsing directly to the post, etc).
Feeds with recommendations requires fetching stuff in advance to not be slow and janky. Basically the feed service would need a bot account on your instance and retrieving all popular posts, given the current architecture. Having thousands of these bots across every instance do this would cause a significant performance hit on smaller Mastodon instances when one of their users posts something popular. So you need something different, like a server plugin where the bot fetches the content once and tells all participating Mastodon servers about their cached copy, so they don't all have to hit the hosting instance. But that's a security risk with the Mastodon design.
Doing it this way is why small instances gets hammered when a user's post goes viral.
And as for moderation bluesky also carries information with the top post from the post author and allows hiding replies too, etc. This gets enforced on the appview side, so the posting user's PDS is unscathed if it goes viral.
Bluesky is built to assume a handful of big relay (remember that a relay can merge in contents of another) and a bunch of appview and a ton of PDS servers, feed generators, moderation labelers, etc.
Realistically, the relay network will likely end up voluntarily adopting a tree topology - hobbyist communities would run small relays bundling all activity from members' PDS servers, then a larger relay in front gathers everything from a ton of smaller relays and makes it available to appviews
Zeppelin.social is 3rd party appview and you can host your own
https://whtwnd.com/bnewbold.net/3lo7a2a4qxg2l
A Full-Network Relay for $34 a Month
Add using DID:Web and you're now fully self hosted
https://en.wikipedia.org/wiki/Gettier_problem
Unjustified true belief