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 @nprofile1q... 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.
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 @nprofile1q... 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.