@captainepoch There's a big difference between supporting v3 and phasing out v2. Firefox already supports Manifest v3.
Mozilla's implementation is not restricting adblockers in the way Chrome does.
Criticizing Firefox here is also something I just don't understand. The only thing it will do is making Chrome users doubt and not move away. It's time to move to protect the web.
In my adventures about Time in Programming, and specifically #PHP, I always thought that timezones were part of the system files, not part of PHP itself.
This was wrong, as I found out while reading the timezone database mailinglist, where @derickr posted the following:
“I have just updated the tzdb for PHP, and one of our tests started failing”
I'm loving how deep the hole of 'time in programming' is.
So, my talk will be about time, and one of the big things is that a lot of developers save into UTC all the time. But, that doesn't actually work in all cases, and it made little Tommy late to his appointment.
I'll be diving into the problems with time, how to avoid them, and fun things like timezones, clock psr, clock component.
@ocramius It's actually quite a cool project. It's software to run a lot of different sex toys the same way, so you can use open source software to control it.
Of course, it's also quite funny, and the name is perfect.
@Schrank
Firefox Multi-Account Containers, it's basically 'profiles', which means you can have a work account logged in in one tab, and a private account in the other.
uBlock Origin, for blocking ads, of course.
Consent-o-Matic, automatically disagrees with most cookie popups.
And of course, your favorite password manager.
Changing settings isn't needed, but right-click the Pocket button and remove it. And if you like darkmode, you can enable the dark theme in Settings.
I just started a plain typescript project, and was too lazy for a docker setup so I just installed Node with apt and went on my way.
I installed Typescript, that went fine, but when trying to use it it gave a vague error.
Quick search fixed it, but... I'm amazed by the cause: Typescript didn't support the version of Node I had installed, which sure.. That's okay. But why didn't NPM tell me this? NPM does not have node version constraints?!?
A line which will also stay closed forever. Connection to Mönchengladbach can be better done from Venlo, and nobody wants new trains through the forest.
Basically, you shouldn't expose the vendor directory, but a lot of sites did this anyway. There was a file in PHPUnit which if it was public (which the maintainer never expected to be), you could execute code.
