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.

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.

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.

Right, and then not watch YouTube or Netflix or anything on my… TV… Good plan!

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.

I picked up one of the ARZOPA ones and they are fine. Not the best looking, but good enough for a second monitor on the go. I used to take my ipad 9.7" with me places for this purpose and even though the image isnt as good, its way less effort to carry around.

I wouldnt use it as a single monitor regularly, nor for gaming.

I had to keep using the usb-c cable that came with it. Not sure if its a specific protocol that my thunderbolt 4 cables dont support or not. Minor inconvenience i havent looked into further.

Don’t feed the troll.

Especially not one that uses mental illness as an insult.

I tried to use Copilot but it just kept getting in the way. The advanced autofill was nice sometimes, but its not like i’m making a list of countries or some mock data that often…

As far as generated code… especially with html/css/js frontend code it consistently output extremely inaccessible code. Which is baffling considering how straightforward the MDN, web.dev, and WCAG docs are. (Then again, LLMs cant really understand when an inaccessable pattern is used to demonstrate an onclick instead of a semantic a or to explain aria-* attributes…)

It was so bad so often that I dont use it much for languages I’m unfamiliar with either. If it puts out garbage where i’m an expert, i dont want to be responsible for it when I have no knowledge.

I might consider trying a LLM thats much more tuned to a single languge or purpose. I don’t really see these generalized ones being popular long run, especially once the rose-tinted glasses come off.

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.

The page title isn’t necessarily visible on the web page that sets the title.

Clicking is not always a simple task.

I shouldn’t have to leave my current page just to figure out what another tab is.

Again, just because you feel something is useless or easily avoided doesn’t mean that all internet users feel the same.

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.

I’ve been windows-free for about 8 months as well. I’m a more casual gamer so i haven’t had to venture out of steam proton yet (but i’ve got bottles on hand to experiment anyway) A few of the games i tend to return to every few years will definitely need bottles.

I built a beefy system, and I was initially planning on running windows (or one of the de-microsofted builds) on a vm with pass-through GPU (shunting my linux over to the on-cpu gpu when im running it) but so far i’ve had no need to continue setting that up. I proactively placed all my steam games on an ntfs filesystem just in case i do in the future.

Either way, i’m glad to have the flexibility to make windows work without dual boot, but so far it looks like i was being overly cautious. Probably cant play some games with anti-cheat right now… but i so rarely play those types of game.

https://whatpwacando.today/ is a nice site to test things out. You should see the option to install on Firefox for android, as well as verify what features work.

Glad it finally landed in main, I’ve been using nightly to install PWA’s for a while. It worked fine, but having the two different browsers to juggle for initial install was a pain.

+1

the UI could be improved (I always end up hovering for tooltips on controls) but it works really well.

I also like that tabs will stay in the stash by default on close, so its great for opening a bunch of reference sites really quickly without worrying about losing them

Closest thing to the old firefox experiment from a few years back.

If you know how to add a real “delete” entry that would be great.

At least in nautilus 42 the preferences let you enable a permanent delete option in the right click menu, if that’s what you are looking for.