It's just an older design from a more innocent time, newer specifications don't allow this, but to maximise compatibility Bluetooth stacks left the new behaviour off.
The pr seems to suggest it's not the filename though given the new file was named the same and didn't crash.
I would guess grammarly is hooking chrome and potentially trying to read metadata about images, and the particular gif had metadata in a format they hadn't expected.
Issues don't mean downtime though, and GitHub has lots more features. For example an issue noted here was stale commits of up to 7 minutes in 9% of new pull requests... I'm willing to bet such issues aren't acknowledged by most platforms
Sure, but where does the energy come from to actively remove? Because that's usually the point, the energy creation created more than the removal removed.
I mean, if you abuse formatting enough I suppose... although I will say, the pipeline/bind operator has been in proposal for a decade at this point.. it's depressing that some version hasn't shipped, because C# extensions and similar in swift can really help shift how from what.. it* could really help JavaScript a lot
Exactly, the phone number thing is quite an illogical jump.. I think the author has a problem with Microsoft more than anything - I can't help but think you'll enjoy life more by not looking to be outraged, all the best to this individual.
Even if that's true (apple is a bit ambiguous here because they say passcode login is enough), this is still connected to a need to login physically, it sets a much higher cost of acquisition for most.. plus this isn't relevant.. the tech is still aimed at proving real human interaction, even if it's not perfect at that today..
Some of the takes about why attestation is bad seem purposely false because the author dislikes the feature. If attestation isn't triggered then prior behaviour will happen (captcha etc).. this is a progressive feature.. and the point of the attestation isn't to prove you're using an approved device, it's to prove a human is actually present, of which, a verified software stack is needed, otherwise the feature is useless..
This gets brought up every time this concept is floated. As if web developers don't already face this challenge today, and as if web browsers aren't developed with huge amounts of regression analysis. Not only that, but today browsers are considerably more consistent between them.
That's fair, I suppose my point is there are easier ways, I don't think there's any way to technically achieve full privacy on the current design of the internet that couldn't be circumvented by operational changes. But perhaps the point is more that technologies like this are maybe used more to provide false assurance through obscurity. Although it does sound skeptical and bleak given there is no real solutions to that.
How far does this scenario go though? it would be easier for Google to just deploy a changed client app (chrome) that skips the blinding infrastructure, or just sends the user information to them at the same time anyway. In the end, unless you're reading and building every line of code (and maybe even hardware) you are delegating trust.
Given that JavaScript syntax evolution seems to have stalled again (a decade of proposals for bind operator?) I feel like I know why languages like this are appearing, having written quite a bit of swift and kotlin recently, JavaScript really would benefit from shipping bind syntax.
Having used an adblock for a decade or more, it's actually shocking to browse without one these days, it actually feels like I've got malware, with many many sites having LAYERS of ads, like they are buckshotting and expecting most to be blocked.
Poetry ended up being mostly a disappointment having used it for the last 18 months. First time installs were eventually an hour long to resolve, and lock files were platform specific, making using them for reproducibility almost useless. The wider python ecosystem is frankly painful to productionize even today and it really does need some focus and governance.
Kind of wild they don't require domain ownership proof in this case though, if I'm displaying one domain but actually linking to another, I should need to prove I own the original domain