nostr:npub1jk9h2jsa8hjmtm9qlcca942473gnyhuynz5rmgve0dlu6hpeazxqc3lqz7 whatβs wrong with the note Ben posted?
the bug where the note shows up on the top of your feed til the timestamp in the future is hit, sometimes 10 mins other times 30 mins etc
cc: nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z (only happening with amethyst users notes)
Amethyst does send notes in the future if the user wants it like that.
ahh unfortunately Damus sees it the moment he posts it and not in the future timestamp that they desired, so it clogs up the timeline n remains on top until the desired timestamp is reached..
which is strange bc ive used shipyard to schedule notes in the future n this issue never arises
Shipyard is a DVM that actually posts the note (that you signed) in the future. π
Aaaaaaahhhh
why not do this instead nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ?
We can do that as well.
But virtually every client posts in the future if the user changes the date/time or the timezone of the phone. The receiving client is the one that needs to filter things out if they are in the future.
Makes a ton of sense!
Damus PR to fix this issue: https://github.com/damus-io/damus/pull/2967
This is huge Terry!! Thank you so much bro π«π«π«
nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9rhwden5te0wfjkccte9ejxzmt4wvhxjmckw6hsh give the man a raise!
Thanks sleepy - this is an unintended or at least undesirable consequence. Lets see what devs say
nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf thinks Damus might just need some timestamp filter logic π
& no prob! π«
