Or is it saying that `base64 /path/to/input-file | base64 --decode` can bypass read file permission flags?
3,012 karma · joined March 24, 2016
Or is it saying that `base64 /path/to/input-file | base64 --decode` can bypass read file permission flags?
2. I actually prefer when HN links to articles rather than videos. I kind of expect interesting reads, not watches when I open this forum.
The article quantifies the amount of rulebreaking. The article actually compares rule breaking across participants and notes that those who were better at obeying the instructions of the experiment are the ones who refused to continue till the end.
The article doesn't invalidate the milgrim experiments. It claims that the interpretation from traditional literature is possibly wrong.
It’s a solid os, and I’m enjoying it, and I love that I can’t break things while tweaking. But the docs are and discussion threads are not written for beginners (it’s really hard to write for beginners).
Within science, participants have always published descriptions of methodology and results for review and replication. Within the same science, participants have never made access to laboratories free for everyone. You get blueprints for how to build a lab and what to do in it, you don't get the building.
Same for computation. I'm fairly sure almost all (if not all) algorithms in these suites are documented somewhere and you can implement them if you want. No one is restricting you from the knowledge. You just don't get the implementation for free.
Macros (in general) are way spookier than a defer statement.
I would not introduce zig’s errdeferr though. That one would need additional semantics changes in C to express errors.
And the problem is a notepad app is expected to be dead simple, have few features, and be hard to get wrong while implementing.
Can we please get a law where kids won’t just take their parents’ IDs and upload them to random places?
I think we understand that UX problem much better now than developers did back in the 70s. In general, not just for ss/lsof
It’s hard for personal communications. The server shouldn’t know the keys, and they need to survive for decades.
I have lost chat histories more times than I can remember, and I have to be extra diligent about this these days.
I don’t even want to think about pgp when I have to manually take care of this problem. Not because of my own skills, but because I could never make it reliable for my family and friends on their side.
In principle, what’s stopping the technique from targeting macos CI runners which improperly store keys used for Notorization signing? Or… is it impossible to automate a publishing step for macos? Does that always require a human to do a manual thing from their account to get a project published?