Are people really surprised there's collateral damage from a hastily added couple of sentences ripe for misinterpretation? Did Anthropic measure the impact of the change at all?
Two more things to note about impact assessment: Flatpak uses the selected runtime's baked-in trust store (I think), so any apps may be susceptible even if you update the system package. Containers also don't inherit the host's trust store and use the one from the base image.
If the application uses p11-kit, or a TLS library that uses p11-kit such as OpenSSL, NSS, or GnuTLS, then Flatpak should automatically give it access to the host system's CA certificates.
It's not just new accounts. Since at least around mid-August they have been deactivating existing accounts (some 10+ years old) by forcing them into a broken "human verification" flow. You have to pass a Cloudflare check if using the web client, which then discards the signal and forces you to go through the app flow (which many report is also broken/stuck).
I suspect it's a crackdown on accounts used for services like xcancel/nitter, but their heuristics are laughably poor and have resulted in a massive wave of false positive effective "bans" while having no noticeable impact on mirroring services.
Buried in Microsoft's announcement is the more damning fact that 96% of GamePass subscribers spent fewer than 15 hours on cloud game streaming. I suspect the whole service may be retired sooner rather than later to free up compute resources for you know what.
This approach seems kind of backwards to me. Why try to detect everything except the thing you're trying to remove instead of either sampling a few uhs and ums and treating them as noise to be silenced (with a sharp crossfade to the noise floor that doesn't interrupt speech flow) or finetuning a model to detect them specifically for full automation?
> instead of either sampling a few uhs and ums and treating them as noise to be silenced
If you're not paying ttention, ctting out specific sounds can easily cause more trouble. I for one would be quite pset if I couldn't hear the pire's reasoning for calling a foul.
That's been happening to me more often too recently. I find that, for a growing number of simple problems, reinventing the wheel is faster and more efficient than importing a mature, fully-featured dependency.
reply