FUCK IT THEY GOT PAPERLESS-NGX TOOO?????

I've been researching information about /etc/machine-id, a file that contains an ever-persistent machine ID that identifies the install across hardware or netwotk changes, and that is world-readable.

Most documentation I've seen says it is mostly safe to change this file and generate a new ID on shutdown, and there are example scripts to do it via eg.: systemd or rc.shutdown . That's nice, but... we're on Linux, we don't "shutdown" our machines, what do they think we are, Windows users? We don't shutdown at least intentionally.

So, I was wondering, is it feasible to regenerate this ID on hibernate? It's another instance where the machine powers down, there are ACPI hooks to run scripts on hibernate/wakeup, and I feel at least for a laptop it's a more common use case than a shutdown.

Basically $TITLE.

It happens sometimes that I need to install both the native and the flatpak version of a program, for compatibility or feature reasons. Say for example, native Gnucash has a crash in a specific dialog that I can skip with the flatpak version if that dialog crosses my workflow.

But this causes an issue. Many flatpak applications I have installed, like Norka, result in duplicating the icon / .desktop entry in the menu, which is annoying but survivable, But a few others, such as Luanti, seem to hide or replace the menu icon of the native program, leaving only one entry in the menu that always leads to the flatpak version. And this is quite breaking.

Is there any to prevent Flatpak from hiding or overwriting the native program icons, or at least prevent it from camouflaging itself? Basically I'm looking for how or where to achieve any of the following:

• Make flatpak menu entries install separately, with names or descriptions guaranteed to not conflict with native program icons (say, "App - Flatpak version").
• Make flatpak menu icons install into their own subdirectory in the menu.
• Make flatpak not install desktop menu entries

Thanks in advance.