@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.
Some of you know, I'm learning to control a windmill.
Have some pictures of the brake of a windmill.
Pulling the rope slightly and then letting go of it slowly will drop the beam, which will move the beam so the circular beam around the rotating wheel gets tightened.
discovered livetechhelper.com, while the initiative could be positive explained, the execution is horrible! I found https://livetechhelper.com/repos/jaapio/phpunit
I can help with #phpunit but obviously any income should go to the original maintainers not to me because I created a fork!
Same applies to other projects, should we stop this?! #php#foss?
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.
@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.
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.
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?!?