not sure how it would work. probably a service worker that (re-)connects to relay once in a while (1h?) and shows notifications if enabled: direct messages, text notes from certain pubkeys, chat messages.
makes sense to do this after #15 so that when a user taps a notifications on the phone, it always opens the same instance of the webapp, as opposed to a new web page every time.
not sure how it would work. probably a service worker that (re-)connects to relay once in a while (1h?) and shows notifications if enabled: direct messages, text notes from certain pubkeys, chat messages.
makes sense to do this after https://git.qcode.ch/nostr/nostrweb/issues/15 so that when a user taps a notifications on the phone, it always opens the same instance of the webapp, as opposed to a new web page every time.
would be nice if "enable notification" is an opt-in config in the setting view. otherwise the user gets prompted with "nostr wants to show notifications" on page load, which could be a bad first impression.
would be nice if "enable notification" is an opt-in config in the setting view. otherwise the user gets prompted with "nostr wants to show notifications" on page load, which could be a bad first impression.
not sure how it would work. probably a service worker that (re-)connects to relay once in a while (1h?) and shows notifications if enabled: direct messages, text notes from certain pubkeys, chat messages.
makes sense to do this after #15 so that when a user taps a notifications on the phone, it always opens the same instance of the webapp, as opposed to a new web page every time.
would be nice if "enable notification" is an opt-in config in the setting view. otherwise the user gets prompted with "nostr wants to show notifications" on page load, which could be a bad first impression.
of course, it should be an opt-in setting.