Not yet, I gotta figure out how to do that
nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr
Can list events be modified/edited/replaceable by most recent?
Discussion
Thanks! I tried to upload two gifs but then couldn’t find them after. Nostr search is where it’s at, right?
That’s right
I assume you added a search term and tried to search using that term again?
It may take a few minutes for the event to finally publish and be searchable
But I’ll look into it and get back to you because for some reason this function gives me trouble
Yes, tried same gif two different search terms.
Do you mind sending me the gif you were trying to post? You can send it over DM if you don't want to post it publicly
I just tested with my own gifs and didn't have an issue so I want to see if it's image specific (which was a problem in the past)
This was the GIF, how appropriate!
That was more work than expected, but I think I fixed it
It should work with MP4 files now
- updated the display page to render looped mp4s
- updated NIP94 publishing to create thumbnails/previews for videos
- assigned uploads their own hashtag for filtering "gifbuddyupload"
If you run into any trouble again just let me know
yes, any event in the k >= 30000 < 40000 is a replaceable event and should have a "d" tag as an identifier (preferably random)
https://github.com/nostr-protocol/nips/blob/master/01.md#kinds
I see
So in this case where nostr:nprofile1qyt8wumn8ghj7ct5d3shxtnwdaehgu3wd3skueqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqqgqw2gfz684etnwchf0ktq2l05wfzfdgc9xc9xy74ef2kd57afk8usm9px6j is asking to edit an existing collection:
The UI would call the latest collection, allow the user to add gifs and then publish a new event with a new/random 'd' tag that can be retrieved by it's latest "created at" time
Makes sense, thanks!
What's the point of the 'd' tag actually if it's just pulling the latest event?
Events in the k>=10000<20000 are replaceable by kind. So each pubkey only has one of them. A good example is the k:10002 events
Events in the k>=30000<40000 are replacable by "d" tag. So when a new event is published it replaces the old one with the same "d" tag. A good example would be the NIP-23 article events