No actually they didn’t amplify anything. They made it 10x harder to manage because none of those events are actually published by the host. They are published by OPA’s key, so they are completely separate & distinct events, which the owners of said event don’t know about, and the potential attendees who may register are just flowing in limbo on a registration list nobody is going to check
And even if the events are “claimed” by the host, (a) the Nostr calendar event itself is not assigned to the event host, and (b) even if that was one day solved, it creates another problem which is the host then needs to manage two separate registration lists.
We did this 9mths ago, and deprecated it because of these very reasons.
If we’re gonna do it, we do it right.
I have to hardily disagree here. nostr:nprofile1qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqypnyupc0uf08dhwwlf2f98qdushv45ypqzf4ql3ymerzyp63ekm65u5nzvk adding their events is a huge win regardless if the host publishes or not. It seeded a huge amount of data to nostr that just wasn't being published before. They could drastically improve by letting their users give them their npub within the settings of nostr:nprofile1qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqypnyupc0uf08dhwwlf2f98qdushv45ypqzf4ql3ymerzyp63ekm65u5nzvk and if a user has a listed npub use that npub as a p tag to show them as the host but that doesn't diminish that it was a huge win regardless.
It doesn't really matter who creates the event. Most nostr livestreams aren't pubished by the actual streamer. They are determined by the p tag of the listed event host. As for managing two lists it would be easily for OPA to just import the same public nostr data into their own DB to let their users manage their event directly in their own ecosystem over OPA+nostr.
This. Just make it work. Then Make it good later.
Thread collapsed
Thread collapsed
