During lunch a friend mentioned that you can just supply a HTTP URL to vim on the command line and it would use curl to download that resource and allow you to edit the content. I jokingly asked whether if you enter :w it would then issue a HTTP POST back to the origin which is of course ridiculous.
It issues a PUT
WARNING! This image may trigger PINSecurity.
From an analysis of 3.4m PIN code leaked from several data breaches https://informationisbeautiful.net/visualizations/most-common-pin-codes/
[Well-Typed Blog] Improvements to the ghc-debug terminal interface
`ghc-debug` is a debugging tool for performing precise heap analysis of Haskell programs (check out [our previous post introducing it](https://www.well-typed.com/blog/2021/01/fragmentation-deeper-look/)). While working on [Eras Profiling](https://www.well-typed.com/blog/2024/01/ghc-eras-profiling/), we took the opportunity to... #haskell
https://www.well-typed.com/blog/2024/04/ghc-debug-improvements/
“When drivers fail to yield for pedestrians, it’s not because they can’t see them, it’s because they don’t care.” Kudos to @VisionZeroYVR for this brilliant intervention. https://momentummag.com/vision-zero-campaign-bricks-vancouver/ #TheWarOnCars
Do you want to stop "supply chain compromises" as a company? Here's a very simple way to do so: pay a stipend to a maintainer of something you depend on.
You don't really need dependency tracking tools. You don't need to exactly parcel out the 'right' proportionate amount of money to every maintainer. All of that operational complexity is unnecessary.
It doesn't even matter *which* maintainer you pick, as long as it's one who isn't receiving a stipend yet, and you pay them enough to constitute a salary.
It will cost you exactly one developer salary. If every able company does this, the problem of supply chain compromises is solved tomorrow.
All you need to do is simply *do it*, and talk about it so that other companies will too.
If you had code on GitHub at any point it looks like it might be included in a large dataset called “The Stack” — If you want your code removed from this massive “ai” training data go here:
https://huggingface.co/spaces/bigcode/in-the-stack
I found two of my old Github repos in there. Both were deleted last year and both were private. This is a serious breach of trust by Github and @huggingface.
Remove all your code from Github.
CONSENT IS NOT OPT-OUT.
Edit — thanks for all the replies. More context here: https://hachyderm.io/@joeyh/112105744123363587
Also the repos i found of mine i’m sure were private, but even if they were public at some point, for a brief time, in the past that isn’t my consent to use them for purposes beyond their intent.
---
Edit 2 -- I see this made it to HN, which is a level of attention I do not want nor appreciate....
For all those wondering about the private repo issue -- No, I am not 100% sure that these ancient repos weren't at some point public for a split second before I changed it. I do know that they were never meant for this and that one of them didn't even contain any code.
If my accidentally making a repo public for a moment just so happened to overlap with this scraping, then I guess that's possible. But it in no way invalidates the issues, and the anger that i feel about it.
history = (λx. x x) (λx. x x)
When life gives you lemons, don't make lemonade. Make life take the lemons back! Get mad! I don't want your damn lemons, what the heck am I supposed to do with these?