Last Notes
Relays don’t need much bandwidth
Tor speeds even nowadays are not great and that is why torrent network hasn't migrated to Tor but mostly VPNs for privacy and DHT.
Lets hope DNS attacks never happen against Nostr.
Doesn’t matter if they do. Outbox allows relay names to change, .onions exist, and we could use “pubkey URLs” where relays can publish a latest location document that is signed.
Torrent sites have been targeted, Anna's Archive has been targeted and freedom of speech is not what nowadays governemnts particularly like.
#nevent1q…750g
And yet you can still access them via domains outside US jurisdiction, proving what I said.
These sit outside ICANN jurisdiction.
And the root zone file is distributed *everywhere* and the servers running the root nameservers are ran by many independent parties.
I think that the idea of a coordinated attack against Nostr via DNS is absurd. Instead of worrying about such nonsense (which can already be circumvented via Tor etc.) we should work on other solutions.
I should remind that countries also control their own TLDs
Thats cool 🤙
Also clarification the my upper note. I am not against big relays. They do bring in positive features and should be used in the network. I just would like the network to be sufficiently decentralized and if someone targets them and brings them down (even on DNS layer) the Nostr network to continue work as if nothing happened.
Yes, that, and the big relays which are good for efficiency but create more centralization and attack vector for bad actors.
And (small) local private relays on decentralized network can be good addition to the current Nostr stack.
some more thoughts inspired by another comment
#nevent1q…spjj
I haven't read the FIPS techonology but many people mention it. A good thing for the DHT though is that is well proven with the torrent network. But if FIPS is working even better then it should be used. The goal is to have decentralized robust social network that is really hard to censor and attack. Becaus I think it would be needed, seeing where current global politics is heading.
Well a deep thoughtful analysis is always good to be done as well as open discussion.
But I don't see huge risk because relays already talk to each other. With DHT they will have another layer to talk to each other without using DNS.
Nostr network is build by clients and relays.
At the moment most relays store a lot of data and use DNS.
I think DHT is really good solution for the relays.
Big relays can use both routing networks.
But local solutions like desktop/mobile client and small relay/cache togerher can benefit a lot from DHT from the decentralization point of view.
I use Gossip dektop Nostr client because I don't want to share my nsec with web services.
I now use public relays but if I build one as a proxy I won't need the public ones. And Gossip already caches/ stores locally notes.
So everything is there, the infrastructure works, only Nostr relays can benefit from more decentralized routing and that can also bring standalone local clients similar to torrent clients that store locally certain amount of notes/data.
And the current Nostr stack will continue to work as it is. Its just a good enhancement to it.
I love Nostr, I think its needed as one of the freedom technologies and I would love to see it even more decentralized with proven technology from the torrent network, meaning more robust against any attempts to take down and censor.
Well, the technology is old and proven from the torrent network.
Its a relay discovery so just another routing layer, but improves decentralization, self-hosting and robustness of the protocol, just like in torrents.
Okay but why not on Nostr as well?
This is an interesting finding.
A simulation of a Kademlia-based Distributed Hash Table for Nostr relay discovery.
Now imagine attached small relay/cache to a client desktop/mobile (just as an example, the idea is in the decentralized routing and discovery) and it supports this type of decentralized discovery and routing.
I think Nostr will get to a higher degree of decentralization. To me it looks like Nostr social torrent network which avoids DNS and can be used in addition the the exisitng routing with domain names etc.
https://chr15m.github.io/nostr-relay-research/
https://i.postimg.cc/rmcGB2vy/Nostr-DHT-Kademlia-1.png
What do you think @npub1acg…p35c @npub18am…p424 @npub1utx…50e8 ?
Get off Google.
I abondoned their search engine in 2021, the results are really really bad.
First thing I do is install an ad blocker extension
I actually put quite some effort into selecting my reaction. I have custom ones and sometimes I find a new sticker to add, just to respond to someone else's note.
That's just... fun. Fun is overrated. These are social clients. We are allowed to have fun, here.
What a stupid idea 😄 What dumbass came up with this?
That's what kind 11 discussions cover. just +/- as voting.
But kind 1/1111 are social, so it makes sense to let people have some fun. It's not as serious.
This is another thing altogether. #Amethyst has a separate DM Inbox setting, but some other clients do not (maybe primal?). The side effect could be what you're seeing.
I'm referring to the "inbox model" originally devised by @nprofile…nq40 in the @nprofile…t6ps.
The idea is that you post your notes to your Outbox relays, and you read reactions and responses to your posts from your Inbox relays. This way your Outbox relays could be "read only" to the world, ones you pay for or control and are less likely to be censored, and you tell your followers to respond in the "Inbox" relays the "public" can write to and where you check for responses.
The problem is that most people set their Inbox and Outbox relays to the same relays, where their Inbox relays can't be written to without a subscription. This breaks the outbox model. One should not put paid-only relays in your Inbox relay set, unless they allow responses to your posts (which, in general, I think they should).
https://npub1c856kwjk524kef97hazw5e9jlkjq4333r6yxh2rtgefpd894ddpsmq6lkc.blossom.band/3d7ca345ab41bca5874e02cfad54fd97f007770a5dc704dfefaddcf84770d0bb.jpg
Chissà, magari un giorno.
Grazie mille Daniele 🙏
Per me sarebbe un vero piacere che tu fossi il suo custode.
Se vuoi ci mettiamo d'accordo 😊
And sometimes the void talks back
Egui has this limit. Possibly related to GPU texture limits on many GPUs. In any case, we should at least display a shrunk image and not panick the thread. And that is what I did on the unstable branch yesterday.
This land was green and good until the crystal cracked
Ok I put a possible fix on unstable. Your example gives me 403 forbidden so could you test the unstable branch and see if it fixed?
Ok we need to have some safety catch code that refuses to display if it is too big.
I tried it out but "Connection failed. Please reload." twice when trying to use it with my Amber.