nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 what do you think about this idea? beside your notes on why nostr is not p2p.
2 years ago i was working on such idea to make a p2p overlay network over nostr for syncing. since no one paid attention i thought probably its a dumb idea and i stopped it.
more:
spec: https://github.com/zurvan-lab/IPNN
a repo which was intended to be the implementation (kind of empty repo): https://github.com/zurvan-lab/redvin
note: you may see im using libp2p in my spec which is awful. back then i was obsessed with ipfs and these kind of stuff and i maid this mistake. if i start it again, it would be a custom protocol probably, much efficient and of course a working one.
Discussion
I think local multicast is easy and obvious at least. Almost have a working demo
first time hearing about this. let me do some searches...
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.
got it. so do you think working on this idea worth the time and energy required?
I wouldn't put it at the top of my priorities for Nostr at this point.
makes sense.
What are your priorities?
1. Always remember to reboot my computer when the microphone isn't working;
2. Have more Nostr apps that work well and correctly available for new users;
3. Get the multisig FROST NIP-46 bunker thing working for onboarding and for allowing people to use many microapps recklessly without risking their keys.
you think clients are more important than relays?
i mean implementations.
considering a long term view.