If you watch the PRs history, you can see that the user github-actions edited them. This user is the default one when a GitHub Action (the pipeline OP refers to) alters the repo. So someone probably submitted a pull request abusing the GitHub token when the Action ran on their PR.
Unfortunately you can’t follow users on Lemmy. On Kbin, Mastodon and others, you can follow Bluesky users through Bridgy Fed but they must opt-in first by following @ap.brid.gy (which very few people do)
Okay, that makes much more sense.
Wait, is it required to mirror the entire Bluesky history? Can’t you just store only new messages? Because the storage requirements (4.5TB according to the article) make it almost impossible to self-host.
TIL that Schneider Electric is a French company. I always assumed it was American or Swiss.
I have been contemplating moving to SearNXG for a few weeks, but I have a hard time finding whether I can configure things like domain down-ranking/blocking or custom bangs and lenses, does anyone know if you can do that on a user or instance-level?
I still don’t get why Strava activities are public by default and why they do not make their users aware of it. I remember having to rummage through the settings to make activities private by default.
If you want an experience similar to Arc without the AI nonsense, there is Zen Browser, a Firefox fork with vertical tabs, profiles and side panel.
Parents, maybe? They are usually so concerned about children’s safety, whether that’s their kids or someone else’s.
It will end up being analogous to Uber and Lyft, and neither helps reducing the amount of cars on the road.
Also it doesn’t respect robots.txt (the file that tells bots whether or not a given page can be accessed) unlike most AI scrapping bots.
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.
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.
Most likely someone submitted a pull request that abused the GitHub token of the Action running on new PRs in order to edit all the other pull requests.