🍁

The reason we didn't use kind 1984 directly is that the semantics are not quite the same. This is a request to the bot for flagging something, so you point to the note or npub and provide a suggestion explaining why. This is because:

We want our own vocabulary, NIP-69 (https://github.com/nostr-protocol/nips/pull/457), which is also friendly to automated reports. This is evolving, so it’s not marked as final.

There is a high chance we will choose something different from what is suggested, either from OpenAI's evaluation or our own manual selection. This is also a hint: we are not receiving a report kind; we are receiving a request for a report with different semantics than kind 1984.

Allowing user-provided inputs and just relaying them blindly for the anonymity functionality would make the Tagr bot appear to have a schizophrenic "personality." For example, both the victim of harassment and the harasser could use it, and from an outside perspective, the bot would appear to ban everything randomly without a consistent set of rules. The idea is to have many bots tailored to different preferences, and you follow those you like.

But I like the idea of a new kind. We are using plain JSON just because it was the more flexible initial approach while developing the service. Right now, we do the communication through NIP-17, so it's a kind 1059 wrapping a kind 13 wrapping a kind 14 with our custom JSON in the content.

I think what you propose is to have a new kind different from kind 14, right? Let's say kind 1986 "Report Request"? Currently, I like that we are fully wrapping the reported note inside the payload, so we don't need to fetch anything, but it’s not a big deal to have it as an e-tag for more consistency, although that increases the chances of not finding it.

So we'd be using NIP-59 wrapping this new kind. It would not be signed for the same reasons kind 14 is not, and also because all the requester identity comes from the kind 13, and we'd be repeating info.

There's more detail in the bot code itself https://github.com/planetary-social/reportinator_server

But keep in mind that there's also a google pubsub side of it that deals with openAI (maybe we should merge both in the future). The google pubsub side is https://github.com/planetary-social/cleanstr

I'd be happy to tell you more about the specifics if you want some more info

It's just a nip-17 private message with a predefined json structure that the bot can understand:

reporterText: just a free form human readable description on why you think it should be analyzed. Useful for potential manual processing.

reportedEvent: being the full event you are flagging. May be only analyzed by AI, if AI doesn't flag it, there's a manual inspection through a Slack channel integration.

Not focused on instagram really but nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch has stories similar to instagram, but we are not really focused on pictures first

Hola de nuevo nostr:npub1taxlq9y6ftm8gplqm9m3p73xxdephx9era3mcsdwk32cnq7rs5yqsyj2hl !

One of the techno gods https://www.youtube.com/watch?v=ZhZJqgQ_ZhE

Running Tidal

(but on web because I can't get the app from Uruguay 😢 )

https://tidal.com/browse/album/304166092?u

You may find this useful https://undocumented.nostrkinds.info

OP_CHECKMULTISIGVERIFY

You may find this useful https://undocumented.nostrkinds.info/

hmmm your are missing something here

No problem! Bitcoin articles from nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a should be there too https://www.lynalden.com/archives/

I'd read first https://www.amazon.com/Bitcoin-Standard-Decentralized-Alternative-Central/dp/1119473861 from nostr:npub1gdu7w6l6w65qhrdeaf6eyywepwe7v7ezqtugsrxy7hl7ypjsvxksd76nak and then https://www.amazon.com/Price-Tomorrow-Deflation-Abundant-Future/dp/1999257405 by nostr:npub1s05p3ha7en49dv8429tkk07nnfa9pcwczkf5x5qrdraqshxdje9sq6eyhe and most articles by nostr:npub1trr5r2nrpsk6xkjk5a7p6pfcryyt6yzsflwjmz6r7uj7lfkjxxtq78hdpu https://bitcoinmagazine.com/authors/alexgladstein

You may find useful this proposed nip from nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

https://github.com/vitorpamplona/nips/blob/relationship-status/81.md

Hey Greg at least use Primal that does the lightning wallet setup for you, just so we can thank you for the website

nostr:npub1uaajg6r8hfgh9c3vpzm2m5w8mcgynh5e0tf0um4q5dfpx8u6p6dqmj87z6 😢

We are seeing another surge of events at one of the nos.social servers, just in case checked stats.nostr.band and it matches https://stats.nostr.band/#daily_profile_events . I wonder if we are under some bot swarm attack as few weeks ago

Interesting! Maybe a moebius band vs 2d space would have been a more intuitive addition to the analogy