Running everything locally makes ssb damned hard.

I think many features of SSB can be implemented on nostr, and that this would lead to a cleaner and more accessible protocol architecture. For instance there's nothing preventing a relay from acting as client and synchronize the messages of contacts of contacts with peers it discovers over UDP Broadcast.

I've only just started looking at the apps. For the twitter like apps such as https://nostr.rocks/ I haven't yet found the users to follow. I want to have a closer look at nvote.

So what happened? I was away for a while, spent some time at a psychiatric hospital. Now I'm feeling better and feeling more motivation again. So I reconnected my scuttlebutt identity. Because scuttlebutt provides a better protocol than the #fediverse. Key based identities, replication based on social distance make a foundation for trust and credibility.

But the feeling isn't there anymore.

Three years ago I was fascinated by this community. It felt like the place that could revolutionize the way computer help us communicate and gain knowledge.

Now it feels more like a community sworn in around an old code base and some rather esoteric design patterns.

I really tried hard to make it work. Learned pull-streams and tried to make it easier to create new apps on top of the ssb stack. Webdevelopers should be able to build apps on top of scuttlebutt, so I developed #patchboot

Eventually I gave up with node and pull-streams and decided to implement the scuttlebutt protocol from scratch using modern JS. Implementing the protocol I discover some of its flaws, like inconsistent encoding and assumptions about the JSON serialization not warranted by the spec.

I'm being told that the feed format will change anyway and something new and better is about to come.

Then the spec is changed to include "Room 2.0". It seems overly complex to me. I try to express my concerns, I'm being told that I'm too late for these proposals. That I should have participated in earlier discussions.

I believe that the remaining parts of the spec are enough to build great app, so I go on coding with #scuttlesaurus and #tricerascuttler.

Then other stuff happens in my life. And now I wanted to come back.

First I learn that Manyverse no longer supports the protocol documented in the protocol guide. Apparently oasis too now uses ebt.

Once connected I want to see what my community is saying about #nostr. Not a lot. @Dominic wrote that it wouldn't scale. @andrestaltz📱 describes it as a smaller derivative of scuttlebutt. @Rabble mentions the idea of moving #planetary away from the scuttlebutt protocol.

When I look at nostr I see a community around a well documented and modular potocol that has the most relevant features of the scuttlebutt protocol. The scuttlebutt protocol provides a multi-layered stack with Handshake, box-connections, RPC, and Feeds. The nostr protocol by contrast, bases on websockets to exchange events. The protocol is described in NIPs (something like RFCs), implementing a few of them is enough to partcipate in the network.

So yes, I think that time spent on the #nostr protocol us better invested than trying to catch up with the undocumented changes of the scuttlebutt protocol. Maybe many ideas from scuttlebutt can be implemented on #nostr in a better way.

On #nostr I'm 9b9a4c51ed78effff213baec91e8f24ec0ee7399b9e3705928ce2d8e7d296c6c , do you have a key I could follow?

I see some use in private messages and closed groups, but I hope the scuttleverse will remain primarily a public place. The notion of social distance is a good criterion for getting relevant content and maintaining informal communities. I prefer this to closed groups with binary exclusion/inclusion. Readable relevant content is the incentive to replicate feeds. As this is what keeps the network alive I'm worried that too much private content could endanger the contribution of resource to the network.