If the problem that Nostr solves is, say, posting NYT headlines, pub crawl reports, or cute cat pictures, it's fine, but most centralized tools are also fine.
If the problem which Nostr is trying to solve is being censorship-resistant and allow for dissemination of information which is actively being suppressed, relay safety considerations become important. Less safety means fewer relays, and a need of a personal connection / trust to be admitted.
Because almost all of Nostr logic is in the clients, you can always run your own relay or pay someone to run it. There will always be someone shady that will run a relay for you if you pay enough for it. And people that follow you will still be able to see your posts.
I agree that the current state where there are hundreds of open relays and people people posting to 20 of them at a time isn't likely to be what the network looks like in the future. But that's fine - it's good enough for now.
It's a bit like posting to your blog anonymously, and having a bunch of mirrors.
Then you are going to convince a judge that the thing on my disk belongs to me, because judges are apparently braindead.
If this is the protocol’s glaring vulnerability then every server in the world has this vulnerability.
This is also the case for tor exit nodes, which is why those here are all hosted by organizations with lawyers.
As you distribute the content here, unlike with tor, you would essentially act as a user generated content provider and would have to take steps to prevent the abuse from occurring again… probably after an involved court case.
This is not like "every server" because not every server distributes what anyone publishes to it.
Though a lot of that might not be an issue in jurisdictions with saner laws, I don’t know specifics.
Signed by a private key which has no connection to my legal identity, and which can be generated in a split second. Signatures give strong pseudonymity.
> Relays don’t have to store any message on disk
This is a good idea, as long as messages are relatively few, which may be hundreds of thousands if they are short. There's no promise of availability, so an infrequent reboot is free to erase them.
> Then you are going to convince a judge that the thing on my disk belongs to me
I'm afraid it can be the other way around, if the material is sensitive enough. You'd have to explain to the judge how it ended up on your computer.
> every server in the world has this vulnerability
No, only a server that allows users to upload UGC without requiring enough background information to let the law enforcement find out their real identities if need be. Should be an adequate explanation to the judge in a civilized country where governmental censorship is not a thing.
So just to be super clear, you don’t upload images on a relay, nostr messages are just signed json blobs i.e text. If you want to post an image you just post a link to it and the image is hosted elsewhere.
If there is such a thing as an illegal text string that is illegal to have on your hard drive then I can do the same attack on any webserver by having the illegal string in my user agent and it’s going to be saved to the hard disk in the logfile.
Then according to your plan I can raid the server with the illegal string and put the server owner to jail. Does that make sense to you?
This sentiment is what's missing in the decentralized space. There are so many centralized spaces that you can use to communicate, and that censorship-resistant is a non-feature.
There are ways to address all of these problems if and when they occur.
I think one of Nostr's biggest contributions is its culture of pragmatism and speed. Do something simple, quickly that works instead of sitting around worrying about every edge case (which is a what a lot of "decentralized" projects do). If you have no apps and no one using them, none of the problems you mention exist. If you come up with something ridiculously complicated (think some recent w3c proposals), you've built a massive barrier to contributors and to developer and user adoption.
It's not the kind of censorship resistance which opposition in country with an oppressive regime might need, and in general not a solution against censorship by state-level actors.
Well, fair. Also, fun and lightweight, no browser needed.
Whether you think that's a good or necessary thing probably tracks very closely with your beliefs about whether money and its expenditure is protected speech. Obviously that's something about which the highest courts and legislative bodies in the USA already have complex and sometimes-contradictory views, so I certainly won't claim there's a single correct answer...even if my personal beliefs fall very much on the "money is a modern social fiction in no way connected to fundamental human rights" side of the spectrum.
Not sure what you expect?
Which I guess is kinda fine if you're building slow go-karts to do friendly races with your neighbor in their backyard - but instead you're already letting those out on the open roads on day 1.
Similar to software architecture, you do start by defining the preferred characteristics and then working your way to the other parts.
On purpose. You can't build a car today that ignores these learnings, and safely deploy it on the open roads; just like you can't build what's effectively an open relay like it's 1997 and expect to stay safe against the threats outlined by nine_k.
Your analogy fails at the mere fact that no physical harm can result from Nostr not solving this one thing you think is 100% necessary.
The fact that Nostr is up and running and working is the undeniable fact that you don't NEED to solve every single problem known to humankind before you write some lines of code.
I've never denied this. You can also DIY a go-kart and drive it on an open road.
> Your analogy fails at the mere fact that no physical harm can result from Nostr not solving this one thing you think is 100% necessary.
Notice how you've specifically used the term "physical harm" to differentiate from other forms of harm. Harm is harm.
> The fact that Nostr is up and running and working is the undeniable fact that you don't NEED to solve every single problem known to humankind before you write some lines of code.
...Where did I try to deny this? My analogy is very specific in that you can do all of these things, and with enough luck, nothing bad will happen.
The problem with luck is that it doesn't scale well, especially on the open road. I mean, Internet.
That is an assumption that you made and strikes as FUD. An equally valid assumption is that nobody can reasonably prove that the person has the private key used for signing the files. Assuming the stated nature of relays and their intended purpose, there is more ground to assume that a relay is a service provider without reasonable way to inspect the contents of encrypted data.
This would be entirely correct were the data encrypted %)
The data are signed, but otherwise plaintext.
For reference, kids in the US got arrested for possessing nude pictures of themselves on their phones [1], because mere possession of a nude picture of an underage person is restricted by law. Talk about who are you going to convince that some shady stuff just happened to pass your server.
[1]: https://www.cnet.com/culture/teen-arrested-for-having-nude-p...
For example; certain nodes on Secure Scuttlebutt have been known to push porn, and this gets replicated onto your store. That node was traced, and blocked by many on the sphere.
The majority on ssb were against that.
Now, a social network populated with crypto bros? Nah... pass.
Relays can be authenticated. If you don't want your relay to accept data from anyone, don't leave it open. Same with any other Internet protocol.
Also, per the spec or convention, relays SHALL NOT talk to each other. Each relay is a separate island, but the protocol permits and recommends clients to publish on multiple relays. This is the basis of their censorship-resistance.
See also my other comment: https://news.ycombinator.com/item?id=34530876
Also, it seems naive to think that a ban on blocklists in the spec will keep real free humans from doing exactly as they’ve done on email, Mastodon etc and share block lists.
You're probably right about shared blacklists eventually becoming a thing though.
The "XMPP camp" is doing well and very busy: https://xmpp.org/newsletter/
We're lacking a nostr bridge if anyone wants to work on that...
That has no bearing on an attacker.
I don't get it. What's the point then?
You can mirror one relay to another easily:
echo '["REQ", "mirror" ,{}]' | websocat wss://source | jq -del '.[1]' | websocat wss://dest
No protocol can prevent a piece of software from doing whatever they want.
The "shall not" is not absolute: the spec assumes and expects relays not to talk to each other. Nothing prevents you from creating a relay that connects to another relay, of course, but that would not be in the spirit of what Nostr is trying to achieve.
If I can store multiple messages on a relay I can distribute arbitrary files. So being text-only doesn't really limit anything.
Like email.
> Unlike an email client, your relay actually makes that message available to anyone.
On the contrary. Public mailing lists work exactly like this. You send a "subscribe" message (or enter your email address and click on a "subscribe" button, or whatever), and the server starts forwarding all the messages to you.
But all those attempts have failed. One presumes that this is because people like email the way it is... simple to use.
> mailing lists are very defunct for any sizeable group.
Hmm... I still subscribe to at least half a dozen mailing lists, some of which have hundreds or thousands of members.
And people choose to live in tyranny? No, it's because it's a coordination problem involving literally billions of people, thousands of pieces of software and would break compatibility.
> I still subscribe to at least half a dozen mailing lists
And I still use a radio to hew packets to connect to a BBS.
I wouldn't want to run the risk of being the first one it does happen to.
I think something like ipfs offers better resistance to such attacks for node owners. I wonder how the two compare because I don't know either in detail.
But sharing unencrypted content from others could be an issue for many reasons. Copyright too.
Especially because this protocol is aimed at content blocked or censored from other platforms, as others have pointed out.
Sure, you can block others from using your relay but then what's the point? Just host your stuff on your self hosted web blog.
Relays also don't host media, it's meant for text-based comms.
iVBORw0KGgoAAAANSUhEUgAAAAEAAAABAQMAAAAl21bKAAAAA1BMVEWbueItP/xuAAAACklEQVQI12NgAAAAAgAB4iG8MwAAAABJRU5ErkJggg==
If I were to run such a node in Germany, and someone would use it to distribute CP with it, I face from 1 to 10 years in prison.
Yeah, no thanks.
When you run a Mastodon instance though, you don't actually need to distribute this content. In fact, you probably would at least ban proxying media for communities like Pawoo, and honestly, probably, any NSFW-oriented instance if you want to be safe.
I hate to break anyone's innocence, but this shit is literally everywhere on Twitter, and a lot of the rest of the Internet, too. Is it legal? Depends on your jurisdiction. Is it moral? ¯\_(ツ)_/¯. Only one thing's for sure: it's on your Internet.
Also, just an observation: either the author of this article is unaware, or feels as though it is not important to mention the other fun stuff going on with Mastodon, like the large presence of zoophiles. The internet is certainly a place to be.
Imagine you're running a relay on your machine, and somebody posts some CSAM, or stolen CC data, or hate speech, etc through your relay.
Unlike an email client, your relay actually makes that message available to anyone.
Unlike an email relay, you are not forwarding the message to someone else like a dumb pipe; there's no final destination.
Unlike a torrent / DHT node, you do not know beforehand what you are going to make available.
Unlike a Tor exit node, you do not deal in encrypted fragments which you don't store locally.
Unlike an IPFS node, you do not store fragments of files while not even having a full set of such fragments for a given file.
Even though the message is signed, you can't reasonably prove that you do not possess the private key used to sign it, or have not possessed.
So, if you are an anti-censorship activist, and your machine gets searched (which may be even easier to do in the case of a VPS), you, the runner of the relay, may have some pretty unpleasant time. Even if you manage to convince everyone that you only forward these messages and do not inspect or endorse them, and the authorities will not even fine you, it will cost you time and trouble.
Worse, it becomes easy to send something incriminating from a throwaway or stolen client through your relay, and report you to the police. This can of course be done with email or any IM, but these will immediately show you what you've got, so you can e.g. immediately delete it. They do not allow perfect strangers quietly put random stuff onto your disk.
Of course the point of the protocol is to resist censorship, so any content deemed criminal by someone cannot be entirely blocked. But the publishers and the receivers of such content make their choice, while those running a relay seem to remain unprotected from from consequences of that choice which they did not make.