Knowledge
A good explanation of how the protocolworks.
Research
- host local servers, one tracking each service
- connect to these servers with a locally hosted mastodon client
each server takes account information and mocks external accounts:
- logs in through social media api
- view posts, corresponding threads/comments sections
- server publishes data form these services in real time to mastodon
- server creates/tracks fake mastodon user from every other user
- these users are visible with clever naming scheme and tolerated byserver
- interacting with these real servers from ur acct (must be hostedin same place) == ur account on that social media interacting withtheir real acct
- likes, follows etc. also emulated – though have to check ifcurrent user is following them, has liked, has followed etc.
- should port over images, videos, gifs etc from whateverproprietary twitter thing they use to sane default formats todisplay on mastodon (i guess these should be cached for some timeperiod, then…)
Federated social media is thefuture.
P2P
Assessment of the feasibility of p2pactivitypub want toavoid static ip, ideally
- run on home server, always-on computer kind of deal ie beaglebone
- NAT TOR? Zooko's triangle – choosing between human readable,decentralized and unique is impossible. PetNames proposal may beuseful
- key upgrade, but all that is needed is tor .onion address support,truly
https://activitypub.rocks/: explanation of the activity pub prococol;how it works. Rotonde: coolidea for a distributed social network