Need this on nostr https://i.nostr.build/aQP3B.jpg


mark this note down for purge in 2 weeks


This is only reliable on a Discord/Slack style client that treats each relay separately


Relay purge request


I was told relays can or do support this. So… we don’t need perfection and we can call out relays who don’t honor requests and ditch them


And just hope relays delete it? Apps stop displaying it?


yes

saves relays data + good for users privacy


Thats your response to everything 🤣


If implemented: someone will set up a relay that only shows expired notes 👀


We have expire spec


💯 even if not guaranteed. We can refine until it’s good enough most of the time


noswhere will retain your notes as long as they are useful to me even if they are ephemeral or you set an expiration
even if you don’t send anything to the noswhere relay

anyone can do this


Let’s do it 🚀


Let them 🤷♂


Need to trust relays to delete though...


We don’t need to hope. We can probably check which relays don’t and just not use them.


Impossible


Any way to easily check if they didn’t?


Impossible or sounds difficult so I don’t want to try?


impossible


I believe that it's impossible because you need to count on behavior over protocol


Sure. From a pure information perspective. But realistically it’s a valid feature request. But not everyone wants Nostr to be a zero trust system. Some amount of trust is useful.


🤔 true. So.. what’s the fix for it?


I do not accept that answer, despite it being valid.


nostr will be so freaking cool if NIPs are prioritized based on top reposted #feature_request notes every month.


nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 any thoughts? Doable? Not possible due to rebroadcasting?


Need this on nostr https://i.nostr.build/aQP3B.jpg


Even though you could use event deletion, It is still technically stored in relay's storage.


That's why people want walled gardens and better encryption. They'd rather have hardly any reach than no control.

People want to own their data, and you don't own something, if you cannot control access to it.


Yes, it's just usually supressed or stamped in the clients, and the relays often seem to keep absolutely everything.

There's no relay trash collection, or anything.


I thought about that at one point, but then I discovered that the notes were disappearing. Don't the relayd already have an expiration date for the notes?


Should be working today with expiration tag (when clients/relays support it). Question is if the attached content should be deleted as well - we could build blob expiration into blossom. nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr


Delete should be used here to protect encrypted conversations. To compensate for the risk of encryption or private key theft.  #[2]  may have a idea


When you put something on the internet where it is accessible to some then it could become accessible to all. People think they're in 'private' Discord servers, meanwhile there's a bot in the same server scraping everything. Similar thing would happen with a relay.
https://www.404media.co/a-spy-site-is-scraping-discord-and-selling-users-messages/


Yes, but that can happen IRL, too. There is no full expectation of privacy, anyway, but there are more and less private places.


We've got repudiation through key rotation, in theory.


A private relay is only as private as the users and operator of the relay want it to be


It might be a little difficult to add expiration to blob since there is no single event or thing that represents the across the network.
the only thing I can think of is the server would be aware of 1063 events and any expiration tags on them


How would this even be possible if it's all going through relays?

Wouldn't all relays have to implement this for it to work?

Am I being a dumbcunt?

nostr:nevent1qqs9c0rt6ltnmdxcz76n324u7jhj70yuqkxwyy2r43grvk784e334cspz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqx78pgq53vlnzmdr8l3u38eru0n3438lnxqz0mr39wg9e5j0dfq3qvzqqqqqqysts438


We already have that specified since many months ago.


I would use this. It'd help with bloating.

nostr:note1ts7xh47h8k6ds9a48z4tea909u7fcpvvugg58tzsxedu0tnrrt3qta9p3y


Oooh no you don't


Oof


Walled gardens don't fix this.


The only way to keep something deleted is to never share it. Bitcoin, and more broadly, cryptology solves this by keeping information secret.


How will the client know what relays to send the delete request to? People can broadcast your note to any relay they want.


Deletion is a centralized trust model


That’s only if they broadcast it


zap dat

zap dat


Need this on nostr https://i.nostr.build/aQP3B.jpg