typically attacks happen when the URL for the source code or binary gets changed significantly... or like in this attack someone adds something to the post_install section which does something like add an npm install command. a lot of updates for binaries are just version bumps and SHA hashes changing which are easy to vet if you trust the source to not be compromised.
The bottleneck, in my case, was indeed the poorly designed GUI of JetBrains and VSCode versus CLI. By migrating to CLI, I have abandoned intelligent queries as well. This project seems like a bridge: it preserves CLI, but restores the queries.
This is a promising road that I would probably not take. I have learned to live with simple per-line regular expressions. I have never felt that they slow me down.
In fact, the opposite is true: they let me craft fuzzy queries clearly, i.e., to balance the fuzziness across the query. I’ve never learned to do that with the black-box intelligent queries, which severely limited my scope in the past.
We’re not talking about security researchers here:
> there is lots to gain from being the first to write about the new malware on some registry, so *companies* are actively downloading and inspecting literally every package.
>We’re not talking about security researchers here:
we are.
"companies" in this context is "security companies" (hence why they are "downloading and inspecting every package", which would not make sense if referring to the people authoring and shipping a single package)
the thing for me is I started using the init system and while it was fine it always felt brittle for some reason. systemd feels solid and robust like it was well thought out. maybe i'm off base and didn't know how to use init effectively but it was my feeling.
that and cron always felt fragile too with a lot of quirks and limitations you had to work around instead of being a robust thing from the start.
It's useful for me to have a "production" website remote that i just run on my computer for myself locally. rsync could also work but tagging with rollbacks make it easier if something goes wrong. it's not a common thing but it's nice to have that as an option. just because you can't see the utility of it doesn't make it useless
I came here to say this. I'm highly confident the site was built with Claude. I asked Claude how it was built and Claude was confident it was built with Claude. Kind of ironic, honestly.
> I also think Americans have the right to decide what happens in their neighborhoods.
I agree with this.
At the same time, all of the data center proposals in my state are in remote locations nowhere near any residences. They’re still the target of protests.
Just because a data center is way outside your neighborhood; doesn't mean it can't have a direct impact on you personally. Electrical and water resources used can affect your utility bills.
But there is also some hype about just how much it will affect you, that is not necessarily true.
I don't know that local control is an unalloyed good. The interstate highway system would never have been built if we followed this as a principle, for example. For another example, Californian voters consistently vote for state level increases in housing, yet locally consistently vote against increasing housing in their community.
At some point national and state level goals must supercede local control if progress is to ever be made.
reply