hodlbod

> As far as I know filter.nostr.wine has paths for each pubkey and relay.nostr.band has paths for nip32-labeled content. I know about those, I'm more wondering what an example of...

This seems fine, but I also feel a little nervous about tagging people in reports who don't have anything to do with it. This could be misinterpreted pretty easily, and...

Getting normal users to create these is a different issue from defining them for people who do want to create them. I agree that there is plenty of signal in...

Informal use, refined over time through experimentation is the way to go IMO. Describing trust is as complex as language itself, whose goal is to communicate meaning. Meaning doesn't fit...

> Are other nostr collaborators fine with the fact that there would be no synchronization? No, I think synchronization needs to be solved for this to become the de-facto messaging...

Just to throw my oar in here, I believe the default for intellectual property is "all rights reserved", regardless of what the protocol you publish it to says. A license...

Check to make sure those kinds aren't used anywhere else, they seem pretty likely to have already been nabbed. Also potentially of concern is location privacy, this pretty thoroughly doxxes...

Sure, but that wouldn't solve privacy problems for publishers of kind 21s. The only way to do that would be to encrypt the note for desired recipients. Obviously not feasible...

> kind:pubkey:eventid This would be ambiguous, because you don't know if the event id is a d tag or an id. I also don't like putting `nevent` in tags. Another...

> the devil on my shoulder Mine says the same thing. It's _sort of_ a breaking change, but in reality it won't break anything. I say we YOLO into it.