

I just don’t update kde very often since it might force me to re-login or restart. I currently have 9 months uptime so that’s the age of kde connect.
(gentoo)
Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key but modern and easier to use)


I just don’t update kde very often since it might force me to re-login or restart. I currently have 9 months uptime so that’s the age of kde connect.
(gentoo)


Desktop version too old and phone version too new to be affected
(•_•)
( •_•)>⌐■-■
(⌐■_■)
But it saves the command history to disk.
It makes the exit command redundant, so that is removed from the history, but all other commands in all cases but mistakenly sshing into the wrong machine will still be saved.
And some fusion is direct to current in coils. The z-pinch style approaches mainly.


Try my oled theme.

It was on the florisboard theme page but the dev took it down because I made it in florisbord not in a repo


ECC ram. Hardware stability was the main factor.
Real Linus mentions spending days hunting an instability bug in the kernel to have it turn out as bad ram on his pc.


I think it only means if you do get paid reasonable amounts for open source work, you don’t have to pay tax on that.
So between jobs it shouldn’t matter since you wouldn’t pay taxes anyway, unless you worked a lot and received a lot of donations. But if you contribute after hours of a regular job, this would ensure you still get the full amount the foss project receives.
There is also mention of assistance with administration, which I’m not sure what that entails.
Albania will probably join the eu in 2030. Wait 5 years, then simply live somewhere in the eu, maybe even do most of your crimes in the eu, and you won’t ever run into border checks.


The year is 2046, the ntfs4g+±next driver is put into maintenance mode as Linux slowly phases out support for the legacy operating system “windows”.


As long as you don’t run out of memory, you can actually insert and lookup in O(1) time for a known space of values (that we have). Therefore we do get the quadratic speedup, that when dealing with bits of keysize or entropy means cutting it in half.
Checking to get a specific uuid takes 128bit, so 2128 draws of a uuid. Putting all previous uuids into a table we expect a collision in 64bit, so 264. We also need about that much storage to contain the table, so some tens of exabytes.


Against a apecific one too. Usually you’d check for duplicates against all previous uuids


In a way that weakens the open source software world by giving companies a way to avoid the GPL license of linux.
For really no reason, this project gains nothing from being MIT instead of GPL.


MIT license :|


I think they mostly are.
Cache is already in .cache/mozilla, so usually there is no change hence I didn’t mention it. They did move the cache to the XDG_CACHE_HOME by default. And yes they are using the XDG variables including the recommended fallback values.
The line between data and config has always been blurred, Most data in the browser is “data” until a user overrides it. Even extension files presence is linked with their configured state of being installed.
For log files I’m not sure anyone follows that. Besides firefox barely has any plain logs, I think having those in the profile is fine.
Currently it’s all in XDG_CONFIG_HOME


I’ve met some from asia and europe


In practice that should mean running mv ~/.mozilla ~/.config/mozilla.
Of course the old directory will still be detected and used if present, probably for a long time to come.
An octahedron


Everything is a web language if you believe
The entire renewal process is fairly cheap, resource wise. 7 day certificates are already a thing.
In terms of bandwidth you could easily renew a billion certificates a day over a gigabit connection, and in terms of performance I recon even without specialized hardware a single system could keep up with that, though that also depends on the signature algorithms employed in the future of course.
The dependence on these servers is the far bigger problem I’d say.
This shortening of lifetimes is a slow change, so I hope there will be solutions before it becomes an issue. Like keeping multiple copies of certificates alive with different providers, so the one in use can silently fall through when one provider stops working. Currently there are too few providers for my taste, that would have to improve for such a system to be viable.
Maybe one day you’ll select a bundle of 5 certificate services with similar policies for creating your certificate the way you currently select a single one in certbot or acme.sh