![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/
1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/
Trouble with those tests is, that they become unreliable or even meaningless, when you have done then once before, let alone daily.
When I installed Kinoite to start using Linux as my primary daily driver, the first thing I did was setting up Ansible, creating a new playbook and all Linux configurations I made from that point on, are only ever done through that playbook, which is backed up in my Forgejo instance. One command and everything is being set up exactly the way I want. It feels extremely liberating.
Windows hss supported slashes in both directions for a very long time. I almost exclusively use forward slashes to reduce mental load when switching between OSes.
The original author of git flow begs to differ. But hindsight is always 20/20 https://nvie.com/posts/a-successful-git-branching-model/
If you use feature flags, don’t forget to remove them after some grace period. Almost everything bad about feature flags that you can read online is related to long-lived feature flags and all the dead code and complexity involved. Adding a feature flags without a commitment and plan to remove them (the flag, not the feature), is asking for trouble down the line.
You can implement public or semi public ledgers without Blockchain. That’s what banks are doing already by sending huge CSV files internally and externally. Blockchain is not a technology of zero trust. It’s close to the opposite. You trust a few peers and blindly trust everyone they trust. That way you trust a network that you know nothing about and if the network decides on a common truth that you are convinced is incorrect, there is nothing you can do about it. The consensus always wins and there is no single entity to complain to and get it fixed. This is great for making sure that many actors need to be bad actors in order to have the whole system fail. It’s bad if you don’t trust anyone and want to make sure that your standards are always observed. From a technology standpoint I love the concept of Blockchain. But use cases that are not forced are few and far apart. Too few for the amount of hype it receives.
It depends. Some hardware degrades gracefully while my current desktop system won’t even boot and throws error codes on an empty battery. It took me hours to figure out what was wrong the first time it happened.
Yeah, it’s the same for me. The content is awesome but requires a lot of concentration.
As you mentioned, with Fedora the best alternatives are immutable spins. Updating means downloading a new base image, applying overlays and additional installations to it and on the next reboot you start from that image. You can configure it to keep as many previous versions as you need and boot into those directly on startup. Since you never change your current image once it’s built, you can’t break a known good system. You can only ever break your next version and in that case, just boot the previous.
I’ve created an Ansible playbook that configures a vanilla Kinoite the way I want it. No need to back up the system if I can recreate it with less than a megabyte of text files. Secrets are in my password vault, personal files are in my personal cloud and get synced to and from the laptop continuously. I would never go back to backing up system files as opposed to recreating it with a playbook. That seems so wasteful in hindsight.
Flatpak with Fedora 39 must have come a long way. Almost every tutorial with workarounds or discussion of broken features you can find online is now obsolete. It just works out of the box, especially under KDE. Mostly. That makes searching for actual issues extremely hard because I find myself chasing down paths of issues that have long been resolved.
Yeah, I removed Firefox from the layers as well and use it via flatpak. Somehow that felt appropriate from a security perspective, to have it sandboxed.
Fresh and most up to date kinoite installation last week, based on fedora 39. The problem is not Linux, it’s proprietary codecs and Firefox’ hesitation to enable hardware decoding on Linux by default. It’s not difficult to get it to work but it simply does not work out of the box.
Linux, browsers, and hardware accelerated videos on the web don’t go along well out of the box. Which is a total shame.
The Lenovo business models (ThinkPad series) are amazing value. My 11 year old laptop is still going strong.
Just stay far away from any Lenovo non-business models.
The Tesla truck is already there and just needs to be built at scale.
Full self driving has been fully achieved in 2017 and will reach end consumers next year (as claimed by Tesla every single year since then).
It is desirable that SpaceX rockets fail hard instead of succeeding in their missions.
Musk has truly mastered this principle and only now are people getting impatient. Most investors still regard him as too big to fail. Either Elon will be able to present sufficient success in the next few years or that bubble will burst very violently. He has almost used up the good will he has built up over years (earned our not).
Maybe the scene is set in the UK.
The horror lies in the final sentence
I believe not. The question states “keywords” so it seems they want to try combinations of words they commonly used. And it makes a huge difference if the script can try one password per second or dozens/hundreds/more.
Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.