A ticket tracker and a wiki!

Else all the institutional knowledge about your software that your users are adding too vanishes forever into a black box. And that’d be a dang pity

Nah, that’s valid. I loved it to bits, myself, but what made me love it was how adroitly I felt it curated feelings of dread and sincere awe as I explored deeper and deeper; and that’s highly subjective. I hope you’re finding as much joy in your own fave games as I did in Subnautica!

WOW, yes, your problem is almost certainly Flatpak-related. I’m surprised you even got as far as you did. Flatpak is often great but does not tend to play well with applications that need less common capabilities.

I’d recommend installing VMM in a different way if that’s an option for you; I expect that will likely make your problem go away.

Well, what are the permissions of /run/usr/1000/doc/c0a3c3fc and what user are you running VMM as?

I am in mad love with this Darmok-ass comment.

Ah, that Techlicious link is a great find, thanks. It does lay out clearly what the theoretical concern is. That’s still a far cry from the “Google will start fingerprintint you” scenario that seems to have people up in arms.

Thanks for digging out this link, I really appreciate it.

Thanks – that’s an announcement about policy updates. I already read it and it says nothing about fingerprinting. The only change to underlying technologies it mentions is the use of e.g. trusted execution environments (the doc for which, per a further link, is in fact on github). Those seem to claim that they let announcers run ad campaigns through Google ads while keeping their campaign data provably locked away from Google. So, basically, all these links are about purported “privacy-enhancing” techs, and you’d be forgiven for taking that with an enormous grain of salt, but either way, nothing in there about fingerprinting.

The Guardian article basically paraphrases the Tuta one – or it’s the other way around, maybe – but does also not provide actual sources.

I just want a source on what fingerprinting Tuta is claiming Google will start using. I feel like the details of the purported fingerprinting techniques should be front and center to this discussion and I’m frustrated that the article entirely fails to provide that info.

I’m aware of fingerprinting techniques, thank you. The article is claiming that Google will start using some of those and I’m looking for the source for that claim, hopefully with specifics about which techniques are involved. Confusingly, the article does not appear to provide such a source.

You’d THINK the article would link to a source about the fingerprinting in question instead of 90% filler slop and ads for their own service… Anyone got a link?

It… depends. There is some great tooling for Python – this was less true only a few years ago, mind you – but the landscape is very much in flux, and usage of the modern stuff is not yet widespread. And a lot of the legacy stuff has a whole host of pitfalls.

Things are broadly progressing in the right direction, and I’d say I’m cautiously optimistic, although if you have to deal with anything related to conda then for the time being: good luck, and sorry.

The default actually works pretty well these days.

Messing with the EFI partition, for instance by attempting to have two of those on separate disks, will probably cause you more pain than Windows will. As far as I understand, only one EFI partition can be configured in BIOS as the boot partition, so you will have to change the configuration in BIOS whenever you want to boot to the other OS.

Windows does have a history of changing the default EFI bootloader once in a while; however your chosen bootloader is still there, just not marked as the default anymore. A Windows app like EasyUEFI will let you change the default back.

Windows 98 really sucked and running Unix at home became an option.

One funny thing about humans is that they aren’t just gloriously fallible: they also get quite upset when that’s pointed out. :)

Unfortunately, that’s also how you end up with blameful company cultures that actively make reliability worse, because then your humans make just the same amounts of mistakes, but they hide them – and you never get a chance to evolve your systems with the safeguards that would have prevented these.

You won’t find the incompetence in the software no matter what.

If you fail to assume that the software contains issues – if you fail to understand that your software is made by humans and humans make mistakes, not because they’re bad but because they’re human – and if you fail to implement mechanisms to feel gracefully with inevitable failures, THAT is the incompetence.

Failures are systemic.

uBlock Origin has a V3 version, yeah. Been using it for a while, seems to work well. I do miss the ability of adding my own filters, hope they implement that eventually.

Go fash, lose cash. 👍🏻

Interesting deep dive and very much worth a read. I’d say it probably underestimates the weight of finance-related pressures coming from the CFO’s office, though.

Correct, AFAIU.

It’s a trade-off that works for many. Not much you and I can do about it, even if it’s frustrating.

Thank you! I know all these things. This still doesn’t help when the DAW support and VST compatibility aren’t there.

If you’re intent on doing music production on Linux, at least do yourself a favor and get a Reaper license, there are few enough pro DAWs that are Linux native. But be aware that many of the big industry VSTs are still not going to work. If you’re fine sticking to e.g. ZynAddSubFX or Pianoteq, though, knock yourself out.

But you can’t reasonably expect musicians to jump those hoops and abandon their fav VSTs when their Windows tooling is there, and works.