6 ms·
The biggest problem I see here is forwarding someone else's unknown and unencrypted content. Imagine you're running a relay on your machine, and somebody posts
by nine_k 4y ago
The biggest problem I see here is forwarding someone else's unknown and unencrypted content.
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.
- drexlspivey 4y ago[flagged]
- Semaphor 4y agoWhat is? How would this scenario be prevented?
- nine_k 4y agoI'd appreciate a bit more detailed answer. 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.
- larrysalibra 4y ago> 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.
- nine_k 4y agoThat's actually a great idea: run enough relays yourself, so you can somehow conceal your identity, and somehow protect yourself from things like losing your (DNS) domain. It's a bit like posting to your blog anonymously, and having a bunch of mirrors.
- drexlspivey 4y agoYou are going to post illegal stuff (signed by you) then somehow convince someone to raid my server in the hopes of that illegal thing being on my hard disk. Relays don’t have to store any message on disk, they relay stuff real time over websockets. Even if you store messages you can trivially wipe them every 24h? 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.
- larrysalibra 4y agoAll this stuff might true, but from both a user and a developer perspective it actually works today and has a vibrant community of motivated, talented and interesting people building on it AND using it. 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.
- nine_k 4y agoI see now. The censorship against which Nostr offers some resistance is things like being banned from Twitter, or being expelled by disgruntled moderators from a subreddit, or maybe even fired by your domain name registrar.. 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.
- rcoder 4y agoOne other critical bit of "censorship" and "oppression" that Nostr very much wants to route around is any restrictions on use of Lightning et. al. cryptocurrency payments directly in Nostr clients, without any intermediaries or custodians in the way. (This fear of "economic censorship" seems to be a common boogieman in cryptocurrency circles, from what I can tell. Certainly a bigger fear than state-level actors coming after you for your Nostr notes or toots or whatever.) 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.
- madeofpalk 4y agoFor what it's worth, the US has "section 230" that absolves services providers of liability for content their users post.
- Georgelemental 4y agoSection 230 doesn't apply to CSAM, since SESTA/FOSTA
- kenmorechalfant 4y agoIf your software encrypts user data with a user owned key that you never touch, i.e. everything is encrypted at rest, can you still be liable if it's later proven to be CSAM?
- panarky 4y agoIf you have knowledge of CSAM or reasonably expect CSAM exists in the traffic you're forwarding, you have liability.
- Karunamon 4y agoNot much. While this may keep you out of jail, it will not prevent you from being raided at four in the morning and having your pets shot and all your computers seized for months.
- aliqot 4y agoWon't prevent your pipes and hosts from extorting or struggling you either.
- nunobrito 4y ago> 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. 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.
- nine_k 4y ago> 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-photos-of-himself-on-his-phone/ https://www.cnet.com/culture/teen-arrested-for-having-nude-p...
- nunobrito 4y agoOK. If data is unencrypted inside the machine then indeed that is a problem.
- sph 4y ago> 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. 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 https://news.ycombinator.com/item?id=34530876
- eduction 4y agoThe whole reason I was excited about Nostr was the censorship resistance but if the relays choose who gets to authenticate you’re back to square one (well, whichever square Mastodon is). 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.
- Ajedi32 4y agoI've only read a little about Nostr, but I think the difference is that with Nostr you own your own identity, so if a relay bans you you can just switch to a different relay and continue as you were with no significant disruption. You're probably right about shared blacklists eventually becoming a thing though.
- Cameri 4y agoThe AUTH Nostr Implementation Possibility is not mandatory. You can choose to use it or not, it's not all or nothing. Every single NIP except for NIP-01 is optional.
- aliqot 4y agoI wonder what the XMPP camp is up to these days
- 4y ago
- BudweiserZero 4y agoThis all depends who colonizes the space first. I have a rule, don't hang out in bad neighborhoods, this extends to social media, decentralized or not. 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.
- twobitshifter 4y agoThe protocol notes that the relay has a choice to accept content, for example a large video. If you were running a relay you might want scanners for spam and illegal content running out front before relaying any content.
- jb55 4y agoIt's only recommended that you store json and text on relays. It's a text protocol, not a protocol for storing large binary data. Note sizes are restricted as well on most relays.
- giantrobot 4y agoUsenet is fundamentally text-only. In fact messages need to be 7-bit safe. It's still been a place to distribute binary content for decades. If I can store multiple messages on a relay I can distribute arbitrary files. So being text-only doesn't really limit anything.
- Turing_Machine 4y ago> The biggest problem I see here is forwarding someone else's unknown and unencrypted content. 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.
- vorpalhex 4y agoThose have both been major problems for email. Enough that email has had multiple attempts at becoming encrypted, and mailing lists are very defunct for any sizeable group.
- Turing_Machine 4y ago> Enough that email has had multiple attempts at becoming encrypted 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.
- vorpalhex 4y ago> One presumes that this is because people like email the way it is 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.
- leishman 4y agoI think this is a very overblown concern that will not be a big issue in practice… at least not for a number of years.
- wkat4242 4y agoFamous last words... 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.
- Cameri 4y agoNostr isn't aimed at content blocked or censored. Relays also don't host media, it's meant for text-based comms.
- giantrobot 4y agoWell HN is text-based as well yet... iVBORw0KGgoAAAANSUhEUgAAAAEAAAABAQMAAAAl21bKAAAAA1BMVEWbueItP/xuAAAACklEQVQI12NgAAAAAgAB4iG8MwAAAABJRU5ErkJggg==
- Cameri 4y ago"That doesn't look like anything to me"
- biosboiii 4y agoMastodon already has "censorship" options, and still people use it big time to distribute CP. https://www.secjuice.com/mastodon-child-porn-pedophiles/ https://www.secjuice.com/mastodon-child-porn-pedophiles/ 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.
- humans2 4y agoSame with Mastodon, same with Tor. Abstract software people forget that at some point we run into the real world. The glyphs of science and math are not holistically representative of reality, but minified abstraction of reality for portability; it would take many more books to capture all of physics in English, so simplified languages over loaded with meaning to save space came about. Social media seemed novel af but it’s resolution was the extent of what our computers and networks could handle at the time. Not some finally destination. Especially with future hardware, RTX 6000, or whatever they call it, and beyond making novel content generation via ML a thing anyone can do, social gabbing in filter bubbles seems even more likely to be on its way out.