Earlier this year, researchers from security firm Avast spotted a newer FudModule variant that bypassed key Windows defenses such as Endpoint Detection and Response, and Protected Process Light. Microsoft took six months after Avast privately reported the vulnerability to fix it, a delay that allowed Lazarus to continue exploiting it.
Dammit Microsoft, you only had one job!
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)
I’m pretty sure the EU Commission will have something to say about this
I’m surprised Datadog is that much of a money maker to be able to afford GitLab
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.
I believe there is a exponential backoff mechanism in place if an instance cannot push to an other’s inbox, so other instances may not have any attempt left to retry if it has been two days. In my experience un-subscribing then re-subscribing to an instance’s community was enough for it to send posts after a few hours.
Do you have any particular blocklists enabled besides the default ones? Try disabling them one by one until you find the culprit, then report a false positive to the list’s maintainers.
What was the issue then?
Oh, do you run the Docker commands as root?
You should login with an Access Token rather than your password. You can generate a new Access Token here.
Are you logged into Docker? What’s the output of docker login
?
I think the local caching was intentional to reduce load on remote instances, should we disable it?
Exactly. Currently Lemmy copies thumbnail and images from remote instances locally.
If you go for RAID, I would advise for software RAID rather than hardware (i.e provided by your motherboard or a physical car). Hardware RAID will lock you to the particular motherboard or RAID card, which would represent an additional hurdle when upgrading or replacing it.