RE: https://mstdn.social/@TechCrunch/117496494257224026
Seven years after I first used a folding phone ... #oldNews :-)
8 results for “sxa”
RE: https://mstdn.social/@TechCrunch/117496494257224026
Seven years after I first used a folding phone ... #oldNews :-)
IMHO It's particularly sneaky that they don't do the detection and at least warn you during the sign-up process ...
Cc @ben
While it crashed the browser after a few seconds the first time I fired it up, I've now got the #f1 Magny Cours 2000 race streaming on the service on Firefox/Linux after setting "general.useragent.override" to "general.useragent.override Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/156.0.0.0 Safari/537.36 Edg/156.0.4314.42".
Sure there are plugins for this but I try to keep this machine fairly clean.
Got a monthly subscription to "F1TV Access" on the official Formula 1 web site (The cheap one at £2.29/month to try it out). Due to the contracts that F1 has with Sky in the UK that's all I can do without a VPN, but it gives you access to full race footage over two years old.
However ... they have quite severe restrictions on web browsers it'll work in and it refuses to load if it thinks you're on something not in their list. No Linux. No Firefox.
This sounds really careless on Google's part ... https://www.theguardian.com/environment/ng-interactive/2026/oct/22/finland-google-felling-trees-datacentre
This sort of message is so frustrating. I'm logged into an account on the web site and one particular page gives me this.
Happens in a brand new session so it absolutely is not related to rogue #cookies
Resharing this chart from Rafael on the number of high-severity reports fixed in the last ten security releases on #NodeJS. This is the way of the world now - you need to keep yourself patched especially if your software is exposed to the internet.
RE: https://infosec.exchange/@mttaggart/117482947799206003
TL;DR While you should probably update your PHP instance where possible, there's a surprising lack of real working exploit code kicking around.
"The second [log4shell/Shellshock/Heartbleed] made the news, there were botnets doing the rounds causing damage [before LLMs]" - https://eliastaylor.com/noexploit/
The #NodeJS security releases that came out yesterday also fixed high severity issues. In 2026 you need to keep any system exposed to the internet fully patched otherwise you're running a real risk.