My next goal is to get users to reduce their relay lists from an average of 20 to 3.
You don't need to trust 20 relays. You just need 1. But 3 adds redundancy in case 2 of them are busy at the same time.
And remember: Relays can see what you are looking at in real time because the app is requesting the post, likes and replies from them as you scroll. They can even count which posts captured more of your attention.
So, make sure you trust your relay operators.
GM.
Humm.. because it is spam, it will not be cached locally. So, if you are going back to one of the hashtag views, it will keep asking for it. I will check when I get back home
On the general list, yes. You can click on the arrows. The outbox and inbox lists have their own rules. Outbox/Home relays are always read/write, inbox is always read and write if the post tags you.
Yeah, we try to avoid it, but sometimes the AI just overrides the process and translates the link itself. Happens here and there on the Google translate web version as well.
More stable Amber support for NIP-46 nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck and a desktop signer to do the same.
Sure, but that's just spam. It's true for the whole of Nostr and the old nip04. Any key can send you a DM.
But a Sybill attack is about using fake identities to gain majority power. The fake identities on Nostr don't give the attacker extra power/influence in the network.
Did you know that NIP-17 was designed to keep metadata private even if devs make mistakes in their apps?
Designing a DM protocol where you control the server and app on a single codebase is very different than designing something anyone can code flawlessly from scratch.
We are starting a trend.
nostr:nevent1qqsp9x0qf3tgj8qj4qqwyd8w0mszqec49ck098u7z7mmf7te7huvqagpz9mhxue69uhkummnw3ezuamfdejj7q3qye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjsxpqqqqqqzg0gyhc
This is why you must add DM relays to your list... The incognito becomes active by default and no one can see who you are talking to.
nostr:nevent1qqsx8g553v99e6559lrg9sa6vv79spfl7mutgsnlydpkp7a8vw4a5ecpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3q64r4kfyyre2w2yy85zdsvlyk8xl2rj99xqjk4r65zfvfeqycu8zqxpqqqqqqzpyvsmq
The protocol uses channel IDs and generated keys that are visible to the servers. Those can be used to track you around. Especially if both users use the same server, which is common for the default setting of the app.
Are those things the default now? Last time I check they were still opt-in. And since most of those servers were been run by the same entity, in practice people can still be traced.
But yes, this is way better than their version from last year.
Do you know why they decided to not use Tor sessions to do proxying and masking?
This is why you must add DM relays to your list... The incognito becomes active by default and no one can see who you are talking to.
nostr:nevent1qqsx8g553v99e6559lrg9sa6vv79spfl7mutgsnlydpkp7a8vw4a5ecpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3q64r4kfyyre2w2yy85zdsvlyk8xl2rj99xqjk4r65zfvfeqycu8zqxpqqqqqqzpyvsmq
Ohh yes. Most definitely the list got deleted at some point or the relay that had it got busy, was offline and didn't send on time. Then Amethyst started a new one when you added a bookmark.
Reminder that if you are using DM relays like inbox.nostr.wine or auth.nostr1.com and no other relay for DMs, you are so private that our own Push Notification system can't see your DMs to send you those notifications :)
We haven't figured out a way to allow push systems into that level of privacy yet.
We did operated a proxy. But then I realized that I not only had all the locations for our users but ALSO all their image and content requests. And I could easily associate both. The proxy doesnt only knows your location but know what you are looking at in real time.
To me, the proxy is WAY worse from a privacy standpoint.
Oddbean new post about login | logout
Notes by Vitor Pamplona | export