i generally agree, although for some reCaptcha-using websites there actually aren’t alternatives. eg many governments, healthcare providers, public utilities, etc are using it :(

A Motorola phone soon shipping with GrapheneOS isn’t just a rumor but it doesn’t help with the problem of Google making their very popular robot detection service classify deGoogled Android users as non-human.

By the end of long workflows

Yes, this has been known for 10 years.

huh? the kind of “long workflows” this paper is discussing didn’t exist two years ago much less 10

more info here: https://reclaimthenet.org/google-broke-recaptcha-for-de-googled-android-users

that kernel release (which most distros have still not shipped yet) fixes only one of the two vulnerabilities (CVE-2026-43284); afaik even upstream still doesn’t have a patch for the second one (CVE-2026-43500) at this time.

(for people relying on Linux privilege separation, here are mitigation instructions.)

amazing! it’s great to see that is still being maintained after so many years.

😭 is the emoji for exocrine

you could try renaming sideloading to “freedomloading” or maybe “freeloading”

freeloading is already a verb in english, and not the one you’re looking for

https://en.wikipedia.org/wiki/Chatbot_psychosis is real, but so is surveillance capitalism’s drive for full spectrum dominance :(

deleted by creator

also it’s from the spammer’s “staging” instance, so the payload is a URL with a staging hostname which doesn’t even resolve 🙄

twitter (via cloudflare) is serving HTTP 403 {"error_code":2,"error_response":"Dmcaed"}

Why buy a personal computer or word processor?

…they asked in 1987, when word processor didn’t necessarily mean a piece of software

Anyone can use copilot to open PRs under their own name on any repo which accepts PRs, so you can’t easily know copilot is involved without looking.

In the case of the first hit in the mastodon post’s linked search query, it looks like a human actually opened the PR last year and subsequently requested a review from copilot (as well as from two humans); after some back and forth nothing else happened until 3 days ago when copilot updated the issue to tell them: you need to pick a “Usage billed to” option in your Copilot settings.

And then, apparently, three minutes after they updated their billing information copilot pushed some more commits and helpfully edited the human’s original PR description to insert the advertisement.

(Obviously this is yet another reason to move off of github, but (1) that is much easier said than done for many projects, and (2) once it’s normalized on github, “coding assistants” will also be spamming in other venues soon enough if they aren’t already.)

It’s easy to avoid if you don’t use AI?

Isn’t this a Raycast ad, rather than a Copilot ad?

It seems most likely that it is copilot inserting it, because the other screenshots in the post show similar ads for its integrations with various other services too

you’re obviously prompting it wrong, and/or not using the latest models _/s

unfortunately, like its predecessor (Nokia’s Maemo/Meego), Jolla’s SailfishOS has never been (and has never had plans to be) fully free/libre open source software.

many components of it are freely licensed, but not nearly enough to constitute an actual mobile operating system you can use.

what happened next? (do the terms actually allow you to cancel it immediately for no cost, or is their $10-per-month-for-nothing offer an alternative to paying a cancellation fee?)

(well actually) you forgot Poland