I don't think this has anything to do with my notes on p2p. I like p2p, p2p is good every time it is possible. Direct syncing between specific devices is such an instance.

The overlay network is the hard part, maybe start with that.

> The only thing missing is an overlay network for linking nodes, but people can continue innovating on that front once we move beyond websockets.

And then a miracle occurs.

Nostr's main goal for 2025:

Figure out if we prefer single pubkey in all of our apps and thus a single main follow list, single notification feed for everything, single key to send DMs OR if we prefer owning multiple pubkeys, one for each app, so that follows, notifications, profile info can all be separate per app.

There are pros and cons in each. And any solution between those two gets really complicated.

For instance,

- If we use multiple keys, one per app, our DMs will also be on a "per-app" basis and senders for the DM wouldn't know which app you are still using to send you a DM. We would need to declare which key everybody should use for DMs with us.

- If we use just one key, we need to move away from our main follow list event so that each app can have their own follows and all sub-root event kinds (zaps, boosts, reactions, replies, reports, edits, etc) MUST also include the event kind of the root event so that each app can have their own notifications. Since it's impossible to require full compliance from ALL clients, it's likely that some notifications won't show up where they should.

- If we use multiple keys, friends of one app might not be readily available when @-tagging on a separate app. We can try to link all the keys so that Clients can always check information in the other keys to bring up to you, maybe as a fall back mode. But wouldn't that in the long term just create the same one-key for everything system?

Who knows...

Yeah, I had it until now in my list for testing :)

Yeah, but no one uses desktop anymore. :(

Every few months Nostr dumps the people I’m following.

Am I doing something wrong?

#asknostr

All nostrdb nodes (damus ios, notedeck, damus.io) are caching nodes. They have the ability to collect notes and note stats incrementally via relay hints. There is no single “global” view of the network, it’s a much more accurate reflection of what nostr is and how it works under the hood. With negentropy, you will be able to sync between any two nostrdb nodes.

This is true for the rust nostr-sdk as well (it’s even further along dev wise) but it may not collect note stats (like/zap counts , etc) like nostrdb does.

This is a really cool vision of the future of nostr: massive redundancy for nostr notes spread across millions of devices. Every device is a potential cache.

They tried to build internet v2 this way (ICN/CCN). We are way ahead of them with a practical implementation of a store and forward, information centric network. The only thing missing is an overlay network for linking nodes, but people can continue innovating on that front once we move beyond websockets.

0xchat. I like the sound of that! ☺️

Will try it tonight 👍

Yeah damus is doing something dumb

I just realized my client eats these links, oops:

damus.io/note13s2fhv94qz6pezsa3trwjh538nzfts2pevzz0wxg0wfyj4g755wqjc9fzn.json

Besides the X-like experiences, what's the first #Nostr app I should try out right now?

#asknostr

git it. so they need to be updated. that's fun to know it had these features even before the spec...

damus bookmark implementation is very old before there was a bookmarks spec. It was contributed by someone i forget and was never updated

I uninstalled and reinstalled #damus and my bookmarks disappeared. I had assumed they were saved in my profile like other things somewhere out there. So, bookmarks aren’t portable or saved with your profile like photo and lightning address are? #asknostr