agnos.is Forums

@julian Sorry, yes, you're correct.

@shraga100 also check DNS records, such as DMARC, DKIM and SPF. Without these, your email will go to spam for sure.

@eeeee didn't we fix that here?

https://sudonix.org/topic/688/nodebb-and-emails/2

They appear on mine @cagatay but not on yours. Not sure why.

@dave1904 sorry. It's not core. You need to install nodebb-plugin-web-push and then you'll see the section I mentioned previously.

@dave1904 it's part of core - have a look under /me/web-push. If you use this, then you'll need to disable ntfy

@julian yes

@julian Yes, very, and their support isn't up to much either in the sense of wanting to fix it. I've had to change my VPN usage from machine level (which I prefer) to browser level - as long as the internet traffic is secured, that's good enough for the time being.

@julian Hmm - still not working for me...

EDIT - works on my Android phone, but not on my PC - guessing it's likely security software.
EDIT 2 - suspicion confirmed. It's caused by NordVPN. If running, the push notification doesn't work - if disabled, it works fine.

@julian when does 3.10 come out?

@julian thanks. I'll check this later.

@baris thanks. That setting is already on for me.

@julian Yes, I've done that, but can't seem to make it work.

@julian I'm using the GIT link you provided to install. Plugin installs fine, but cannot get it to send any notification - even on my mobile device which works fine for NodeBB?

@julian Is there a link where we can install the v4 beta version of this plugin? I'd love to test it out over on Sudonix.

EDIT - NVM - I found the link..

@julian understood. I now have this working on my phone at least.

Edit - and it works perfectly. I get the notification, click it and it uses my already open browser session to display.

@julian OK. Still no activity for me though despite updates here. Did you also remove ntfy as that isn't issuing alerts anymore.

A bit greedy, but this js would probably work

if ('serviceWorker' in navigator) {
  caches.keys().then(function(cacheNames) {
    cacheNames.forEach(function(cacheName) {
      caches.delete(cacheName);
    });
  });
}

Or perhaps this header

Cache-Control: no-cache,no-store,must-revalidate

Or this modified js

function async deleteCaches() {
  try {
    const keys = await window.caches.keys();
    await Promise.all(keys.map(key => caches.delete(key)));
  } catch (err) {
    console.log('deleteCache err: ', err);
  }
}

// run this function on your app load
function resetCacheForUpdate() {
  if (!localStorage.getItem('cacheReset')) {
    deleteCaches()
      .then(_ => {
        localStorage.setItem('cacheReset', 'yes');
      }) 
  }
}

Source

https://jun711.github.io/web/service-worker-cache-busting/

@julian doesn't seem to work for me even with cache cleared.

@baris thanks for this. As well as understanding the genesis of each cache level, it's also useful to understand how it works from the code perspective.