Vertex on Nostr: Communities need curators. Curators need automated and configurable filters to avoid ...
Communities need curators.
Curators need automated and configurable filters to avoid being overwhelmed by a sea of spam.
We provide these tools
You don't need domain names to make Communities work.
I don't want to rely on one relay domain for Community IDs or the publication authority of members.
They bring all this obvious attack vectors and allow for about zero flexibility.
I want to able to optionally set, per content type:
- a fee
- a filter (think Vertex (npub1kpt…nhmz) etc...)
- a list of "roles" that can publish that content type
- a retention time
- exclusivity to that community VS interoperability with others
NIP-05, NIP-29, NIP-72, ... all don't even come close to allowing for that.
#communikeys do.
Published at
2025-03-25 07:18:16Event JSON
{
"id": "9e4c108266f60cce2deec116c5b3651edfc7583dcbc837d6fb103ac406900eb8",
"pubkey": "b0565a0d950477811f35ff76e5981ede67a90469a97feec13dc17f36290debfe",
"created_at": 1742887096,
"kind": 1,
"tags": [
[
"q",
"4b5bedc1db27ed745a040159961eb064c3b10aa6c935ea575d876c3183675e82",
"wss://relay.damus.io/",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"wss://nostr.wine/",
"Niel Liesmons"
]
],
"content": "Communities need curators.\nCurators need automated and configurable filters to avoid being overwhelmed by a sea of spam.\n\nWe provide these tools\n \nnostr:nevent1qvzqqqqqqypzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg3waehxw309ahx7um5wgh8w6twv5hsqgztt0kurke8a4695pqptxtpavrycwcs4fkfxh49whv8dsccxe67sgmud3sm",
"sig": "d270cc0f0580792f023d44e0c37ac57af81b1a6a6b223b05992b2c997fba9668a98b50bfb7ae4edfc1a3633f6d60eb65813be6586cbe0927d792f03622ab41e6"
}
