Ademan

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

nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsz9nhwden5te0wfjkccte9ekk7um5wgh8qatz9uq3kamnwvaz7tm8d3jkzum0deshgmmj9ejx2a30wfjkccteqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqq3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnwsm55dju 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?!

nostr:nprofile1qyg8wumn8ghj7mn0wd68ytnddakj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qgkwaehxw309aex2mrp0yhx6mmnw3ezuur4vghszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qpqu6j0u5aakylx0qp2wl8g0rmvfhhlp4vdl8f3g23n8wfqgx4faw5q995t87 How long have you been on dreamcasttalk?

nostr:nprofile1qyvhwumn8ghj76rzwghxxmmjv93kcefwwdhkx6tpdshsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tm9v3jkutnwdaehgu3wd3skuep0qyg8wumn8ghj7mn0wd68ytnddakj7qpqjlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qs6ulkk 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

nostr:nprofile1qyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzemhxue69uhkummnw3ezumtfd3hh2tnvdakz7qghwaehxw309ashgmrpwvhxummnw3ezumrpdejz7qpqjlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3q0rmwe9 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).