@Xavier@infosec.exchangeI found a neat website that helps confirm your bit torrent client config. You can add a magnet URL and the web page will show which IP the client connects from.
#bittorrent #torrent #evilvibes
https://trak.evilvibes.com
@Xavier@infosec.exchangeI found a neat website that helps confirm your bit torrent client config. You can add a magnet URL and the web page will show which IP the client connects from.
#bittorrent #torrent #evilvibes
https://trak.evilvibes.com
@risottobias@tech.lgbtyou have a P2P swarm of torrent-like peers.
they're not all online at the same time.
how do you coordinate a schedule between peers,
such that it isn't abused by other parties to DOS the seed / so that superseeders are coordinated?
kinda like the cicada cycles?
best I can figure is leaving a message at a mutual friend, encrypted saying "change of plans, my node will be online at UTC xyz", if they don't meet up at the other date.
#p2p #torrent #decentralization #redecentralize
@tezoatlipoca@mas.to @tezoatlipoca@mas.to
@sergiofdezsaez@masto.es @risottobias@tech.lgbtthere's gotta be like, google level papers on different efficiencies for peer to peer exchange of like, small messages (think mastodon statuses), vs large static files (pixelfed), vs streamed content (#webtorrent / #peertube), vs append-only graphs (#radicle/#forgejo)
like some parts of it would be small updates that you could imagine a #gossipprotocols would handle, vs bona-fide #torrent stuff, vs things where they want an authoritative root (kinda like a #TUF root or the ubuntu signature / package lists vs mirrors) vs anycast ice buffers
or for like, how to mirror to super-seeders and then have them as introduction points for the content
