Content
@
0 reply
20 recasts
20 reactions
boscolo.eth
@boscolo.eth
One thing I like about the Bluesky architecture that I would love to see Farcaster adopt is the concept of a PDS (Personal Data Server). This way every post I make is stored in a server I control with my keys (but not necessarily host). It would help move us toward this idea of Publish (on your) Own Site, Syndicate Elsewhere: https://news.ycombinator.com/item?id=29115696
4 replies
11 recasts
59 reactions
horsefacts
@horsefacts.eth
Farcaster had a very similar design before we introduced Hubs. The problem is that if you want to get the latest state of the network, someone needs to coordinate retrieving the latest updates from many different individual servers (which fail, go offline, slow down, etc.) Bluesky uses a central "relay" that watches all the PDS servers for updates and converts them to a single stream. Theoretically anyone can run a relay but in practice it's very expensive. So it's a different trade-off. We want everyone to have access to global state without a relay. IMO the design of FC pushes the tendency to centralize further out to the edges, into client like Warpcast instead of infra like the relay.
2 replies
0 recast
10 reactions
boscolo.eth
@boscolo.eth
I should have put this extra detail on my orig cast. I'm not def advocating a switch to the BSky model for cast distribution, just adopting the PDS for storing each user's historical casts/replies/reactions. Can think of the Hubs as the hot cache (up to how much storage has been paid for), and PDSs as holding all the user's content. It would allow a user to also push this same content via other channels.
2 replies
0 recast
4 reactions
Daniel Fernandes
@dfern.eth
I've had the same idea, but I agree that "everybody run your own server" was a nice idea a decade ago and is a bit anachronistic now. What I'd like to see is a PDS that runs on a file storage network like Codex/ARWeave/Filecoin so you'd get high uptime/bandwidth, and you could achieve "POSSE" via an IPFS gateway so Web2 clients could fetch an RSS feed
1 reply
0 recast
1 reaction
boscolo.eth
@boscolo.eth
What's great about the PDS as conceptualized in BSky (and my proposed addition to FC) is that users don't have to run their own. Think of it as an abstract server class that can be instantiated into what ever app you use. It makes heavy use of IPFS CIDs, but access to a particular users's content is done via HTTP, so no gateways needed.
2 replies
0 recast
2 reactions
shazow
@shazow.eth
One wrinkle in bsky's PDS design is that it custodies the private keys of the identities using it, right? I like FC's design where the identity custody is onchain. That said, I do like the less-monolithic architecture of bsky (vs the hub monolith): 1. PDS has PDS-local data 2. Relays have aggregates of PDS's (full or subset) 3. AppView has indexes/views of a relay Makes it much more reasonable to run a small subset of infrastructure for a specific app (e.g. might just need a PDS, or a partial relay, or a partial appview), rather than always having to have a fully sync'd hub to do anything.
2 replies
0 recast
2 reactions
Daniel Fernandes
@dfern.eth
I guess an external PDS interface could be added to the Hubs, but there's more than that to ATProto, you need the same cryptography setup and the Lexicon schema, which is different from the FC cast format today.
0 reply
0 recast
0 reaction
