Window Rules and Custom Shortcuts from KDE Plasma, just earlier today I binded Meta+Ctrl+k to start Konsole in the directory of my latest modified prototype, open a per directory script which e.g. opens a browser tab, opens Vim in the file to edit, positions those windows properly, here browser on left half, console on top right corner.

Window Rules with its window picker is very convenient to get conditions and properties to apply. Custom Shortcuts is just a list of shortcuts you can add to start anything from anywhere.

Also I added my own wiki as a KRunner Web search, so if I type Alt+Space then PIM keyword it searches directly to my PIM from the center of my screen, also from anywhere.

I understand where you are coming from but I would take the opposite approach, namely not how quickly and conveniently you get back to exactly the same state (because that’s actually really hard) but rather how quickly and conveniently you can get to work, or play, or do whatever you do, from the most generic of hardware and software, including of course yours. What this perspective suggests though is NOT to consider your stuff precious but on the contrary, to assume it will inevitably disappear, due to any reason, from a freak event, e.g stolen to the mundane, e.g. hardware failure over time.

IMHO it’s much more relaxing to consider hardware disposable. My own heuristic for this is to understand what a distribution does, save only MY data (e.g. things that I produce, for example in a data it would be my saves but not the game itself) and buy only well supported hardware.

Targeting Linux distributions is even less likely because unlike Windows or MacOS there is no “official” viewer for a kind of document, being image, video, text, etc but rather only the one that the distribution picked but that even during the installation process the user might ignore or replace. So the attack on the media would have to work for any viewer which seems basically impossible.

Technically possible yes but practically impossible at scale, it would have to be targeting a specific user and then it’s a totally different situation.

Backup your data so that you can restore what matters to you. There is no need for an antivirus on Linux if you stick to the distribution channels of your distribution because package are verified. Unlike in the close source world because the source of those packages are open, verifying, even though imperfect, is much simpler. Popular distributions, e.g. Debian or Redhat, have a very strong incentive not to let anything slip. Maintainer of packages also are able not just to track what changed but also by whom, that means if there is a problem it can be identified and attributed rather quickly and thus other maintainers can be warned. It is not impossible and supply chain attacks do happen, e.g. xz backdoor, but it is rare, specific and has been studied and thus partly alleviated even though it remains a challenge.

If you do download executables or binaries, not media e.g. videos or music, from random places though then all bets are off.

MAME

I have some of her paper zines on my desk, warmly recommended.

Might look esoteric at first but if you think we will be using Linux at least on desktop, servers, consoles and more for decades then totally worth learning about.

I’ll just leave this here… https://debian.org/

It’s disappointing yet unsurprising to read the recurring answers, namely :

• cost
• incumbency

precisely because it’s absolutely avoidable and a well known strategy. It’s so well known that it’s precisely why Micro$lop bought Github in the first place. People are there and the free tiers is enough to get the long tail.

Meanwhile since that strategy happened people who consider smart enough should know the genuine cost behind this : it’s a TRAP. Plain and simple, you get there and you get STUCK there.

So… yes it takes some sweat and even some money to leave the trap … but if you care about freedom, as most free software or open-source developers might, then it’s aligned with your value.

Right, like how Micro$lop :

• blocked repository search without login (while it worked before the acquisition)
• pushed in the most traditional Micro$lop fashion for its own product, e.g. Copilot, with in product ads
• use repositories as ways to feed its own set of products, e.g. Azure for OpenAI, in order to push for code generation while ignoring licenses

and all the other things (please feel free to make this list more comprehensive) as “reparations”?

It’s the same old "Embrace, extend, and extinguish " (EEE) scheme they’ve been (sadly successfully) running for decades now.

So happy with my 2nd hand Pixel 8. No BS, ecologically acceptable IMHO and yes runs most Android apps thanks to GrapheneOS.

what breaks the immersion

This isn’t a game, it’s about your freedom, our freedom.

If you want to use Brave to watch YouTube… well I don’t think you really care. The fact that somehow watching a video on a gaming rig isn’t fast enough so clearly not normal. That being said honestly it’s good you did try.

Artwork idea : load thermostat.

You can’t start a new application if your room is above a temperature threshold.

Extension artwork idea : load credits.

If you do delegate some load to a non digital form, e.g reading a paper book instead of watching a movie, then you “earn” some credits you might use to bypass the load thermostat “when you really need it”.

Measure your system, e.g. Zigbee thermometer for your actual room power draw so the plug for your entire system, computer obviously but also screen, speakers, etc even AirCo unit or physical fans if you have some for the room itself.

That’s the only way to know what is actually happening.

If you do not want to go down that path then the heuristic is simple : the heavier the load on either CPU, or GPU, or obviously both, the higher the temperature. If you have a dynamic system, anything built this last few decades or so, then the fans will not kick in under a threshold which you can consider won’t significantly heat up your room.

TL;DR: if you start to hear fans spinning, you have to reduce your load.

Sorry to be that guy but… why? The whole motivation behind PDF is precisely NOT to be edited, NOT to be responsive, but rather to provide the SAME output, mostly text based, anywhere and everywhere.

I’m not saying she shouldn’t edit PDF but I also have to clarify it is not "normal’.

I’ll refrain from recommending anything before actually understanding the motivation behind her workflow.

lol, $100k+… HP revenue in 2024 was $53,559,000k.

Dell same year $88,000,000k and Lenovo $69,000,000k, so ~$50B to $90B

I let you calculate the percentage but… I’d guesstimate it’s approximately nothing.

Upvoted your comment using f to get link hints, then xy (example of label) so 3 keystrokes, no mouse.

Yes. I also use vim here (in this Web textarea where I’m typing this answer) thanks to Tridactyl.

Indeed, I think vulgarization of CVEs for a broader audience should start with requirements.

Few seem to address the issue here : it does not work 100% of the time for you.

It might work for everybody else but that doesn’t help you much. You have your setup, no theirs.

So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check https://lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and journalctl logs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g. dmesg.

They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate :

• what’s your crime scene? Your laptop and it’s log files
• what’s the crime? It didn’t suspend properly
• where are the traces? In the logs
• where are the logs? Using journalctl or dmesg and typically in /var/log/
• what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using grep and other tools

You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window.

TL;DR : grep logs

what about just using Debian? It’s a bit hassle

What hassle? Genuinely curious.