Bluesky peeps,
what are some novel technical aspects of bluesky I should be aware of?
Does it have a killer feature or something architecturally speaking that gives it a lot of promise?
Sincerely,
Feeling left out, but not sure why
Bluesky peeps,
what are some novel technical aspects of bluesky I should be aware of?
Does it have a killer feature or something architecturally speaking that gives it a lot of promise?
Sincerely,
Feeling left out, but not sure why
bluesky as it exists in beta is a lie. It’s a centralized service only making a promise of decentralization in the future.
At proto is more complicated, but I think the main benefit is if you care about owning where the data lives it (will be, remember it’s just a non production ready promise) cheaper to run your own repo than it is to run your own relay.
For reach the indexer is still gonna have to, index, some of that so now that’s cached over there so…
there are a few cool tricks with DID, not sure it’s worth the complexity trades of from day one, I think those who want that complexity on nostr will be doing it with delegation and multi-sig and those features are silly to put as the first thing in the protocol.
don’t feel left out… there isn’t anyone on there who wants to have this architectural conversation.
nostr:note1zggtuu3ktsh3ks86y7tyjkmsat9jr3d4njyf4e2zklrwj59mqxcs2lfg62