There are multiple causes to its demise.
The big one was security (or lack thereof) as attackers would abuse plug-ins through NPAPI. I remember a time when every month had new 0-days exploiting a vulnerability in Flash.
The second one in my opinion, is the desire to standardize features in the browser. For example, reading DRM-protected content required Silverlight, which wasn’t supported on Linux. Most interactive games and some websites required Flash which had terrible performance issues. So it felt natural to provide these features directly in the browser without lock-in.
Which leads to your second question: I don’t think we will ever see the return to NPAPI or something similar. The browser ecosystem is vibrant and the W3C is keen to standardize newly needed features. The first example that comes to mind is WebAuthn: it has been integrated directly in the browsers when 10 years ago it would have been supported through NPAPI.
I meant add support to new robots other than Dreame. On Telegram he explicitly said he won’t support any new Roborock nor Ecovacs
AFAIK Hypfer (Valetudo maintainer) has no intention to support new robots other than Dreame
As a note, Dennis Giese —who is the co-author of the Defcon talk mentioned in the article— is also the author of Dustcloud, which is used as the basis of Valetudo. Though I’m not aware that Valetudo will ever support Ecovacs robots.
Oh yes, if it ends up replacing concrete that would definitely be a win. It never was my intention to dunk on the invention, I just felt that the title was misleading and had an urge to correct it.
Carbon-negative is a long stretch, it’s just using waste material that is usually used as fuel. It’s at best low-carbon compared to concrete, which honestly is already a good thing.
At around the same time, Meyer learned about the large amount of waste lignin that is produced every year, primarily from pulp and paper processes, which is also expected to be produced from biorefineries in the future.
[…] During the production of pulp and paper products, roughly 100 million tons of lignin are produced annually as a waste byproduct and subsequently burned as low-value fuel.
Meyer saw lignin as a polymer that could be used as a material instead of a fuel and sought to crosslink it like an epoxy resin. Using lignin allowed Meyer to sequester CO2 captured from the air in the form of biomass that would otherwise be burned.
(Emphasis mine)
Holy molly, I wasn’t expecting this! Well, I guess I’ll try that out once Electric Eel’s released
TrueNAS SCALE expects you to deploy Kubernetes clusters, it is unfortunately not meant for running plain Docker. You can jump through hoops to get it working but I personally gave up and ended up running a VM on top of TrueNAS just to run Docker on it.
I don’t know about Unraid though and OpenMediaVault felt a bit unpolished the last time I used it and I can’t attest for its ZFS support.
If I understand correctly, it’s just a fancy donation?
Ah yes, classic tech solutionism.
“No need to be frugal, the tech will evolve and fix the causes of climate change!”
We need a solution right now, not in a decade, dumb ass. So frugality is the answer.
Way to push Fortune 200 companies towards Azul, Adoptium, Correto and other alternative Java distributions, Oracle!
Unfortunately improving existing products does not bring additional subscriptions / revenue 🤡
I really like Readeck, it is very polished and the fact that it copies links content is very useful when saving Medium blog posts (and generally to make sure that I don’t lose the content if the linked page is ever removed)
I would have guessed React Native since Meta is pushing it so hard, now I know.
The Contributing Guide isn’t very helpful, but after skimming over the dependencies.gradle file and the repo’s Languages section, I can say that it’s a native Android app written with Jetpack Compose in Java and Kotlin (I assume they are progressively rewriting the app in Kotlin).
I have a completely different experience from yours: it would import random packages or rules and suggest stupid shit that made me disable the feature after less than 10 minutes of use. And again and again after IDE updates would re-enable the feature!
If you use a third-party’s DNS server (such as Cloudflare, Quad9 or Google) as your upstream DNS server, you only have to update PiHole.
If you have set up your own upstream DNS server using a DNS resolver like unbound or Bind9, update it as well as your PiHole.
I struggle to find if it uses DNSSEC or even a change log. If it does, contact the maintainer and disable DNSSEC (if you can) until a fix is released.
They maintain their own resolver, so they have to patch it if not done already.
Dammit Microsoft, you only had one job!