Thread

Issue appears to be that Divine consumes content from all of Nostr, but have applied their own content policy. So anyone posting content on Nostr, that appears in Divine (since they don't have their own special tags or events), will get hit by swarm of users reporting content according to Divine policy rules. nostr:nevent1qgsp0c5gn7aqzqsaqj9p8lgt5yy26vwrsvnzj4rqcg0xn3pl4ra729gqyqqqqgkns3le6t8ehu9jju0t0v362at4atga66e4jhq55chxq0ftsdyu5yw

I'm so annoyed by my own typos and mistakes such as "it get's worse"... "it get is worse"... 😂 Should be: "it gets worse". Thanks!

We're tweaking the moderation and content warning system, right now it's flagging a bunch of things as adult content which are clearly not adult content. Divine is using the extension to nip-71 that Vitor and I came up with in terms of just a replaceable event type so you can edit the metadata about the content. You can use it for any content you want, including AI generated content. We are using the client tag, you can filter out divine content from your client or your relay if you want. We're not pushing the divine events out form relay.divine.video but i think there are folks running scripts that share them beyond our relay. The filters for the divine app is we check and label any content uploaded to our blossom server or from events on our relay. We do let you add your own blossom server and change the relays, but we'll indicate that you're outside of the divine experience and in the broader open nostr ecosystem. In the divine app, we're going to have it use labelers we provide, but with settings to choose others. I honestly don't expect these choices to be very appealing to existing Nostr users and would encourage folks to consume the content with other clients. We are curating what goes in our relay and our media severs. If you're not keen on how we do it, use other clients or use the open source divine app and make a version with different choices. I'm not planning on changing the nip-56 tag to other, i think 'ai-generated' is a useful tag of content and if a second app supports it i'll submit a PR to update the spec. Innovation in nostr is not based on strict support of the spec, each app supports it as they choose, with a few core elements. If we don't extend it, try new things, add extensions, then Nostr won't evolve. In ATprotocol they've got strict schema validators and their relays and appviews will not accept signed events that don't fit pre-approved schemas. That's not really the Nostr way. There is no central nostr standards authority to complain to, it is a permissionless network. We will see a lot more folks get upset like you are at seeing content reports until nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqelpt5w changes Amethyst to show content reports as a content report label. Right now it shows up as if it was a comment. If you don't want to see them, stop using the divine relay, use a client that doesn't display labels that way, or contribute to amethyst to change it's behavior. I don't really love that decision decision, but I do support each nostr app developer making their own choices about how to interact with the network.

nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9ekxzmny9uq3zamnwvaz7tmwdaehgu3wwa5kuef0nw62p3 you are misusing nip 56. Nip 56 is for reports that relays need to act on. If you are just labeling content, please follow the nip and use nip 32 labels instead. Remember, all web of trust systems on nostr are punishing all reports severely. Your users are getting downgraded everywhere.

"The spice must flow", events will flow anywhere. I want (wanted) to support Vine-style content, both for consumption and creation, but there needs to be a solid way to differentiate the content. Relays are dumb, they grab anything. So anyone can make a small script that replicates video files from all other relays and sends to Divine. That would take 5 minutes effort and create a little bit of chaos. Client tag is not a good solution, then we go backwards in time when web browsers was using fake browser agent to trick website to render their website anyway. Should I fake my client to be "divine" so it's shown in Divine? I don't think that is a good solution. "The filters for the divine app is we check and label any content uploaded to our blossom server or from events on our relay." Just as short video events flows everywhere, so will reports. At least it would help if you kept reports to your own relay, but reports get sent to the original posters relays as well. Then at least I wouldn't see those reports unless I explicit used your relay as my account relays. "We are curating what goes in our relay and our media severs. If you're not keen on how we do it, use other clients or use the open source divine app and make a version with different choices." You are fully free to curate what goes on you relay and media servers. I'm interesting in support the short form content and I can add the same content policy, but right now there is no difference between "divine" content and "nostr" content, yet you are encouraging all your users to report content that violates your content policies and police these policies and this affects the broader Nostr network. If you want your own isolated content network, then do so, you can still use Nostr, but come up with some special tag or kind, or anything that makes it possible to filter out on relays. "If we don't extend it, try new things, add extensions, then Nostr won't evolve." Extend it then, don't abuse it. Do it in your own living room, don't go into other people's living room, make a mess and tell it's their responsibility to clean up your mess. "I'm not planning on changing the nip-56 tag to other, i think 'ai-generated' is a useful tag of content and if a second app supports it i'll submit a PR to update the spec." "ai-generated" is not a useful content reporting tag. It will never be part of NIP-56. Should we punish Nostr users for posting AI content? There is nothing wrong with AI generated content, reporting should not be used for it at all. Do what nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqelpt5w suggested and label the content, don't report it. That's the abuse here. And no, don't change it to "other", that would really be problematic and leave everyone without any option to filter. "Innovation in nostr is not based on strict support of the spec, each app supports it as they choose, with a few core elements." Then add something to the events created in Divine that separates it from other NIP-71 videos. Follow your own ideas, don't simply invade the space of others and tell other's that it's their problem. I can't post any NIP-71 videos anymore because of the risk of being massively reported. "We will see a lot more folks get upset like you are at seeing content reports until" Seriously? You're going to continue this practice and not do any changes? You asked the broader community of Nostr developers to help you with inflow of a lot of users, even I reached out to help. "If you don't want to see them, stop using the divine relay" Nostria shows reports and blocks content for the users. I had to add validation of the report type now to avoid showing your "ai-generated" reports, since it made a lot of content appear reported. You already took my WOT ranking from 100 to 95 with one single amazing video I uploaded. Is your goal to ensure I cannot take a job at ZapWork eventually, because I sometimes make AI content? "I don't really love that decision decision, but I do support each nostr app developer making their own choices about how to interact with the network." You don't love the decision that instead of "extend and embrace", which would be perfectly fine for your app, you won't change your app and instead will continue to add censorship pressure on the behavior of people on Nostr in general? Resulting in lowered Web of Trust score for anyone who don't follow Divine and Apple content policies on Nostr? You're misusing NIPs and asking everyone else to update their software? Be better than this.

I just checked out your Safety Standards, appears you've extend the NIP-56 even further than just AI: "Misinformation: False or misleading information" "Copyright Violation: Unauthorized use of copyrighted material" Use labeling for this, not reporting.

whitelist standard report kinds and discount this trash

oh, also this is an attacker, they have WoT standing by deception. attack this, don't let them maintain the upper hand. offense is the best form of defense. report the reporter

nostr:nevent1qqsyeppea8zemzaytqyx6g2syl87css0e59s8pzn6wyglkmsmt7agmgppemhxue69uhkummn9ekx7mp0qgsx3zc2wys3pvx0y4y00pk7c332m8l4w79yvfkyluy5fyqh3myyw8crqsqqqqqp9jpjlx