pull down to refresh

I've been talking about this for weeks now. The only reason I don't use the cross-post feature is because it doesn't use kind 1. Many clients don't support long-form content.
I don't have the technical know-how to have any idea what a kind 1 is... But if we get a easy share to Nostr button out of it, then it sounds great to me.
reply
42 sats \ 0 replies \ @mo OP 12 Mar
Kind 1 it a tipical nostr note, like a tweet
reply
Cross-posting is already available on the SN, but it's in the long-form content format. As I mentioned in my response to the AG, some clients don't support it
reply
21 sats \ 4 replies \ @ek 13 Mar
The issue is that kind 1 does not support edits but we have plans to use presigned events. When events are presigned for every edit, we should be able to broadcast the final state for you after the edit timer ran out. Then we can use kind 1 in a way that harmonizes well with SN's UX and features.
This requires some architectural changes though since currently, your browser is broadcasting the events as is done by "normal" nostr clients.
reply
This could be a really dumb idea... But could you not put a delay on the crosspost. So that once the edit timer is over and the post is set, then it actually crossposts?
reply
42 sats \ 1 reply \ @ek 13 Mar
No, this is not a dumb idea, this is actually exactly what I meant with what I wrote above, just with more technical terms :)
We need presigned [kind 1] events so we can delay broadcasting them and that you don't need to be online when the edit timer ran out.
reply
\o/ a win is a win. My brain dun a good enough. 🤣
reply
21 sats \ 0 replies \ @mo OP 13 Mar
Does not make sense to post items as kind 1, as long-format it makes much more sense and it alights with SN values. Otherwise, this place will turn like X.
I was referring to comments: something that could be done instead of publishing immediately, the comments could be posted after the 10min expire. In this way no more edit everywhere. This will also bring people to SN as the conversation main thread is happening here.
reply