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.

Wonder I’d they’ll allow reordering the buttons and possibly adding other items from the … Menu or extensions. I kinda doubt it since customization on mobile has always been limited, but then again, the old UI had no extra space to work with in the first place.

Generally speaking I’m not opposed to sqlite. The case of a notes app is the one exception.

If i need to make a big find and replace change, i dont need to rely on the app to have the capability or whip out a sql editor or cli tool. I just open my favorite text editor and do it. Or chain some cli tools built into the os.

Its not even about data portability or export. Its about working with the data.

Exactly. Not a huge fan of notes apps storing the data in a db.otherwise there is a lot to like about joplin. With obsidian i open my notes in codium all the time to make mass edits or fill gaps that obsidians UI cant meet, which is not possible with joplin.

Fortunately with obsidian as long as you keep the plugins on the lighter side and keep any non-markdown content in seperate files via linking, im not too worried about having to jump ship if it ever goes bad. Worst case if a plugin dies or i have to migrate, the actual loss of data is that some plugin used json or whatever and it’d have to be converted or replaced.

I do have hope at least that if the company folds they’ll open source it, or turn a blind eye to a community reengineering effort. And what is unique about obsidian markdown and metadata will probably get community-built migration tools quickly if enough people jump ship en masse.

But for the time being Obsidian is the best option for me and i dont feel that bad about it.