Honestly, I'm not mad if AI fully defeats captchas to the point they go away. They almost always fail to be usable via accessibility tools. These things might block some automated systems, but they also block people with disabilities.

Manifest v3 extensions work in Firefox, too. Its just the new thing. Its way easier to build cross-browser extensions with, too. V3 is actually a good thing overall, as its led to a lot of extensions being available for Firefox when the devs might have just targeted chrome. Way more feature parity between browsers with v3.

Chrome dropping support for v2 doesn't merit a response from Firefox because nothing changes for Firefox users and they're not going to drop support. Any one who actually cares (and they should) will move to Firefox on their own, so why waste advertising money on that? Eventually Firefox and any other browsers who want to allow stuff like ublock will probably have a way to do the same tasks in v3 (and the Firefox Dev team has said as much in blog posts for ages), then it'll just be a feature that doesn't work in chrome. V3 just simply doesn't have the API that ublock uses in v2.

There have been discussions for years in the w3c standards group about this whole shitshow and this is one the chrome team have basically refused to budge on despite all the other browser teams. Its honestlu a mirscle they delayed it as long as they have. This was originally supposed to happen at the start of 2023.

Chrome is kinda like a country with a overrule veto vote at the UN when it comes to w3c working groups since they can just do whatever they want anyway, and nothing will change until they no longer have that power. That said, browser feature parity is at an all time high recently and its because all the browser teams are working together better than ever. There are just these hard limits chrome chooses to stick to.

Until recently, Wayland development was rather slow, especially in the areas where more specialized software run into issues that force them to stick with X11. Since Wayland does a lot less than X11 and is more componetized across multiple libraries designed to be swappable, some of these areas simply do not have solutions. Yet.

And, as always with FOSS, funding is a big part of the problem. The recent funding boosts the GNOME foundation received have also led to some increased funding for work on Wayland and friends. In particular, accessibility has been almost nonexistent on Wayland, so that also means that if an app wants to ensure certain levels of accessibility, they can't switch to Wayland. GNOME's Newton effort is still very alpha, but promising.

While big apps like blender and krita get good funding, they can't necessarily solve the problem themselves by throwing money at it, either. But the more funding Wayland gets to fill in the feature-gaps and ease adoption, the sooner we'll be able to move away from xwayland as a fallback.

Wayland and its whole implementation process certinally aren't without fault. There's a lot of really justified anger and frustration all around. Even so, staying on X11 isnt a solution.

While I found ubuntu's business practices (all the upsells, mostly) the most grating, really the thing that pushed me off of Ubuntu was packages being behind inexplicably and all the forking/modifying they did to gnome and just always being like 1-2 major versions behind, especially since gnomes been shipping tons of features the last few years and Ubuntu wouldn't get them for ages.

Outside of the snaps that Ubuntu seems to force you back into if you purposely try to turn it off, its not the worst to avoid otherwise. Or just deal with for a few apps.

If they want the ubuntu stack of tooling, suggest debian. If they feel intimidated by Debian, Ubuntu is fine. Debian is really solid out of the box for a primary devices nowadays. no need to wait for Ubuntu to bless packages since the Debian ppa's are usually much faster to update. But as long as they aren't doing really weird stuff, they can always move off of Ubuntu to Debian or any other debian descendant easily if they want a smooth transition since its the same package manager.

