second night in a row trying to view 
and it just returns a white page. caching old fingerprinted assets on an index.html r something?? cc: @DanConwayDev 
GitWorkshop.dev
Decentralized github alternative over Nostr
Thread
Login to reply
Replies ()
some combination of time, clearing cookies, and hard refreshing resolved it.
I tried a few months back and found it unreliable.
@ben thanks for the report. I thought this white page issue was related to a tempory PWA corruption I introduced for users who visited the page during a windows of a few hours when I initially introduced it. I can see now this is happened on persistently on Firefox. I'll look I to this in a few hours.
🫡 thank you! it sounds like you can repro but lmk if you want any testing
Thanks. I've actually justed picked this message up now (i somehow misted your note from 3 days ago) and I'm afk. I reproduced it in chrome based on the troublesome build I mentioned. I'll try and reproduce when I can get back to the keyboard.
I can't replicate this. I also tried rolling back and forwards with various with a dev preview and couldn't replicate any issues. What Firefox build are you using? I've tried librewolf and 145.0.2. Can you replicate it on gitworkshop.dev now even after you unregister the old service worker? Does it also happen on vnext.gitworkshop.dev?
tested on 145.0 64bit. still seeing the same behavior:
1. go to
2. observe white screen
3. console > application > unregister service worker
4. refresh page (works)
5. refresh page > back to white page and console errors
it does NOT happen on vnext!
GitWorkshop.dev
Decentralized github alternative over Nostr
Does this happen I'm a fresh profile? I'll try it on this version but I suspect there is something else being cached somehow that's causing this issue.
I cannot replicate this on 145.0. vnext.gitworkshop.dev is now at the exact same state as gitworkshop.dev. does it now have the same behaviour? does a fresh profile fix it?
my guess is my local state got corrupted somewhow. after logging out then going through and manually clearing local storage, indexdb, cookies, and everything else I could find, it's now working as expected!
A hard-refresh works every time for me.
yes, a hard refresh is the work around i have been using too
So you're getting this too?
Was it a PWA before? Do the site has service workers? Uninstall them under the Application tab in DevTools.
I made it a PWA a month or so ago, clearly not as successfully as I thought.