1,093 karma · joined November 7, 2022
* author forgot to renew the cert like, day before
* author also set up HSTS and both browsers said "nope, we won't even let you add exception for this one".
I wonder how that correlates with companies bragging that they only take day or even few hours to have new hire code landing at production "coz they are so agile"
Sure normally it is a joke but this one in particular does look like something that would actually be worth something to the right buyer
> More than half of all new packages that are currently (29 Mar 2023) being submitted to npm are SEO spam. That is - empty packages, with just a single README file that contains links to various malicious websites.
Yeah once you cut the obvious they will get smarter but at least some will leave to look for other easier target.
Spammers just try to find something that ranks high in SEO and costs them nothing, if repository stops being that most will leave. Most other package repositories don't have that problem to such degree
> unlisting a valid package could break project
... and about packages that most likely are NOT used as dep anywhere
> Let’s say there’s 10 spam uploads per hour and it takes you 1 second to verify a package is spam and remove it. That’s 30 minutes a week just dealing with spam. While I was on the .NET package manager, we had the on-call engineer handle this thankless chore.
No need. Just add flag button where a package can be flagged for a check. Users will do the flagging for that so at least you won't have too many valid packages to verify
> Could you detect these packages at upload time? Yes, but spammers will change their patterns once the package ecosystem gets too effective at detecting current patterns. Perhaps machine learning could help, but often times package manager teams are small and don’t have expertise in this area.
With AI I'm afraid it might get awfully close to "newbie user just publishing package full of shit code"
Coz you might want results not only from docs but stackoverflow and other places ?
> Essentially, there is no overlap in the Venn diagram of "searching for a package" and "searching for information about a package". You want one or the other, not a results page with links to both.
Of course there is. I want docs, examples, and maybe opinions vs alternatives if I look to solve problem X with external dependency.
Difference is really that the open design could be repeated way before design based on existing part would go out of produciton.
That requires 1:1 DB user to real user mapping + one connection to DB per users, it is entirely horrible performance-wise, which is why it is so rarely used for anything more than separating apps from eachother.
It's good news for RV, even more reasons to ditch ARM
There are plenty of tools to either keep them encrypted (we just use simple GPG, but our team is small) or just auto-generate and never show to user in the first place (various key vaults that can be used from automation like HashiCorp's Vault)
This isn't even politics per se, just feel good activism, the "I'm helping", while doing absolutely nothing that helps in the topic). Equivalent to thoughts and prayers.
"I hate them so I will only give them a tiny bit less money" is why it will never change
I found a fake sensor like that once.... was wondering why my code done by datasheet didn't worked on cheapo breakout board I bought off aliexpress.
Then I read ID register and they used older chip that had some of the stuff set up differently...
But yeah, especially now with various ESP32 firmwares like ESPHome you can essentially just make a YAML with specification on where to listen and what bit to flip and get simple switch/controller with zero actual coding.
There is even custom firmware to turn off-the-shelf IOT devices to work with "open" standards.