As long as the immutable distro paradigm isnt a turn off for them, Vanilla OS is also really neat, including cross-package manager installs. V1 is Ubuntu based, v2 will be Debian based (if it isnt already GA'd... I know thats soonish)

I've mostly switched to using Debian for dev containers and servers, and 99% of the time any ubuntu-specific guides are still perfectlh helpful. I moved to Arch for main devices.

(Side note: I abandoned manjaro for similar reasons as I abandoned Ubuntu: too much customization forced upon me, manjaro's package repo was always behind or even had some broken packages vs the arch repos, and some odd decisions by the maintainers about all sorts of things. EndeavourOS has been just way better as someone who likes to have a less-dictated setup that is closer to the distro base and faster to get package updates)

Edit: I guess my tl:dr is... If one thinks "Ubuntu", first ask "why not debian?", and then proceed to Ubuntu if there are some solid reasons to do so for the situation.

The appearance of similarities between Generative AI and the unconscious mind do not mean there is any actual equivilance to be had. We gotta stop using the same terminology to describe generative AI as we do humans because they are not the same thing in the slightest. This only leads to further unintentional bias, and an increased likelihood of seeing connections with the unconscious mind that don't actually exist.

What drives me crazy about its programming responses is how awful the html it suggests is. Vast majority of its answers are inaccessible. If anything, a LLM should be able to process and reconcile the correct choices for semantic html better than a human... but it doesnt because its not trained on WIA-ARIA... its trained on random reddit and stack overflow results and packages those up in nice sounding words. And its not entirely that the training data wants to be inaccessible... a lot of it is just example code wothout any intent to be accessible anyway. Which is the problem. LLM's dont know what the context is for something presented as a minimal example vs something presented as an ideal solution, at least, not without careful training. These generalized models dont spend a lot of time on the tuned training for a particular task because that would counteract the "generalized" capabilities.

Sure, its annoying if it doesnt give a fully formed solution of some python or js or whatever to perform a task. Sometimes it'll go way overboard (it loves to tell you to extend js object methods with slight tweaks, rather than use built in methods, for instance, which is a really bad practice but will get the job done)

We already have a massive issue with inaccessible web sites and this tech is just pushing a bunch of people who may already be unaware of accessible html best practices to write even more inaccessible html, confidently.

But hey, thats what capitalism is good for right? Making money on half-baked promises and screwing over the disabled. they arent profitable, anyway.

Roku was such an easy recommendation for a long time... Non-complex UI, long support for updates, not owned by google or amazon... Far cheaper than LG and Samsung... (Not that Samsung's UI is anywhere near as easy as roku)

But now I guess thats done. Unless an alternate firmware exists or this doesn't hit older TVs I guess I'll be looking for a new TV... Which is a shame because my current 4 year old roku TV is more than capable.

Power users love to bash accessibility features like this. Its a classic case of "I don't need a wheelchair ramp so i dont know why the library added one!"

Accessibility is way more than screen readers. It's more than specific disability-minded modes. The web needs to be friendly to everyone, including people who may not know they could benefit from accessibility features. Everyone benefits from this type of work.

There are definitely some legit feature concerns and priorities being called out here. Mozilla has left a lot to be desired of late on that front. But a power user is more than capable of jumping into settings or about:config to turn things like this off, or finding an extension to get by for now.

Also the firefox dev team isn't tiny. This isn't blocking other work or anything in a substantial way, it's a fairly isolated piece of UI, and there's no guarantee that skipping this would change the timeline on anything else.

Tooltips are a standard accessibility feature. Just because you may not find them helpful doesn't mean others do not benefit. The delay is to ensure they don't get in the way unintentionally (but still allow usage) for those who do not need the accessibility benefit at all times.

Chronic migraine. People think its just a headache, but that's really just the most obvious symptom and least complex symptom. Family practice/generalized doctors know too little about it to recognize it. Everyone around you thinks you're just being dramatic. If they can push through a headache then why cant you push through a migraine?

Migraine is a cycle that lasts days. It has phases: prodrome, aura, acute, postdrome. The acute phase (the headache part) is just one phase. Sometimes the headache isn't even that bad, or long. Sometimes it lasts multiple days. Its a neurological disorder and, in a lot of ways, basically is like your nervous system short circuiting for a few hours or days. Triggers have a lot to do with severity, but there is also a lot of bad info about triggers too. With chronic migraine, you could avoid all triggers and still have 1-2 migraine events a month, and those events dont care about your calendar.

Because information is so badly shared and everyone (mostly unintentionally) gaslights anyone with migraine into thinking they're not suffering from a chronic condition, many of us go a long time before discovering useful information or getting diagnosed.

There are a ton of signs during the prodrome phase which, once you know what to look for, can help you avoid (sometimes) the acute phase by taking meds soon enough and focusing on avoiding known triggers. Even standard over-the-counter stuff can short circuit a lot of migraines before the most painful part. But also, some of the prodrome stuff alone can make working or completing tasks difficult. I often start having trouble speaking, get very tired, have difficulty focusing vision. General brain fog. This can be hours or days before an attack.

After the headache phase, the postdrome is often more brain fog, speaking issues, low energy, but also sometimes a euphoric state which can make getting back into your normal schedule really difficult.

I miss family events. I miss friend events. I have to cancel stuff all the time. I worry about scheduling things for fear of being in a headache phase. I've been lucky with employers being understanding, esp with the work from home setup and mostly DIY hours, but i absolutely couldn't work a job with shifts.

So you want software developers to spend less time building the software so they can run a nonprofit too? Do you think all the conferences, sites, fundraising, marketing, extensive help docs, bug processing, and community engagement is all something that can just be done on the side?

Just ask any software dev working st any of these foundations. They don't want to do any of the business-side work. Or, if they do, they certainly don't want to do it alone. If they were alone in it, they wouldn't have time to write code.

That's how Microsoft markets their "safe links" in Outlook, which is more or less the same behavior of wrapping all links with a redirect. Whether they actually do anything with that to save you from phishing attempts or whatever... who knows. Even if there is a safety feature, it's still an easy way to mine url query params for data or learn about the user for other purposes (which they may or may not be doing)

IMO if you can't turn it off, there's a secondary motive to the feature. Especially when the feature is marketed from a place of fear rather than aid.