Michael Dilger

I would have done something like this if I had come to nostr early enough to change this aspect of it. I would have also made it binary. In fact,...

As a data point, in chorus/pocket I coded what Staab describes in this comment above: /nostrability/nostrability/issues/38#issuecomment-2120827062 kind 5 events with 'a' tags delete only events before the deletion event.

I think we should keep NIP-04 to document how that works because we cannot make all the nostr clients stop doing it, and there are many nostr clients now. Marking...

BTW gossip ticks both columns now.

What branch/commit are you building?

Your build is not considering the file `.cargo/config` which enables the tokio_unstable config flag. That is why the task 'id' logic is missing. Search older issues I think I've answered...

The full-featured build command (from the README) is this: If this isn't working let me know, but it looks like you didn't include "--cfg tokio_unstable" ``` RUSTFLAGS="-C target-cpu=native --cfg tokio_unstable"...

I think it already is. It is on my system. I must have misspoke up above.

I have implemented ram-only storage of events. Ram-only storage of media probably isn't going to work (people will run out of RAM pretty quickly) so I setup a temporary directory...

Clarification: The event is correct, it has an 'a' tag reference. This is about ~~the feed picking it as a root note (wrong), and~~ rendering of the note (ought to...