Replies (107)

That would be easy to find out with `nak req -k 10002 -a e4641d0eed71d2d0c0f68cd3508d50fcdb1954ac1ccda269ddbb7a7897c22614 relay.damus.io purplepag.es user.kindpag.es relay.nos.social relay.nostr.band`, but the answer is yes.
That is precisely the reason @fiatjaf is producing all these posts... to put the problem into developers faces so they can smell it up close. Without the ability for clients to fetch notes from (perhaps the only relay that doesn't censor them) as specified in the nevent that points exactly to where that note can be found..... then what was the point of making a decentralized protocol?
Just ive noticed clients use timestamps a lot to limit their reqs.. and tend to be very timeline centric. They won't usually see old notes. Tho that doesn't explain why they can't pull a specific eventID from a specific outbox. Relays also can tend to limit old messages, unless they're serving backups capability, so that would make it important that the outbox gitlost uses supports very oldness.
The relay is not in your list, so the app won't connect to it. We are making a new permission screen to allow you to connect by clicking a button, but it's not ready yet. :( But yes, attackers can use relay hits to monitor the IPs of victims they want to track. If they know IP, they can get a rough location. If they can track over time, rough locations become more precise identifiers. It would be an elaborate social attack, but it is possible.
Huh, so even if I follow the account, amethyst will not connect to that accounts outboxes? How will it find anything in that case unless your relays match their outboxes? Or you're just saying, outbox is not fully operational till you have the extra settings?
Yeah, the attack vector is much much larger than a centralized social platform. Instead of Facebook or Twitter knowing everything about you (which at least they protect). Here any rando could figure out a lot of things. Guess I should really not use nostr without a vpn. Though now sure how much that helps. Though VPNs somehow still leak a lot of information.
Servers can always track you. Relays are the same. That's why we avoid connecting to random relays. You MUST trust the relay operators in your relay list. If you don't trust them, don't use them. Find better ones.
Literally ANY web service you use has this capacity. The only difference here is that its in the open. Many devs DO in fact advocate for privacy and security. @Ava is 🐏 and gives amazing tips and advice. Know your threat model and how to work with it. No one else is going to hold your hand and do it for you.
But should the easy solution be. If I see a note, and I quote it, the client should rebroadcast that not with my quote? Isn’t that just a thousand times simpler? It doesn’t solve everything, but gets rid of some issues.
If people aren't using Tor and aren't using a VPN but they care about this, then I sure hope they never open a web browser. But giving people the head's up and asking permission is nice. People want to see the note, but they also want to feel in control.
Gotta do your research. Find each of your relay's operators, read their privacy policies and terms and conditions. You need to know who you are "in business with" and what they are and are not doing with your data. Don't delegate that due diligence to anyone else. And always remember, if it's free, you are the product.
That's the goal. That security on Desktop is less of an issue, but mobile is crucial. You don't want people to know where you have been all the time.
If you connect to a relay, that relay knows you connected (your IP address) and what questions you asked. This is EXACTLY like a web browser. Everytime you go to a website, that website knows you connected (your IP address) and what questions you asked (the URL). People who insist on hiding their IP address use VPNs or Tor. This works perfectly well with nostr just like it works for the world wide web. Trying to avoid connecting to some relays just makes nostr dysfunctional. This problem is outside of nostr, and nostr clients are just making the problem much more complicated than it needs to be by coding connect-based relay access control lists. Just tell the user to use a VPN or Tor if they are concerned about privacy. As for AUTH, that makes more sense to me. You shouldn't just AUTH to a random relay. But fetch a note... I don't see what the big deal is.
I love that you separated the relays into sections, is it possible to have a drop-down menu I relays that work in each section, that we can choose from and research or have a star system?
Agree on Tor and on Auth. But we don't have a good/easy solution for Tor yet. Most people just use their regular connections on the go. So, I see as a massive privacy risk.
We made the questions just a number in the lower left. AND after you answer all the several hundred questsions, they don't keep repeating eventually you catch up with it. BUT YES your point is very valid. It is fucking annoying to approve every relay. But I'm also coming around to the idea that an 'nevent' is kind of like phishing, getting you to go to a relay that is malicious, just like a link in an email trying to send you to a malicous website. Whitelisting relays is one solution, painful as it is.
It is, and so is media loading.. which no one ever talks about they just harp on relays. VPNs or relay proxies that you trust are the only solution. And probably image proxies if you're doing the proxy option. Tho I applaud the efforts in attempting a UI for connections, it has enabled me to see that using nostr means you go to weird servers all the time. At least nevents don't have JavaScript payloads or anything, it's safer than browsing (I think). But images, yeah those are likely the most dangerous thing.
.'s avatar
. 1 year ago
Does reading from a relay and not writing to it offer any changes in privacy?
It depends on which filters you send and if you have to auth or not. We just have way too many filters bundled in one subscription to risk. Gotta redesign that part of the code :(
Default avatar
Rand 1 year ago
sounds like drugs/ prohibition etc crazydays/metadata?
Default avatar
Rand 1 year ago
ya, still seeking solutions(can't code),,,,ffs
It could ask for AUTH and if your client allows it your client will tell it (and prove) your npub. Then it knows WHO is at that IP. This IMHO is a step too far and clients shouldn't AUTH to random relays w/o asking the user. But gossip lets users turn that off if they don't care.
How about the note to be rendered show the relay name below an "Allow" and a "Whitelist" button. I guess generally this is a similar problem as emails and images. Many email clients just load you YOLO all images received, which is a stupid behavior.
That's also hard, because what "requests" do you allow, and what "requests" do you ask the user? At the end, if every key interaction is asked, it is the safest, but the most annoying.
Yeap. The majority people whom I onboarded left just because apps are poor and buggy and people confused. Simplicity and stability will win.
#nostr relays should talk between themselves as in a NETWORK so we can connect only to our trusted relay and pay them to protect our privacy
Your IP is recorded and tracked at every website that uses google tag manager for example, and thar is almost all websites. Your IP is sold and resold hundreds of times by Google and the hundreds or thousands of data aggregators. They build detailed profiles of everybody, and it's on the market. It's not just nostr, everyone needs a full time VPN and ad blocking, period, as a bare minimum.
Centralized platforms knowing but "protecting" your information is a total fallacy they would like you to believe. Selling your information is how they got huge. They anonymize it maybe, but once it's sold it's out of their hands, and it is quickly de-anonymized, attached to a detailed profile, and resold.
The fixes have to be client-side and whatever can be done in the protocol because we don't know what malicious software relays run. I am glad to see devs are exposing what the problems are and iterating on potential solutions. Sites that just want your traffic will be quiet about the vulnerabilities, especially when keeping you vulnerable is so profitable.
VPN or tor is the only way to obscure your IP on the internet, feel like I'm talking to a wall sometimes. Is this just beyond most people's understanding? Relays are already as dumb as they can possibly get.
You don’t have to tell me this. I’m with turned on orbot but there are not too many people like me. Vitor did it right by implementing it inside the Amethyst, that’s what all of the mobile should do as well to make people aware and use it by default or turn off if they struggle with performance
Ok your note was very confusing then.. this one makes more sense. That's right you even ran a relay and use Tor now.. it's just sad when people see a note like this and go 'wtf? Back to centralized then'. Instead of, oh, how do I VPN?
I thought #nostr only recorded time and the content of posts? You’re saying individual relays can add their own trackers for other metrics if you choose to connect to them? I guess that makes sense, different servers/websites can use different analytics so why not relays.
Would be interesting if relays had a special REQ type that effectively says “go to this other relay and get me this event”. It’s like rebroadcasting the note without the client actually having the note. If the relay stores the note then it doesn’t even have to retrieve it with other requests.