We just released Planetary 2.0 (our secure #scuttlebutt app). It includes a rewrite of the core secure scuttlebutt bot and the frontend ui from UIKit to SwiftUI.
https://apps.apple.com/app/apple-store/id1481617318
Folks might not know, but a lot of what nostr is based on is secure scuttlebutt. There are design differences, but it’s 99% the same. Because of that, we’re working on a version for nostr, which we’re calling nos.social.
Please take a look and check it out.
How is Nostr able to support the same identity on multiple clients but I don’t see that on SSB? Is there a fundamental difference in the 2 protocols that enables this?
Yes! SSB is fundamentally cryptographically signed JSON in a hashchain (or blockchain). Nostr is just cryptographically signed JSON. Because SSB posts are strictly ordered you can't add to the same hashchain from two separate devices because it forks the chain. I wrote more about it here: https://mattlorentz.com/weblog/2023/01/18/nostr-v-ssb.html
Is there a way / best practice to group SSB identities together?
Not really, that’s part of the problem. What folks do is they link to their other identities in their bio… there is not accepted cross signing of keys yet. There’s a proposed feature called fusion identities and a new feed format called metafeeds to solve that but it’s been very slow going.
I saw your post on planetary dot social that you are winding it down. I suppose it was not ever possible to have read only accounts on SSB (like they do here on Nostr). Read only accounts can’t fork the blockchain.
We do basically have read only clients. Look at planetary.name as an example.
