This was me in 2013…
This was me in 2013…
I… Mean… You obviously don’t, but whatever.
Sorry. I apologize.
It’s frustrating trying to explain the same thing over and over again…
The tokens are how drm works. The process of DRM is token validation and enforcement of intellectual property rights granted by tokens.
I don’t know how else to explain it. It feels like I am back at my original post. I don’t know if you understand any better or if you still have misconceptions about what NFTs are or what DRM is or if you still think there is some magic in NFTs.
Again, all of this already existed and will continue to exist with or without blockchain. There is very little novel in the implementation details of the tokens. The people who got the idea for "nft"s didn’t come up with a new idea. This isn’t some new math. The only portion of NFTs that is new is the cooperative signing… Which again, isn’t a new concept either.
Right now, everything you described… Literally all of it… Ubisoft implements for their launcher and enforce with their drm solution.
Nfts, digital tokens, already exist. Their use, in the protection of copyright, is called drm. “Nfts” bring nothing new to the table of digital rights or copyright… And a whole host of stupidity.
To be clear, it is kinder. Not much, but it absolutely is kinder. Pasture raised is what free range should have meant… But fortunately we have a word for it now.
Generally yes with two huge caveats.
First, It has been widely demonstrated that diverse teams are more productive and produce higher quality products than homogeneous teams.
Second, selection criteria is heavily biased towards homogeneous teams and has also been demonstrated to stifle innovation.
Desire/inspiration is nearly as important as capability and non-optimal teams (according to most, if not all selection criteria) will consistently outperform “optimal” teams in any tasks that require innovation.
Without knowing the exact model it’s difficult to know for certain but you can buy off brand refill kits with chips. The printer may intentionally degrade quality with the aftermarket chips (and may never reset itself even if you return to official toner)… HP is just a terrible company.
Have LTS kernels started backporting non security fixes like this? To be fair I haven’t looked at this in over a decade but this kind of patch wouldn’t have been backported then.
This is one of those comments that causes Arch to get the reputation that it does. You aren’t wrong and you probably don’t intend to be off-putting but here we are.
Red Hat and Debian both backport security fixes but don’t backport things like laptop device support. It can take a year or more for versions of those distros to gain the kind of functionality that is looking for.
This is an excellent answer. My eli5 addition is this:
It depends on your distro. Distros that do more hand holding and more compatibility without additional operator involvement will be more likely to backport or use a stable kernel with backports like these. Examples: Ubuntu/Fedora/Mint. Distros that focus on system stability will take much longer to integrate backports like these, ex: Debian. And masochists will tell you to do it yourself, ex: lfs, arch.
You couldn’t pay me to use this…
You are making just such a weird argument and it sounds like you are retroactively trying to salvage a bad position because you made a mistake.
If you care strongly about audio quality. A built-in doesn’t have any quality guarantees… why then does usb vs hat matter?
If quality is your concern why bring up price in the first part? It is blatantly obvious that cheap parts *might" equate to cheap quality. This is blatantly obvious.
Obviously there will be USB solutions that are equal or better solutions than prebuilt rpi dac hats since the primary dac hats are exceptionally niche.
This response just sounds like you got caught out in your mistake/bad argument. Why be a dick about it?
This is exactly why having a couple of big instances is so beneficial. I don’t want to have to manage the infrastructure of Lemmy. I don’t want to think about banning instances for csam in particular. I want to be able to go to a place that has a set of rules I understand and that takes care of it for me.
Honestly, I don’t think there needs to be a discussion about defederation anymore… maybe a non-stickied post… but the people who are against it need to leave / get over it. To the rest of us sane people, defederation is 100% an obvious necessity in an open social structure where things like csam even exists as a possibility. Even something as benign as bots is reason enough to defederate.
Just do it. We don’t need to agonize over it or talk about it anymore. There are a lot of assholes in the world. I don’t need to engage with them.
And yet, somehow there is still a bug in the datetime implementation.
Wow. I’m honestly surprised I’m getting downvotes for a joke. Also, no. It isn’t. It really isn’t.
Also Go: exceptions aren’t real, you declare and handle every error at every level or declare that you might return that error because go fuck yourself.
For lithium batteries (phone batteries) it’s actually more important than draining to 0. Many studies indicate that the average phone battery should last several thousand cycles while only losing 5-10% of total capacity provided it is never charged above 80%. Minimum % (even down to 0%) and charge rate below 70% is also unrestricted.
The tl;dr is that everytime you charge to 100% is the same as 50-100 charges to 80%. Draining a lithium chemistry battery to 0 isn’t an issue as long as you don’t leave it in a discharged state (immediately charging).