What is the status of NIP-59 support among relays? > To protect recipient metadata, relays SHOULD guard access to `kind 1059` events based on user AUTH. When possible, clients should only send wrapped events to relays that offer this protection. > To protect recipient metadata, relays SHOULD only serve `kind 1059` events intended for the marked recipient. When possible, clients should only send wrapped events to `read` relays for the recipient that implement AUTH, and refuse to serve wrapped events to non-recipients. (Yes they're not REQUIRED but they improve privacy) #asknostr

@Alex Gleason Do you recall if Truth Social has an API and/or exposes the old masto API? (and if I'll get b& trying? lol)

#asknostr Is there any NIP that specifies to put a json *object* inside an event?

Lol what is a kind 1111?! What is 1 not good enough for ya anymore?!

@BaronBurdock How long have you been on dreamcasttalk?

@hodlbod sorry to be obnoxious but I shot you a DM that's semi time sensitive. (not any kind of security issue)

#FreeRoss Thank God he's free! Now if only we could free him from this new sentence...

Not a big fan of the "it's just concatenation" line of argument

@hodlbod did you fix something with caching websocket connections or something? Over the past month or so I stopped using coracle (and nostr) because I was being assaulted with 22242 signing requests, and now I'm not (or at least it's tolerable now).