Replying to
@slightlyoff@toot.cafe @jaffathecake@mastodon.social From the outside of the Webstandards process this all looks very much like Google pulling a “fuck your complaints, we’re shipping it.” and should be treated as a hostile act
Remote
Ash
@ash@icosahedron.website
mastodon 4.6.8Python developer, Apache Airflow core committer/PMC
160 Followers
134 Following
8 Posts
Joined April 03, 2017
GitHub:
Location:
London, UK
April was a good for month for solar and battery. So far my net electricity costs for the month are -£29
(Mostly thanks to Octopus Agile meaning i get half hourly billing that went negative when Storm Dave? was around)
Replying to
@slightlyoff@toot.cafe @jaffathecake@mastodon.social
The firmer ground to argue from is that there doesn't appear to be a path to plausible interoperability.
That’s a more polite way of “fuck your complaints, we’re shipping anyway”
Old oak trees are huge
RE: @chris__martin@functional.cafe
Don’t threaten me with a good time! (That being the meter hint of Cloudflare being in trouble)
RE: @david_chisnall@infosec.exchange
Key point of this for me
> But the most relevant part is that it contained three critical command-injection vulnerabilities.
>
> These are the kind of things that static analysis should be catching. And, apparently at least one of the following is true:
>
> Mythos didn't catch them.Mythos doesn't work well enough for Anthropic to bother using it on their own code.Mythos did catch them but the false-positive rate is so high that no one was able to find the important bugs in the flood of useless ones.
No you’re listening to the 2012 Olympic Opening Ceremony songs
Replying to
@slightlyoff@toot.cafe @jaffathecake@mastodon.social and I appreciate that, but hence the bit about “as an outsider”. I get to just vent and be unproductive.
But also: do we really think the Chrome team thought “yes, this is a good standard that will promote interoperability” given the feedback they already received before the I2S? So either: they didn’t care, or, their intent is questionable. Even assuming good faith, i can’t see how it can be anything else.
Add on to this the “track record” of things like cookie/ad tracking cohort thing a few years ago, change of Extensions to make uBlock not as effecting, it all adds up to making it hard for me, a random dude on the internet to believe Chrome has web standards interests at heart