What are we missing?

Reply to this note

Please Login to reply.

Discussion

Have you seen what people like nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309aex2mrp0yhxummnw3e8qmr9vfejucm0d5hst8nxq7 and nostr:nprofile1qqszw70nm86zcl0wzlcwd0xulzdgl82e95v78vdm6fl0rnlarfle35gprfmhxue69uhkummnw3ez6un9d3shjtn5095h2tnc09aqz9thwden5te0wfjkccte9ekk7um5wgh8qatzetg02k are building using NIP-52, for example? Calendar events should all be interoperable with Nostr. There’s no reason to be maintaining multiple permissioned event databases for something so basic as event scheduling.

https://github.com/nostr-protocol/nips/blob/master/52.md

Yep. We have multiple working calendar apps now. There's no reason that OPA apps couldn't be calendar events published to the Nostr.

Sorry, you mean multiple that don't work? ;)

What doesn't work with Plektos? I built it because Troop and Flockstr didn't work. I've been using it just fine, but I could have missed something. Tell me what you can't get to work and I'll try to fix it.

I think that’s nostr:npub14wxtsrj7g2jugh70pfkzjln43vgn4p7655pgky9j9w9d75u465pqvagcye’s point. There have been a lot of false starts so far. We need a competent team to launch something that lasts. If OPA becomes the official calendar app for Nostr, that would be great. Keep the basic functionality free and turn it into a user acquisition pipeline for upgraded features.

Didn't check it for some time, looks nice! I will give it some tests and come back with feedback.

Thank you for your work! 💙

Thanks for share!

I couldnt have accomplished half of what I've done without your insights. Thank you for helping a newb along the way!