Tootfinder

Opt-in global Mastodon full text search. Join the index!

@beaware@social.beaware.live
2024-02-23 02:02:22

Because people can't click a link and read it that way apparently, I'll post images from the Fediverse wiki page here that supports my claim that AP is the Fediverse. If anyone has anything else to say that isn't covered in these images, I'm willilng to entertain it.
But don't come into my replies saying "AP isn't the only protocol that's a part of the Fediverse" because I'm literally covering that right here, right now.
Sorry, I'm an…

A screenshot of the Fediverse wiki page that says "The fediverse (a portmanteau of "federation" and "universe") is an ensemble of social networks which can communicate with each other, while remaining independent platforms. Users on different social networks and websites can send and receive updates from others across the network.

ActivityPub, a W3C standard, is the most widely used protocol that powers the fediverse. Noted fediverse platforms include Mastodon, Lemmy, PeerTube, and Pixelfed.

…
A screenshot from the Fediverse wiki page that says "The term fediverse was first used to describe the network formed by software using the OStatus protocol, such as GNU Social, Mastodon, and Friendica.[1]

In January 2018, the W3C presented the ActivityPub protocol, aiming to improve the interoperability between different software packages run on a wide network of servers. By 2019, a majority of software that was previously using OStatus had switched to ActivityPub,[2] and the term "fediverse"…
A screenshot from the Fediverse wiki page that says "Other Protocols
Other similar protocols include Bluesky's AT Protocol, Nostr and Farcaster.[3]"
A screenshot of the Fediverse wiki page that says "Gossip. Certain social networks, including Threads[4] and Tumblr, have expressed interest in adding fediverse-compatibility.[5]"
@arXiv_csDC_bot@mastoxiv.page
2024-02-27 08:19:57

This arxiv.org/abs/2305.13385 has been replaced.
initial toot: mastoxiv.page/@arXiv_csDC_…

@risottobias@tech.lgbt
2024-02-18 08:00:49

wait... wait...
IDEA
<.< >.>
okay, so on device cookies you'd need to share a lockout list ({user_uuid, cookie(optional), failure_time})
(optimally you'd share/compute a list of temporarily limited users and IPs and their expiries)
If you had multiple nodes and wanted to cluster JUST this information...
you could probably make a really really simple gossip protocol or fireflies protocol.
like an optimistic "the other nodes will let me know list entries so I can add them" kind of hint.
(this does make me want to replicate the rest of the dumb SQLite tables between unikernel nodes but... bleh that's more stateful / actually DB things) owasp.org/www-community/Slow_D