Sonic Frontiers looks good.
Live testing noscl. 🤞
Posting from Damus. This client works, can confirm.
I read the Activity Pub spec again. It's still a non-starter for me.
I have a directory of status updates in plain text files which are displayed on my website. I am thinking of hosting a read only nostr relay that allows you to subscribe to all of these. I'm not sure it's worth the effort tho. Perhaps I just read a relay to display all my current statuses instead.
I didn't lose my keys.
If kind7 defined "reaction" and the body was reaction itself (an emoji/code/etc.) this would allow for greater utilization. What points are there against this method?
Could reactions be it's own NIP or just a single UTF-8 character body of a NIP-01 reply which is recognized by clients? Additionally could there be a NIP for event amend like how there is for deletion? Would it address the Twitter edit button scenario?
That was kind of along the lines of what I was thinking. It is a little archaic though 😁.
There are other ways to handle this, but yea client implementation.
This had the effect that users would just reply to their own tweets because they couldn't post long form content (or worse screenshots of text). It's not easy to read or good technical implementation. And as is tradition, people will post without thinking.
I'd only be worried about a length greater than a hundred kilobytes? Allow the client to deal with the display mechanism.
Other than the notepad, these examples make sense to me.
An arbitrary restriction by Branle? Or did I miss it in the spec?
Please give me more byte length.
Seeing usage of the Nostr protocol for purposes outside of text communication such as personal notes, crypto, & tic-tac-toe is neat but misaligned with the original goal (IMO). I think defining/accepting too many NIPS will hurt the simplicity in the long run; be careful.
Forewarning: everything I do on this public key is a test and may regen at some point later. How much do I trust these random web apps 🤔