5 ms·
Go to about:serviceworkers and ctrl-f twitter and remove every instance. That will fix it.
by miffe 6y ago
Go to about:serviceworkers and ctrl-f twitter and remove every instance. That will fix it.
- matsemann 6y agoYup, that fixed it for a few days at least last time. The issue about the whole page being inaccessible. The issue with the page loading but not the tweet is still ever present..
- untog 6y agoIt doesn’t answer how Twitter can be so bad at this, though. Looks like a like of us have experienced this for a long time, I’m mystified why they wouldn’t fix the bug.
- dTal 6y agoTIL about service workers. So there's a persistent cache of javascript that can't be cleared except one at a time? My cache is full of fly-by-night websites. Surely this is a shocking privacy hole? Web browsers need to be more transparent about what state they are storing, and more accommodating of attempts to clear it.
- kalleboo 6y ago> Surely this is a shocking privacy hole? Also a performance/battery suck. Apple refuses to implement it in Safari, and it's one of the big reasons web developers deride Safari for being "the new IE"
- GoblinSlayer 6y agoAs I understand the docs, they can be killed any time, e.g. when their site is left, then they aren't different from page scripts. Well, it doesn't look like they solve any problem either.
- detaro 6y agoThe most crucial thing they solve is giving websites access to their cached pages, and they can thus show cached content while also making a request for new data in the background, still provide cached functionality while the device isn't connected to the internet, ... In the wider concept of "PWA" (Progressive Web Apps), they also are used to enable webapps to act a bit like local apps if the user opts in - a user can add them to the homescreen, and they then are launched just like normal apps (but still sandboxed in the browser). An example that does this quite well is the Web-IRC client "The Lounge" - you can open and use it in the browser, but also pin it as a standalone app, including support for push notifications etc if you allow that.
- dTal 6y agoWell, except there's nothing stopping a site from handing out a unique service worker with a hard-coded i.d. to every visitor. It's persistent state with behaviour, like a cookie that can do things.
- detaro 6y ago> Also a performance/battery suck That's far from obvious. Good cache control and offline usage are great for battery usage. > Apple refuses to implement it in Safari Wrong, Safari supports them. What Apple doesn't do well is enabling webapps that you pin to your homescreen ("PWAs") to work (they allow it, but from what I hear it's buggy and has weird restrictions), because they'd rather force you to make a native app.
- account42 6y agoYou can have good cache control with HTTP headers, no need to run scripts on the client for that.
- gruez 6y ago>Surely this is a shocking privacy hole? AFAIK it's fine because they get cleared when you delete cookies/site data, so it's no worse than a site using localstorage, for instance.
- Isthatablackgsd 6y agoMe as well, I look up about service workers. I agree with the transparency, I was not aware about service workers until this post. In the meantime, there are Firefox/Chrome extensions that manages the service workers. Those extension can block service workers from installing without the user consent which that was nice.
- wasmitnetzen 6y agoThe Cookie AutoDelete extension has an option to delete them. I'd highly recommend having that extension anyway!