391 karma · joined February 26, 2017
Users who already have the keypassxc package will need to explicitly switch packages if they want the full one. That's not the same behaviour as described in my quote comment.
> I think the proper solution would probably be to package both a "-full" and "-minimal" version of the software and utilize Debian package meta-data fields to define a Conflicts relationship between the packages and tag them also both with a Provides for keepassxc and also add a tag Replaces: keepassxc to the -full build so that during a package upgrade an existing user would be provided the version that continues to provide the features of the package which is being upgraded/replaced while new users can choose for themselves which of the versions they'd like to install
https://github.com/keepassxreboot/keepassxc/issues/10725#iss...
Why would this _not_ be the obvious choice?
Most languages with some amount of popularity have at least a handful of features that I wish other languages did as well and that can feel, at least in the moment, to be completely obvious and critical features that every language needs.
However, many editors can accomplish the same goal by highlighting or changing the text colour of todos.
Those will let you get the most out of an efficient heat pump.
If I took baths every day then it might become a problem but once a week or so had had no negative effects.
I paid to heat that water up, so I damn well want to get as much out of it as I can.
The fact that this hasn't been exploited in the wild much is good, but doesn't mean that the advice is wrong. Unless the vulnerabilities themselves are all patched it _will_ be exploited in the wild eventually.
If there was a relatively turn-key solution that people could deploy it might help wean people off of cloudflare.
You might not be able fully "run it out" given the speed, but every step you take when bailing is a good thing and rolling out after you take a few steps will help as well.
At the end of the day, it's obviously going to be more dangerous than a bike or a scooter, though. My issues with future motion is more to do with their extremely poor response to design flaws, though.
I think that riding at more reasonable speeds and riding with focus and awareness is still reasonable, but the faults we've seen add hidden risks that are difficult to address as a rider.
It can use type-c _or_ a barrel-jack DC adaptor.
If Ted Bundy and John Wayne Gacy founded a company together then your headline would make sense, but I don't understand why this would compare to anything the author of this article wrote.
The economics are totally different, though. The "product" is very high value and has a short shelf life, so being able to deliver it quickly is a big benefit.
On top of that, using a fixed-wing delivery vehicle and launching it with a human-powered slingshot makes it actually reasonably energy-efficient.
I was neither supporting nor opposing the idea of disabling the ability to use S3 publicly. While I agree with the new default I would not support removal of the feature.
I believe Cloudfront also still has a free tier which cuts out egress fees on the first X GB of data.
When testing with my own cards, I was able to read card number, expiry, and currency which is enough in many countries for it to be considered a card skimmer.
If there are existing manufacturing processes that can be leveraged to build cells with this chemistry—and do so economically—then commercialization could happen very rapidly.
Otherwise, it's likely to be filled away until future manufacturing technology comes along, which may be "too late" if even better or more economical options exist at that point.