Mastodon Feed
Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
Margarita ("Margarita Noriega") wrote:
Mastodon FeedMastodon FeedReblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
peter@area51.social ("Peter Mount") wrote:
Mastodon FeedReblogged by slightlyoff@toot.cafe ("Alex Russell"):
juddlegum@journa.host ("Judd Legum") wrote:
Mastodon FeedTime for some new music in your timeline!
I finally got around to listen to the music of "Goth Dad" and I really enjoy it. :batsquish:Vision Video - In My Side
https://song.link/s/1FgOjbd5YinVDboy7Ul5Jw#music #NowPlaying #VisionVideo #goth #GothicRock #PostPunk #NewWave #GothPop
Mastodon FeedReblogged by lcasdev ("Luca Casonato 🏳️🌈"):
deno_land@fosstodon.org ("Deno") wrote:
Attachments:
Mastodon FeedReblogged by blithe ("Blithe"):
ivory@tapbots.social ("Ivory") wrote:
Attachments:
Mastodon FeedReblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
ifixcoinops@mstdn.social ("Dan Fixes Coin-Ops") wrote:
Mastodon FeedGo get it! https://apps.apple.com/us/app/ivory-for-mastodon-by-tapbots/id6444602274
Mastodon Feedpzmyers@octodon.social ("pzmyers 🦑") wrote:
I'm contemplating traveling by train this summer. The US doesn't make it easy to figure out what is possible, though.
https://freethoughtblogs.com/pharyngula/2023/01/24/any-train-people-out-there/
Attachments:
Mastodon Feedxor@tech.intersects.art ("Parker Higgins") wrote:
Got set up on @ivory and signed up for an annual subscription. So far it's great, congrats and good luck to @tapbots
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
We've been developing out ahead of artificially denied consensus for a decade, and Apple implementing many of these designs w/o changes today is an admission that all the trolling and side-eye was just that: marketing to cover for a lack of care and investment -- not a real or accurate commentary about quality.
We'll always engage with Apple (and anyone else) in standards, but the idea that somehow things must move slower, or that Apple is being more responsible here, is thoroughly rubbished.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
But this also points out a separate quality axis that used to be fused to the standards process in the old wild, wild west. Once upon a time, it was ship-and-fix-in-standards, but that's not how it works now. We do all the quality assurance work *before* shipping.
Not only is it possible to design features responsibly, in the open, with extremely high quality, great security, & privacy, but to do so well ahead of (gamed) consensus.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
So it's important to view the manufactured opacity and disengagement from Apple as a tactic: by withholding engineering bandwidth in standards, it can prevent responsibly designed features from migrating to more "official" standards bodies which provide the cover of more consensus.
When you don't want to fund the work, and the gate is consensus, you can spend a *lot* less to dam the standards river and muddy the water downstream. And Apple does.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
The Blink API OWNERS discuss and vote on these features, in the open, and our tie-breaker is "do we have evidence that this solves an important problem well?"
That isn't a discussion about other vendors; it's about end-users and end-developers.
Here's a talk I gave about the incredibly open, risk-based approach we take:
https://www.youtube.com/watch?v=1Z83L6xa1tw
What you should understand is that every Blink developer feels like they're wading through molasses to navigate this gauntlet. The bar is HIGH.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
What does that look like?
There's an arduous process that we make feature teams walk to launch. The result is that features must be developed *responsibly*, and in the open.
If we're going to take the risk to put something into the platform in an area where Apple (et al) are radio silent (which is a LOT of the web), the bar goes way up to ship. Specs. Tests. Explainers. Developer feedback. All of it is required:
Mastodon FeedReblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
PlayHistory@oldbytes.space ("Play History") wrote:
Attachments:
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
The worst misunderstanding is the idea that Chromium is "shipping proprietary features" that Apple et al are protecting the web from.
Obviously, I'm biased, but this is usually a case of Apple withholding engagement in standards fora, which denies feature teams a browser partner to move things forward, but that's not the constituency for features; developers and users are.
So we work around radio silence by Apple by demanding care and evidence, rather than standing dead in the water.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
IDK who needs to hear this, but Safari is not a "counterbalance to Chrome", it's actively gutting Mozilla of revenue while simultaneously holding the web back through structural under-investment.
Some of y'all are cheering Apple as they measure the web for a casket because you don't like the insurance plan it's on today:
https://infrequently.org/2022/06/apple-is-not-defending-browser-engine-choice/
Mastodon Feedxor@tech.intersects.art ("Parker Higgins") wrote:
almost no spelling error (by others) gets on my nerves — if meaning is clear spelling is definitely secondary. except "mastadon" for some reason
Mastodon FeedReblogged by slightlyoff@toot.cafe ("Alex Russell"):
andy@bell.bz ("Andy Bell") wrote:
Mastodon FeedReblogged by slightlyoff@toot.cafe ("Alex Russell"):
anildash@me.dm ("Anil Dash") wrote:
Mastodon FeedReblogged by slightlyoff@toot.cafe ("Alex Russell"):
mathowie@xoxo.zone ("Matt Haughey 🦣") wrote:
Attachments:
Mastodon FeedReblogged by nadim@symbolic.software ("Nadim Kobeissi"):
WPalant@infosec.exchange ("Yellow Flag") wrote:
Mastodon FeedReblogged by jeffsonstein ("Jeff Sonstein"):
juglugs@mastodon.juglugs.com ("Widdershins Smith") wrote:
Mastodon FeedReblogged by jeffsonstein ("Jeff Sonstein"):
bleakfuture@home.social ("Bleak Future :verified:") wrote:
Mastodon FeedReblogged by jeffsonstein ("Jeff Sonstein"):
GottaLaff ("Laffy") wrote:
Mastodon FeedReblogged by jeffsonstein ("Jeff Sonstein"):
tincanman@mastodon.world wrote:
Mastodon Feedjeffsonstein ("Jeff Sonstein") wrote:
if you are surprised by this then I want to talk to you about a nice bridge I happen to know is coming up for sale cheap Real Soon Now
Mastodon FeedReblogged by jeffsonstein ("Jeff Sonstein"):
venladetta ("Venla Detta") wrote:
Attachments:
Mastodon Feedjeffsonstein ("Jeff Sonstein") wrote:
got that?