Damus
Open in Damus

Recent Notes

Zhash · 4d
Ha, that's Nostr for you. They overlap less than it seems, though: nostropus is for everyone, while Quill's check only helps people who already use Quill. Same idea underneath: the notes are already signed, so copying them anywhere is safe.
Nostr Vault · 4d
Just the new kid on the block, trying to make a name for himself Yes, it includes a local relay listening on localhost. You can also disable the relay completely if you have another alternative like Citrine
Roger · 5d
Yes, the signing side is a client bug, and a relay cannot repair it: it has no way to know that a kind-5 carrying one e-tag was meant to kill four earlier versions of the same address. That is exactly...
 Lez profile picture
Lez @Lez
Yes, right. I'll distribute the deletion events instead of deleted notes. I should explicitly query for deleted events to know if a relay has forgotten a note or it was deleted, then act accordingly.

It's also valid: if I already crawled back to the beginning, I should display the oldest timestamp, it's a low hanging fruit. I'll do it.

I want to take Nostropus in a direction to be a play-around and fix-around client. Stay tuned :)
2
hasky · 5d
Let’s go
Roger · 5d
Distributing the tombstones is the right half of the fix, and there is one trap inside it. A kind-5 only covers what it names: the ids in its e-tags, or with an a-tag every version created before the deletion. So the copy has to be the byte-identical signed event, same id and same created_at. If the...
Roger · 5d
Manual pruning with no advertised policy is the worst combination, because NIP-11 has no field for retention. A client can ask a relay which NIPs it speaks, but not how long it keeps anything, so nobo...
 Lez profile picture
Lez @Lez
Good points, thanks! The deletion/tombstone event being pruned is a real issue I didn't think about. The only thing I don't understand is what the a-tag has to do with Nostropus? It should be fixed in the clients that sign those kind-5 events, shouldn't they? I mean Nostropus could display "incomplete deletion event" if that's what you mean.

There is another issue of caching, sometimes if the published note is read back too quickly, the event doesn't show up because of a stale cache. I myself never had this issue with nos.lol, I've always seen it as a very good quality relay.

The relay-quality tag would be another good feature, and much more could be achieved by running background checks periodically from a server. Like nostr.watch

Thanks for your input, greatly appreciated!
1
Roger · 5d
Yes, the signing side is a client bug, and a relay cannot repair it: it has no way to know that a kind-5 carrying one e-tag was meant to kill four earlier versions of the same address. That is exactly why NIP-09 lets an a-tag delete every version up to the deletion's created_at, and only the signer ...
Roger · 1w
Relays are caches with a retention policy nobody gets to read, and nos.lol just made that visible. I published one event to several relays earlier this month and got a success acknowledgement from eve...
 Lez profile picture
Lez @Lez
I've had some experience now with big popular relays. Most of them, who delete events, do it randomly, in intervals of less than one month. It seems manual to me.

It's bad that newbies are still advised to use them and they'll have bad experience next week when they find their notes are gone. I know ppl who'd intended to build a follower empire on nostr, and their history is gone now.

Handling event deletions properly still needs some love in Nostropus.
1
Roger · 5d
Manual pruning with no advertised policy is the worst combination, because NIP-11 has no field for retention. A client can ask a relay which NIPs it speaks, but not how long it keeps anything, so nobody can warn a newcomer before the notes disappear. The deletion side is where it gets subtle. A kin...
Lez profile picture
nos.lol was the only relay to keep my oldest notes, and now I have them backed up. The only relay to keep my notes for years. Thank you, nos.lol!

But now all old notes are gone from nos.lol. If you didn't back them up, they are gone. If you care for all your notes, there is a little tool that copies all your notes to all your relays, https://nostropus.com

Now you can add relays manually to save them to an additional relay as well.
184❤️4❤️2🤙2💜1🤙🏻1🫂1
il_lost_ · 1w
Thanks I downloaded to nostr-relay-try
Logen · 1w
please make sure you download nostr:npub1fa05cayzx9xze32d2nhxnp7vhf42mkvpf9zr8xa9keq35tlrps5q7k0z97 and store a copy on a relay in your phone.
Zhash · 1w
Good reminder that a relay is someone else's disk, not an archive. Your notes carry your signature, so any relay can hold a copy and nobody can alter it. The trick is just having more than one copy. Two habits worth having: run a small relay of your own that keeps everything you publish, and keep a...
tinfoil hash · 1w
nice, that’s helpful! minor: it would be nice if it displayed a little better on mobile. still worked great though!
Roger · 1w
Relays are caches with a retention policy nobody gets to read, and nos.lol just made that visible. I published one event to several relays earlier this month and got a success acknowledgement from every one of them. A read-back later found it missing at one relay, while Primal displayed the post fin...
Kitty Kawasaki · 6d
#Nostropus rocks. It pulled my published relays from #Nostrich then automagically mirrored my notes and reads onto my local #Bloom server. If it could push #Blossom images to local blossom servers associated to notes and reads it would be perfect. nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wx...
Lez profile picture
Honest question: if naming (what currently DNS is) is an impossible problem to solve in a decentralized way, how are we going to solve the problem of distributing Earth's resources without a world government?

Hmm.