I once implemented a WebDAV server in PHP. The standard isn't that bad and clients are more or less following the standard. It's still horrible how they are doing that. I saw behaviors when opening a single file like:

  - does / exists?
  - does /path/to exists?
  - does /path/to/file exists?
  - create a new file /path/to/file.lock
  - does /path/to/file.lock exist? 
  - does / exist?
  - does /path/to/file exists?
  - lock /path/to/file
  - get content of /path/to/file
  - unlock /path/to/file
  - does /path/to/file.lock exist? 
  - remove /path/to/file.lock

(if not exactly like that it was at least very close, that was either Finder on OS X or Explorer on Windows). Without some good caching mechanism it's hard to handle all of the load when you get multiple users.

Also the overwrite option was never used. You'd expect a client to copy a file, get and error if the target exists, ask user if it's ok, send same copy with overwrite flag set to true. In reality clients are doing all steps manually and delete the target before copying.

It was satisfying seeing it work at the end, but you really need to test all the clients in addition to just implementing the standard.

Well the PHP from 20 years ago was much better than the from 25 years ago. But there have been a lot of nice additions since then, including the last 5 years.

Everyone trying to access a site behind Cloudflare is forced.

Then you make a complaint to the company whose site you cannot access...

But then there are packages like htm that are doing basically the same thing with just tagged templates.

The language doesn't really matter much. I think I keep using PHP as in the years before.

You'd think they've done it on purpose so you don't watch Youtube on TV. I tried but it's so bad you'd never open it a second time. And that's the platform where there are no ad blockers, so it must be good for them ...

They have released 100% of the source they have.

I had being using krypton, with the private key being on my iPhone, and am now using secretive. Never had much of an issue with not having access to my private key. We made rolling out public keys to the servers very easy by using the gitlab key file. So when I get a new Macbook I'd just need to create a new key and upload it to gitlab. We have multiple devops that can run the playbook to roll it out to the servers. And if they have a new Macbook I roll it out for them. And we don't have that many Macbook upgrades anyway.

> Great to see this finally. It’s obviously the way it should have been implemented from the beginning.

It was on its way to get implemented and then Microsoft enabled it by default in IE10, so not making it the choice of a human, and ruined it for everyone.

> you can have a linter forbid it entirely if you like.

It would be better if that would be the other way round "linter forbids it unless you ask it not to". Never wrong to allow users to shoot themself in the foot, but it should be explicit.