pull down to refresh

Hmm yeah I'll look into this today and try to replicate
We found the issue. We thought it's kind 1 events but it's actually kind 30023 so they don't show up on "normal" nostr clients but on clients like habla.news. This makes sense since kind 1 does not support edits but kind 30023 does.
So there is no problem with your code, just with UX.
update: to be fair, it was @Thawne here. And he's right, we should explain it better that these won't ever show up in clients like Primal or Snort afaict.
reply
Ahh ok yeah that makes sense I think some more clients like Damus and Primal are starting to support reading in 30023's but it's mostly web clients still.
I wonder if there's a clean way we could give people an option to crosspost as a kind 1? We would need to enforce a character limit and append the title to the top of the content field if the user selects that option but it could be done pretty easily.
reply
30 sats \ 1 reply \ @ek 31 Dec 2023
Maybe also post as kind 1 after they can't edit anymore (after 10 mins)? For this, you would need to queue a job for the worker.
Also wondering if we should limit this to posts. As it is, I don't think stackers would want to crosspost comments without context.
reply
We would need to enforce a character limit and append the title to the top of the content field
Oh, didn't acknowledge this. Is there a character limit for content of kind 1 events? I see that they are called "Short Text Note" but I can't see a specific limit in NIP-01.
reply
deleted by author