https://addons.thunderbird.net/en-US/thunderbird/addon/filelink-provider-for-send/ this add on can be pointed at any send instance, so long as the instance isn’t too diverged from the popular fork or Mozilla’s original project.

The Thunderbird team has talked in the past about bringing Mozilla Send back as more of a feature for Thunderbird files embedded in emails, hence some of the work that’s happening off and on by Mozilla themselves in the original project, some of which has been merged into the project this post is about.

I moved one of my computers to endeavor, but one is still on manjaro and the contrast is kinda hilarious. Manjaro machine always gets funky after updates, it struggles to deal with sleep and hibernation, and it feels slow even when its like 4x as powerful as my EndeavourOS machine.

Its been in testing for a bit. It got bumped from the last major desktop Thunderbird release and since Thunderbird releases used to be synced to firefox ESR releases its been a slow turnaround to get their schedule moving faster.

Its an f-droid metadata issue that the team is already aware of https://github.com/thunderbird/thunderbird-android/issues/8478

I mean, the issues were present and widely reported for several months before Intel even acknowledged the problems. And it wasn’t just media reporting this, it was also game server hosts who were seeing massive deployments failing at unprecedented rates. Even those customers, who get way better support than the average home user, were largely dismissed by intel for a long time. It then took several more months to ship a fix. The widespread nature of the issues points to a major failure on the companies part to properly QA and ensure their partners were given accurate guidance for motherboard specs. Even so, the patches only prevent further harm to the processor, it doesnt fix any damage that has already been incurred that could amount to years off of its lifespan. Sure they are doing an extended warranty, but thats still a band-aid.

I agree it doesnt mean one should completely dismiss the possibility of buying an Intel chip, but it certinally doesn’t inspire confidence.

Even if this was all an oversight or process failure, it still looks a lot like Intel as a whole deciding to ship chips that had a nice looking set of numbers despite those numbers being achieved through a degraded lifespan.

Wow, Bitwarden has made leaps and bounds on catching up to 1password on dev tools and enterprise features the last few years. I’m going to need to re-evaluate/consider moving over.

As a side note, if you work somewhere that uses 1password, you can usually get your personal subscription comped as an individual. Only need to pay for it if you leave your company or they drop 1password.

I dont know that I’ll stay on 1password forever, but on the scale of things I’m most concerned about self-hosting vs using a reasonably private SaaS, 1password is nowhere near the top of my list to ditch. Otherwise, its a solid recommendation for non-self hosters who want to make some progress.

The space example is extremely apt. Its possible we could have had tons of space stations, a moon colony, maybe even some other stuff going on around the solar system, asteroid mining, etc. But thay would have at least required the space race to continue longer and for spending to grow to create a big enoigh industry to ensure thay outcome, assuming no capacity or time issue. Alas, we took another path.

Something that seems important to us might not matter in even 10 years, or at least, not have a monetary and/or societal incentive to keep advancing.

So the site should just… Not work in firefox then?

A lot of the sites in the about:compat block or don’t work in Firefox because the sites don’t follow web standards

All web browsers have semi hidden pages like this for all sorts of purposes. Its not really intended to be secret, its just not stuff worth even adding to a file menu. Some of the about: pages in firefox are in some submenus, some on settings, but def not all. Tho you’ll fimd them mentioned and linked in support guides.

If anything, the ability to access these is better than them being blocked…

I’ve also had struggles with arch with printing, more so than debian-based distros. EndeavourOS is where i did the most troubleshooting, but its also a problem on my manjaro install (whicj ill move to endeavour… Someday) But learning how to use cups directly was worth it.

Currently, printing via GUI is like 5ppm and very low dpi so… Not great. But at least I can print for the casual use cases out of the box and could work out a terminal solution if I needed to in the meantime.

I don’t print much so haven’t put time into getting things working better for bigger jobs, but printing is definitely going to be a more hit/miss experience with arch. Its looking like better GUI experience for my specific model will require a driver from the AUR or scripting the Debian install from brothers drivers site. But my model is apparently not as widely used and just hasn’t gotten as much community support I guess

Brother, in particular, has always been fairly well supported via Linux fortunately. Especially great since their laser printers have been the best cost/value for home use for a long time.

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.

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.

Don’t feed the troll.

Especially not one that uses mental illness as an insult.

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.