Took a break from my monster refactor and built a proof of concept personal/social calendar app based on nostr:nprofile1qqszw70nm86zcl0wzlcwd0xulzdgl82e95v78vdm6fl0rnlarfle35gpp4mhxue69uhkummn9ekx7mqpzdmhxue69uhhyetvv9ukzcnvv5hx7un8qyf8wumn8ghj7ur4wfcxcetsv9njuetnkylmgk 's NIP 57 draft.
https://calendar.coracle.social/
It's extremely minimal right now and basically useless, but I'd like to add an agenda view, as well as the ability to share/invite/join events. Unfortunately I probably won't have time to maintain the project, so if anyone wants to fork or contribute, have at it!

I love that the nips repo has 126 open pull requests
Could be relay connection status, I'm working on improving that. Make sure you have your relays set to publish in settings too.
The real algorithm was the friends you made along the way
Playing around with nostr:nprofile1qqszw70nm86zcl0wzlcwd0xulzdgl82e95v78vdm6fl0rnlarfle35gpp4mhxue69uhkummn9ekx7mqpzdmhxue69uhhyetvv9ukzcnvv5hx7un8qyf8wumn8ghj7ur4wfcxcetsv9njuetnkylmgk 's NIP 52 on https://zap.stream/naddr1qq9rzd3c8ymnzwfkxcusygyhcu9ygdn2v56uz3dnx0uh865xmlwz675emfsccsxxguz6mx8rygpsgqqqwensngc4x7
They underestimate how much this is going to trigger some Christians
It's really humbling how many developers on nostr are better programmers than I am.
Nostr is #rad
You keep this up and you're going to have to apply for a grant to be nostr devs' full time marketing department.
I said someone, not everyone! Thanks though
No better way to get some attention if you're a dev and feeling lonely
Can someone respond to this note? Testing something
Hey nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyfhwumn8ghj7un9d3shjctzd3jjummjvuc79cjs , finally got around to listening to the CD episode, congrats on the funding and thanks for the Coracle mention!
Obviously I'm happy you've also open sourced Primal, and it's clear from the discussion that you're approaching things the right way.
I do have another criticism/question though: why create a proprietary caching service rather than augment the existing relay standard via NIPs? I drafted COUNT back in March (I think), which was sort of an initial foray into making relays work for advanced use cases. I've written a few blog posts on the topic, and I'd really like to see relays come into their own, maybe via some kind of routing layer that allows users/clients to find relays with the data and functionality they need.
I'll just be over here building
