https://github.com/madmalik/mononoki/blob/main/LICENSE

It should be offered as an option really.

One caveat is that you need to think ahead about how much space you want to assign to each partition. You could end up with your /home/ partition being full while the system partition still has plenty. Or vice versa. You can manually readjust the boundaries but it requires some understanding and can’t be done on the fly by a non-technical user. By contrast if everything’s stored on the same partition you never have to worry about this.

You can, by the way, manually recreate this set up even after the initial set up although it will require lots of free space to shuffle around files (or some external storage to temporarily hold them). Basically what you do is create a new empty partition, copy all your /home/stuff there and then configure your system to always mount that partition as the /home/ directory when it boots. Files are just files after all and the operating system doesn’t really care where they come from as long as the content is correct. Once you got it working you can delete the originals and free up the space to be used otherwise.

Typically your personal files and app settings are stored somewhere in your user home folder, eg under /home/bob/. Ideally you’ve set up your system in a way so that the entire /home/ folder is stored on its own disk or partition at least. That let’s you boot up a different distro while using the same home directory. But even if you haven’t set it up separately from the rest of the system, you can still manually copy all those files.

Not every single application setting is transferable between distros as they sometimes use different versions but generally it works well. Many apps also let you manually export profiles or settings and reimport them elsewhere later. Or they have online synchronization baked in.

One reason to keep in mind is backwards compatibility and the expectancy that every Linux system has the same basic tools that work the same.

Imagine you have a script running on your server that uses a command with or without specific arguments. If the command (say tar) changes its default parameters this could lead to a lot of nasty side effects from crashes to lost or mangled data. Besides the headache of debugging that, even if you knew about the change beforehand it’s still a lot effort to track down every piece of code that makes use of that command and rewrite it.

That’s why programs and interfaces usually add new options over time but are mostly hesitant to remove old ones. And if they do they’ll usually warn the others beforehand that a feature will deprecate while allowing for a transitional period.

One way to solve this conundrum is to simply introduce new commands that offer new features and a more streamlined approach that can replace the older ones in time. Yet a distribution can still ship the older ones alongside the newer ones just in case they are needed.

Looking at pagers (programs that break up long streams of text into multiple pages that you can read one at a time) as a simple example you’ll find that more is an older pager program while the newer less offers an even better experience (“less is more”, ¿get the joke?). Both come pre-installed as core tools on many distributions. Finally an even more modern alternative is most, another pager with even better functionality, but you’ll need to install that one yourself.

ouch stands for Obvious Unified Compression Helper.

great name

I just use atool (archive tool) instead. It works the same for any common compression format (tar, gzip, zip, 7zip, rar, etc) and comes with handy aliases like apack and aunpack obsoleting the need to memorize options.

Many do as it’s considered good practice, but it’s not guaranteed, it just depends on the individual command (program). Usually you can use the --help option to see all the options, so for instance tar --help.

In case your browser isn’t completely locked down: there’s also image editors that run as web apps like photopea.

The part that confuses me a bit is that it’s a mod that removes functionality from a single player game. Usually features get added, not removed. When something is removed it’s usually to improve stability or performance. Or to rebalance the gameplay. This change falls into none of these categories.

Well I guess if the mod author did it to garner attention or make a point he/she/they succeeded.

Good point.

I guess just having a staggered temporal restriction is fine, don’t need to wait until you retire necessarily. You would still receive a portion of your salary package in the form of classic currency and plenty for a good life too. An example could look like this and I’m obviously making up the percentages and durations here, they would need to be fine tuned:

• 40% of salary as cash
• 10% of salary as stocks that can’t be sold within 6 months
• 10% of salary as stocks that can’t be sold within 12 months
• 10% of salary as stocks that can’t be sold within 18 months
• 10% of salary as stocks that can’t be sold within 24 months
• 10% of salary as stocks that can’t be sold within 30 months
• 10% of salary as stocks that can’t be sold within 36 months

I guess it would be best to change the rules so that they cannot trade their company stocks at all while working there and a reasonable period beyond. I think some legislations already restrict floating stock like that but I’m no expert on the matter.

You do realize that a lot of employeess that stayed at Twitter after Musk’s take over did so because their work visas were tied to the occupation and otherwise they would have had to leave the country on short notice?

but the proposal does not yet spell out what constitutes a violation.

and this is not a coincidence. Authoritarian states love vaguely operationalized definitions like this because it’s basically a blanko check to arrest anyone at any time. And it puts the populace into a fearful, fatalist mindset of “I could be arrested at any time for bogus charges, even if I did nothing wrong.”

Man am I glad that I picked KeypassXC as my password manager some years ago. Super safe, easy to use, costs nothing, not dependant on internet/cloud, can export data to another app at any time, transparent because open source.

I’m using Syncthing to synchronize across devices which arguably took some fiddling to set up but I only had to fiddle once and haven’t touched the configuration since; it just works automagically in the background.

Open Dyslexic has you covered. It was designed by experts for this purpose.

It’s so dumb that JSON doesn’t officially have comments.

So much this.

Used to work at a company where I sometimes had to manually edit the configuration of devices which were written and read in JSON. Super inconvenient if you have to document all changes externally. As a “hack” I would sometimes add extra objects to store strings (the comments). But that’s super dicey as you don’t know if it somehow breaks the parsing. You’re also not guaranteed the order of objects so if the configuration gets read, edited and rewritten your comment might no longer be above/below the change you made.

Always found it baffling that such a basic feature is missing from a spec that is supposed to cover a broad range of use cases.

Interesting. In German typography we used to use lower quotation marks at the beginning of a quote and lower quotation marks at the end of a quote, both in handwriting and print:

„Amazing“

But the lower version isn’t found on the default QWERTZ keyboard layout so in personal digital communication (instant messages, emails, etc) especially you find double upper ones a lot:

“Amazing” or ‘Amazing’

The formal spelling rules haven’t been updated and you may still find the lower-upper vision in professional publications where the software adjusts the quotation marks according to a global setting. But most anything that is typed directly by a user will use the lazy lower-lower version.

Well at least it consistently unlogical. But wait: it actually depends on the grammatical case for example:

die Mädchen = the girls das Haus der Mädchen = the house of the girls // the girls’ house

So depending on context male, female, neutral articles are all used (der Mädchen, die Mädchen, das Mädchen) 🤷‍♂️

Wikipedia confirms, in particular on this page on the expression ye olde.

Also bonus content:

singular: “das Mädchen” (neutral) - the girl

plural: “die Mädchen” (female) - the girls

So in the plural form you have to use a female article again, but the actual spelling of the word is unchanged. Go figure 🤷‍♂️ 🇩🇪.