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

Hey, it’s okay, friend, not every game has to be for everyone and that’s fine.

What worked for me, I guess, was to not approach it in terms of a game where I’m trying to make progress, so much as a vast place with a lot of mysteries that all actually make sense once you work it out; and that happens naturally if you let your curiosity drive you. You will, in fact, be making progress; you just won’t realize it until the pieces fall into plane and, all at once, you know.

OUTER WILDS! If you’ve played it, you know why. (If you haven’t, do not ask. Play it.)

Mint is just perfectly fine, don’t listen to the naysayers.

As the old observation goes, novices use something like Mint because it’s there, and it works; intermediate users use something like Arch because they want the control to tweak things in the greatest depths; experts use something like Mint because it’s there, and it works.

Can you give me a link to that documenation and tooling?

Linux daemons and utilities typically come with manuals that get installed alongside the software. There’s a command line tool, aptly called man, that can be used to search and display these manuals. So for instance, man resolvectl displays the manual for the command line utility that you can use to control, configure, monitor and debug the systemd-resolved daemon. (Although I usually look up the man page online because it’s more convenient to scroll through than in a terminal.) Man pages for a given daemon will typically mention near the bottom related man pages for e.g. control utilities like resolvectl, so it’s not necessary to remember it by heart.

a week later they all have different configurations.

I’m trying to remember any situation where one of the systemd components would change its configuration on its own, but I’m coming up blank. It may be my memory failing me, but possibly that’s the wrong tree to bark up?

Especially then. Great documentation and support tooling make troubleshooting much easier.

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?

Wow, that’s a sobering read. And comprehensive, and insightful. I hope this gets some attention and results in much needed improvements in that area.

Also check out Wordatro (https://store.steampowered.com/app/3140120/Wordatro/)! It’s well made and quite addictive.

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?