#socialinbox — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #socialinbox, aggregated by home.social.
-
One of the neat innovations of the #DistributedPress #SocialInbox is that instead of having a large central instance database everyone pulls from for their clients, each user has a personal database of just the things they got sent. From there they can pull data from people they follow and replies using the ActivityPub client-server API. This means that the data you see has a higher social context to who you interact with rather than a grab bag of whatever folks throw onto the global timeline.
-
Suuuper rough sketch for anyone interested. Basically we'll have a list of accounts you follow in localStorage, then ingest their outboxes into this. Then we'll set up fully p2p identities and use the #DistributedPress #SocialInbox as another source to ingest stuff like followers only posts and replies from people you don't follow.
https://github.com/hyphacoop/reader.distributed.press/pull/3
-
Super excited that our new #ActivityPub implementation, the #DistributedPress #SocialInbox has got it's official announcement out! If you want to add #P2P or #Fediverse support to your existing site, do hit us up! :)
-
Cool thing in the #IPFS and #libp2p ecosystem is #IPNSLink https://ipnslink.com/
tl;dr: Run a server somewhere (like at home), generate a public key for it's identity. Users can access it from either the p2p network directly or any gateway that will automatically route to it.
No need for dns or messing with ip addresses.
I'm thinking it could be handy for #SocialInbox users that want to self host at home on their pc.
-
🤫 `npx distributed-press-social run` #DistributedPress #SocialInbox #ActivityPub
-
@em @teal What makes you say that they can't? I use signed fetches as auth for the #DistributedPress #SocialInbox and it's pretty straightforward. There's the issue of CORS headers not being availabke on a lot of instances tho.
-
Fun fact! You can now follow @[email protected] which is one of the first accounts using the #DistributedPress #ActivityPub #SocialInbox project.
We're finalizing our release so expect more info on how it works shortly!
For folks that don't want to mess with the technical details, keep wacth for @sutty which is integrating this functionality into their static site #CMS using Jekyll!
-
Anyone got an API endpoint of the "most blocked instances" handy? I wanna add it to the initialization flow for the #DistributedPress #SocialInbox
Ideally it'd be nice to say "Here's the top 100 most hated instances so you can preemptively block them if you'd like". It's not perfect but I think this would make it easier for small publishers to get started.
