I pushed out a new version of nostrcal.com tonight that may end up breaking your experience if you've been using the site since I've rolled out PWA support. That's because I pushed out a new schema for our indexeddb that will store all the user's events to a local db. This allows for a faster loading on subsequent visits but also allows for use as an offline calendar if you have the PWA installed.

To fix you'll just need to delete any site data for nostrcal.com in your browser. Once you reload you'll just need to sign back in and it should start trying to save events to the db. Unfortunately this will reset any notifications you may have set on your local device.

Building block by block but we're starting to get the foundation down!

Reply to this note

Please Login to reply.

Discussion

This version should have very early support for NIP-53 live events that nostr:nprofile1qyvhwumn8ghj76rfwejhgctvdvhxummnw3erztnrdakszrthwden5te0dehhxtnvdakqqgpc0rv4mdac2np6p5aj66mmlxlj3vmpv2lxgvn025sm5uw08dz6dyvfhn64 had requested for the /events page. I say early because I seen the events on my localhost version but now I'm not seeing any future events now that it's live in production. Milage may vary but we'll get it working soon!

Oh it does seem to be working on /events after all. I need to go to bed lol. I was using wss://hivetalk.nostr1.com instead of wss://relay.hivetalk.org but when I added the right relay it was there. It does need some work to populate as a proper event. Clicking it doesn't load it for example.

By local do you mean browser cache or a local nostr relay (such as Citrine on Android)?

Right now I'm just using a local browser cache of calendar events for the user and notification preferences in indexeddb.