I’m here to stay.
I guess you meant this as a joke, but for clarification, I meant no big changes such as new desktop edit mode. I wish the team would just focus of bug fixes and enhancements without introducing new elements or changing things up in a big way like this.
I use tar with a an external file for exclude and include files on my custom backup script. There is a --wildcards
option, which lets you use *
(star) to exclude everything from a directory. The command looks like this:
tar --create \
--zstd \
--verbose \
--restrict \
--force-local \
--wildcards \
--exclude-backups \
--exclude-from "${exclude_file}" \
--files-from "${include_file}" \
--file "${archive_file}"
And the include_file is a simple text file with newline separated paths. It looks like this:
/home/tuncay/.var/app/io.gpt4all.gpt4all/cache/*
/home/tuncay/.var/app/io.gpt4all.gpt4all/data/*
deleted by creator
deleted by creator
I wish the team would just spent an entire year of bug fixing and refining user experience without adding new features or making big changes such as the new desktop edit mode. Don’t get me wrong, this is super exciting too, but for the complex nature of KDE it would be good if they keep a bit of focus after a major release.
It just came to my mind, that WINE not only stands for Wine Is Not an Emulator, but also could be interpreted as: WINdows Emulator.
OBS is clunky and complicated to me. The Canvas and Output resolutions are separate, which confuses me the hell out of it. I only experimented with some settings so far to record gameplay (after my new PC installation) and need to see how this works out. But if I change settings to record something different, then I have to configure it again to record gameplay. Also to use Hotkeys, I have to allow hotkeys to be used globally in my system (which I don’t want to otherwise). Because of Wayland and how it works.
All in all its must simpler and superior to do this in Steam itself now. For other use cases, I will still keep OBS, its not bad, just not straightforward for daily game recordings. But I can add other software and games to Steam and can use it with Steam Recording too (if the overlay works there).
As others noted, this has background recording functionality and manual on demand recording as well. I have used manual recording software and still have OBS installed for any use case. But having Steam Recording builtin is very convenient.
All of this is builtin and works the exact same way regardless of operating system and hardware (independent from cpu and gpu and os). No one needs to study hardware and software in order to configure it in the best possible way. If you used this on Windows, its the same on Linux, no dependency of recording software.
This is a much bigger deal than just recording footage with gnome-screenshot.
The new logo is too symbolic. But it scales better. I like the old one more though.
Its huge for me, because in Linux I can only record through OBS. And OBS is suboptimal, compared to a builtin solution like this. On Steam Deck I used the plugin too, but had to remove it again, because the plugin system stopped working.
Sure, a few more settings wouldn’t be bad, in example for saving as video file. But I think for the sake of simplicity for the end user and also for the devs themselves (I mean Steam devs) they kept it a bit barebones when it comes to codec or resolution settings. This has to work on Windows and on Linux (not sure about Mac) and on the Steam Deck out of the box.
It’s still beta and they already said in the article some features are coming. I’m more than happy with the timeline feature, this is amazing. I set it to 16 hours at highest quality, lol.
Its built-in and therefore independent from gpu and driver or additional software, and independent of the operating system, it even works on the Steam Deck out of the box. This is a feature I waited long time for.
The image does not doing a particularly good job in explaining whats wrong with X. It just shows how it functions and why a rewrite in Wayland is needed.
By that description, Ubuntu does the same, matching the release cycle of non LTS Ubunu versions; every 6 months with breaking changes (just like Fedora). The difference to Fedora is, that Ubuntu users do not need to upgrade to the next major version, while Fedora have to, because there is only one version.
Tiling: Add fallback path for the first Polonium tile. Commit. Fixes bug #488898
I’m a little bit surprised or confused here. Polonium is an external script. KDE/Kwin specifically addresses scripts? That’s actually wonderful, totally the opposite of what Gnome does (yes, I had to bring it up).
I stopped using Polonium, as it does not work perfectly fine for me. I’ll let them cook a bit more, its otherwise an excellent script/addon.
There is no single Bash standard to follow, only a few guidelines. One way you can check for some basic errors and formatting would be using an editor with support for Bash (in best case with a builtin LSP). At the end, you have to find your style and coding standards or adapt what others do if you want work with them or edit their files.
${variable}
and some other things.BTW the mk-blog link is 404 for me.
https://www.laws-lois.justice.gc.ca/eng/acts/C-42/page-6.html#h-103344
Assuming this is the correct source for Canada’s law about copyright. In the section about backup copies 29.24 (1):
( c ) the person, in order to make the reproduction, did not circumvent, as defined in section 41, a technological protection measure, as defined in that section, or cause one to be circumvented; and
( d ) the person does not give any of the reproductions away.
So (d) means it is not allowed to distribute the backup copy. As far as I understand. This is standard in most countries in the world. Also I cited ( c ), because this is usually also standard law. Normally, you are only allowed to make backups, if you do not circumvent any protection. Well its up to the interpretation if the Switch has such protection measure that falls into this category. But still, for our topic, (d) is relevant and seems to not allow for distribution of backup copies.
Mind you, I am also not a lawyer. And not everything needs to go to court in order to have an understanding of the law. Off course, unless it is a bit of grey area like in the case of ROMs. But I think this is addressed in the above quote. I hope this is the correct source! So for the time being, I have to assume law regarding this is just the same as in most other countries, because there is nothing else for me to evaluate here.
You misunderstand me. They can write new code and be ready when the bug hunting phase is over. The end user only gets bug fixes. Later they can backport any new feature after the phase.