The guardian does have a semi-paywall in that you can either share your personal data with them or pay. Which in my opinion is a breach of the GDPR but apparently the UK ICO has said it’s fine. Yet another toothless/useless organisation
FYI. Ryobi has nothing to do with Home Depot. It's owned by a Hong Kong power tool manufacturer, and used to be Japanese (in fact, Ryobi still exists as a tool manufacturer, just not the power tool division)
Probably the reason they're not in any of the hauls is because they have a reputation for not being very good, and are harder to sell/fence...
This sounds very much like Apple being maliciously compliant. Similar to their complaint against Epic Games...
I'd be interested to see what the EU makes of this.
She says that she was doing a 3 month "ramp" - which I can assume is the induction period. She'd only got out of the ramp and started "proper" at the beginning of December, which is what (I think) you heard
I would say Bevy isn't really similar to Unity. Something like Fyrox - https://fyrox.rs/ - would be more similar. Bevy is more low level and lacks an editor (as of now, it's planned)
Someone who needs to start developing right now should use Fyrox right now. I tested the same project in both, and can echo the sentiment that Fyrox is further along and much more similar to classical engines like Godot, Unity or a number of further-along C++ engines.
Bevy breaks things every minor release and is missing key features. If more people supported the Fyrox effort, then the rust gamedev ecosystem would be less vulnerable to a change in bevy's pricing structure just as this Unity change has impacted the wider game dev ecosystem.
Not sure exactly how to do it (not used mercurial in a long time), but I extracted the repository tarball to a directory then used hg clone to make the code usable/readable
I feel like this would be better as a Well-Known URI, for example /.well-known/password-manager.json with similar format to the repo – That way it's not up to Apple to decide what goes in the repository
Sites would immediately use it to essentially disable password managers "for security." Sites have done everything they can to block password managers historically, I don't anticipate that changing.
You're asking the wrong person: Sites shouldn't do that. But they do, often.
Banks are the worst offenders, but it isn't limited to that. Any site that thinks it is "special" and requires "extra security" targets password managers for reasons unknown.