Funny, because last time I said I thought it highly suspicious that GrapheneOS supports only hardware built by a surveillance corporation, I was told tinfoil hat.
I am also one of those people who "don’t usually do a lot of networking stuff", so here's a question.
The article contains this:
#replace eth0 with the interface open to the internet (e.g might be wlan0 if wifi)
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
However, I use mullvad and the .conf files that they provide contains none of this, and works just fine. It contains just: interface, private key, address, dns and peer public key, allowed ips, entrypoint.
For the courts, it seems it's the opposite.. Meta, Anthropic and others seem to be getting away with terabytes of piracy, on a much larger scale than the typical consumer
I've already connected the dots of the HN zeitgeist. Besides this was done by a few individuals at Meta, or are you thinking they had a board meeting and shareholder vote on it?
even if we completely ignore organizational structure, do you truly believe not holding companies accountable for a few rogue employees is a good call? Is it too difficult for higher-ups to blame the rank-and-file and arrange scapegoats in the opaque black box that is a corporation? and even still, we can ignore this potential precedent and focus on motivation only: if an employee uses illegal means as a tool to reach their work goals, isn't an investigation into said work goals and culture warranted?
This is all already happening, that's why we know about it. But there's also nuance. Was piracy Meta corporate strategy, as implied ad nauseam on here, or was it some guy taking a shortcut?
Is it actually bad that Meta trained their AI on books? No, court already decided that it's substantially transformative and doesn't harm the publishers. Should Meta employees have stolen the books? No, obviously not. The middle men need their cut.
I keep seeing people saying how amazing it is to code with these things, and I keep failing at it. I suspect that they're better at some kinds of codebases than others.
> I suspect that they're better at some kinds of codebases than others.
Probably. My works custom dev agent poops the bed on our front-end monorepo unless you're very careful about context, but then being careful about context is sort of the name of the game anyway...
I'm using them, mainly for scaffolding out test boilerplate (but not actual tests, most of its output there is useless) and so on, or component code structure based on how our codebase works. Basically a way more powerful templating tool I guess.
Downside: lots of Python, and Python indentation causes havoc with a lot of agentic coding tools. RooCode in particular seems to mangle diffs all the time, irrespective of model.
I think that technical people tend to see their area of expertise the most fundamental one, from which everything else derives.
This guy specialized in security and so he thinks that the concepts that he learned underlying everything, and everything else is just application.
But he's making the same mistake as everyone else. Everybody has gaps in their knowledge, it's just that he chooses to talk down to people who have their in their knowledge in _his_ area of expertise. Physicists do this a lot (I should know: I trained as a physicist so I know a lot of physicists). "Physics is really everything, everything else could be deducted from physics in principle, so no point spending time thinking about it". He carried this attitude into the next area of expertise he learned.
I'm with the project manager. "How does the gorb fleem the leemaflop?" Don't know, don't care, you do your job and I do mine. Time is finite and I'd rather spend my time on things I find intellectually stimulating, not IT security. The irony is, if everybody could reliably answer those questions, he wouldn't have a job. I find the lack of understanding quite disgusting frankly.
I don’t think robots will be replacing a toilet or retrofitting PEX in an old home anytime soon. Though it might be nice for the drywall guys to have robots make the cuts instead of the plumbers.
