News for hackers. Stuff that matters.

jonoc

Re:Restructuring GitHub's bug bounty program on Thursday July 23, 2026 @01:17AM (#49017230)
I get the joke, but I don’t think GitHub is treating one type of person as inherently more deserving. They’re paying for signal and reduced triage cost as well as the vulnerability itself. AI makes it incredibly cheap to flood them with plausible-looking false positives, while their investigation capacity is finite.
I'm not making a stance on things, just clarifying the previous comment
Not sure this is correct - alaq said the messages are e2e, so not visible at all by anyone other that the participants of the conversation. The meta->data<- however IS visible by them and can and is likely to be used for advertising.
Re:Some thoughts on LLMs and software development on Thursday August 28, 2025 @11:23PM (#45059794)
thats a fascinating way to put it
"Even if I believe that what I'm doing is morally correct and legally protected, legal processes still have a financial cost. I can't afford to take on that financial risk for something that I do in my spare time to help others." - this is very logical and exactly what I would have done but it still makes me very sad that this is the way the world works right now :(
Re:A step by step guide on how to become a DevOps engineer on Sunday October 30, 2022 @05:01PM (#33398633)
You are not crazy - you can definitly specialise. Though I think this is a good way to find out areas you may be interested in
Re:TailwindCSS v2.0 on Wednesday November 18, 2020 @02:48PM (#25141539)
The problem I have with pure CSS is it relies on the fact that you and your team are experts at CSS, which is almost never the case. Pure CSS with an unexperienced developer can lead to spaghetti pretty quick. There are always limitations with any approach, including frameworks, but on a team with more than 1 developer and long term maintenance in mind I'd prefer to go with a framework more times than not.
Not sure I agree with this due to the fact that all projects are different and such their tooling requirements will be different. I don't think it's fair to just apply a blanket rule of 'use fewer tools' - this tends to end up with people writing their own implementation of existing tools which then turns in to tech debt so it's kind of a void argument.
This assumes everyone is using GitHub and VS Code - I think the main issue is applying it to the node ecosystem as a whole
I'm guessing it's a tongue and cheek way of saying "why be resistant to change without reason?"
Yes this runs of linux and macos now. dotnetcore is multiplatform. It doesn't use Mono.
Re:Clarity Design System for Angular 2 on Wednesday November 16, 2016 @02:41AM (#12965198)
Looks very nice. I've hated angular material docs due to the overly complex examples. These are simple and to the point. I'm keen to try this out for my next a2 project :)