Not even TCP/IP is the protocol to rule them all. In the #protocolSociety, data is not(!) tied to the transport channel. Data is tied to mathematically derived keys. The protocols that add the most value to the most people and let us network using data unbounded by the message passing tech, will rein supreme.

Should be popular opinion: “Pear and Nostr should enter into a symbiotic relationship”. https://pears.com

The node itself can be a hidden onion server (code on repo defaults to TOR), but data can really be transferred using what ever channel is available. You can even send content (nostr notes here) using USB-stick and someone else can publish it (same as Nostr).

I also invented “archive nodes” and “bridge nodes” which is basically what relays are in Nostr. This implies that indeed, we could implement #treebit on Nostr without actually making any big changes to Nostr.

A node connects to peers that it discovers. The peers have to compete for the available bandwidth. Those peers who offers the best content gets more bandwidth. Before downloading content, your node download scores for the content. Content is always identified using its hash. An average score is derived based on your own prefences (key words, WoT aka #opengroups, etc) and a download priority queue is created. Basically put, #treebit is not(!) a gossip protocol, not a distributed hashtable either. Its 100% p2p where your node only store the content you value (which is the content you want and content your node think your peers want). The whole design is based on incentives. I dare to imagine that this is might be a novel p2p protocol, because I never heard of it before (though that could be simple ignorance on my part).

Love to hear it. Ive stopped working on it myself (don’t have time to do it any longer), but would love to see someone else at least get some inspirations and what not!

So true. Why not wrap the relay in an onion hidden service. Very easy to do.

nostr:note1ajaxz2kt8uc3rm0zfkht5gnzqng7hszm5q5h9vpr88hhrgz3fdkqfqkwwd

No. No-one knows about it. I developed it a few years ago (before Nostr existed) when I designed a network that is pretty similar to Nostr. I realized that for content to properly propagate while remaining true p2p and work even in ultra hostile environments (such local adhoc meshnetworks that were being attacked (think demonstrations etc)) content needed to be filtered. When Nostr broke through and reached escape velocity, I quit working on it.

When I tried to solve the “content storage and propagation issue” I found that it would be possible to solve it using an inventive model, where the content itself is attributed a value (no shitcoinery). Basically the network nodes would cluster in #opengroups https://github.com/baumbit/opengroup and what we think of today as relays, would be transformed into network cluster bridges.

Id say its semantic nitpicking (which can be a good thing) and that it also depends on what ur trying to understand about it. Bitcoin is much more than p2p though, because there is a social layer to it, incentive models, etc.

Ive designed a network (giacomo vetted it) that does exactly this and the ideas can easily be merged on Nostr. You can read about it here: https://github.com/baumbit/treebit?tab=readme-ov-file#what-is-treebit

words of wisdom! we need true p2p and this requires some sort of content filtering. fortunately there is a way: #peercuration https://github.com/baumbit/peercuration?tab=readme-ov-file#peercuration

There is nothing preventing this, but someone has to do it. And someone will, at least when the attacks starts. We could go even further though… and will need to integrate #peercuration

so true! there is an easy fix. just wrap a nostr bouncer in an onion hidden service and let it connect to other such wrapped bouncers.

yes. i thought about implementing the #treebit network topology (https://github.com/baumbit/treebit?tab=readme-ov-file#what-is-treebit) on #Nostr You could easily do this using a nostr bouncer and wrap it in an onion server.

Thats a great idea! And it’s possible. I designed a protocol similar to Nostr (before it existed) based on the idea that all users gets extra benefit from running their own node. It is the #treebit network (https://github.com/baumbit/treebit?tab=readme-ov-file#what-is-treebit)

If there are only a handful they can be attacked easily. If everyone is running a relay, it’s much harder. If everyone run relays (we should) a relay is no longer the proper concept, instead it’s a #node, just like on bitcoin. And we can do it!

Along with relays we could also have node-to-node content sharing. It would render attacks on relays more or less pointless, thus no point in even attacking them! Its the #protocolSociety mediated by #peercuration

When relays starts to get attacked, people will understand. But why wait for the attack?

nostr:note197ks4ytxca6ryvah2669j7kuxw0z4jykmgncrjkcnufy8ga92ecsgw7g28

I have a network design that fixes this problem (You can find a proof-of-concept here: https://github.com/baumbit/treebit ). The fix is easy: node-to-node (p2p, just like bitcoin) and content propagation is solved by #peercuration (https://github.com/baumbit/peercuration). The design even works in adhoc meshnetworks. And… good news everyone, its applicable to Nostr notes!!!

In the end we need some type of computer, but the relay design is much hub-n-spole where as node-to-node is less so. I designed a Nostr like network that is node-to-node and the same design could easily be applied to Nostr: https://github.com/baumbit/treebit