1,359 karma · joined May 13, 2016
Systems programming and human advancement.
Right. Let's see Klabnik accept a PR from Curtis Yarvin. The "inclusiveness" of Rust, and projects like it, only applies if you hold the correct opinions.
The definition of "inclusive" as viewed by most of these CoCs is extremely narrow.
Put a parakeet in a windowless room and close the door. I can reasonably make the statement that the parakeet is perching, looking around, and/or preening its feathers, because that's what parakeets do. I wouldn't need direct observational evidence to make this statement.
Panopticon-level spying is what intelligence agencies do. It's what they've striven to do, as much as possible, without getting caught. The Binney and Snowden leaks corroborate this, and there's no reason to believe they've suddenly stopped trying to. OP doesn't need evidence to make the reasonable claim that intelligence agencies spy on us, and likely do it by hoovering up our data for analysis.
c.f. the "Deep State".
True or not, it's a charitable read of OP.
A very human bias is to believe and follow those in positions of authority, despite long and verifiable records of abject failure and incompetence.
Researchers sell bugs all the time. Whether to a bounty program, a broker, a carder forum, etc, it happens all the time.
Nobody is going to look down on her for admitting to doing what some people do for a living.
Would you prefer she works for MSFT for free or "responsibly" works with Zerodium so that the Feds can get their hooves on the bug first?
I rarely see similar articles bemoaning the carbon emissions associated with heating, say, wealthy New England apartments. It's always those damn poor people in the South ruining the environment.
Oftentimes a beard hair will grow into my skin and I will unconsciously pick at non-ingrown hairs in the general region until there is a small hairless hole surrounding the actual ingrown hair.
I have to consciously tell myself to get a needle and fish it out preemptively so that this doesn't happen.
No, there are plenty of people who notice it. We've learned to keep our mouths shut on the topic because the coordinated downvote attacks by FVEY sycophants on this site make attempting discussion pointless.
Find a different site if you want to raise even the merest, slightest questions with CIA talking points.
What about not being a CS major prevents you from picking up Sedgewick or a programming language reference?
It seems to me to be precisely the opposite. It is extremely common to see cyclists have a full 4-5 foot shoulder to ride on, but they always choose to ride as close to vehicular traffic as possible. Sometimes even on the white line. By doing so, they endanger everybody, and the only explanation for this behavior is entitlement.
So, cyclists, please change my mind: when you have a wide shoulder to occupy, and you choose to ride so close to the left of it that your handlebars are in serious danger of being clipped by vehicular traffic, why? Why not the middle of the shoulder, or, god forbid, the right side of it?
edit: thanks for the enlightening replies.
It is an authenticated, nonrepudiable communications platform using identifiers that are very difficult (possible, yes, but most people will get it wrong) to comprehensively anonymize.
The ability to present nonrepudiable communications to a judge is precisely the wet dream of law enforcement officers, ambitious prosecutors, and despotic regimes everywhere. All they need to do is flip the people you're communicating with, and you're done.
Expressing skepticism of their stewardship of a security company is perfectly reasonable.
As others in this thread have pointed out, just bootstrap. It's what we did, and as a consequence we don't answer to any of the rent-seeking parasites of the finance world.
At some point you really do need to give up on your fancy canaries, gateway and host IDS, perimeter blinky boxes, threat intelligence feeds, endpoint protection products, etc, and just start firing those in your employ who willfully and joyously thumb their noses at basic security hygiene.
Specifically, that most stakeholders in a feature or project accept "mostly works, with the exception of rare edge cases" as sufficient cause for launch. This usually takes the form of "get it out the door as-is so we can promote it, and then refactor later".
This is actually somewhat reasonable in terms of balancing business and technical interests, and I can see the case being made for doing it.
The problem, of course, is that "refactor later" never happens because there is always another project or feature demanding to be worked on. These same stakeholders might allow a day or two after launch to refactor, but then promptly decide that starting on Project B takes higher priority than refactoring Project A (which, in their mind, "works").
The above scenario covers at least 95% of our existing technical debt.