HN user

yaleman

275 karma

website: https://yaleman.org website: https://terminaloutcomes.com github: yaleman twitter: yaleman4331258

Posts1
Comments70
View on HN

There's a lot more checks and balances built into rust as a language, so the foot-gun opportunities are less likely - which makes it rather suitable for reliable systems programming.

And getting back to this particular case... kanidm is fast AND reliable. There's a lot of testing going on comparing it to 389 DS.

2FA on SaaS applications is free and easy, while centralising authentication is much harder - you need to manage an authentication platform instead of just using the application's own authentication.

Taken by itself the suggestion is odd, but in concert with the next entry "use password management software" it makes for a low-cost, zero management, higher security stance than not suggesting 2FA by itself. Noone should ever ignore the option to turn on 2FA.

I really wonder if the missionaries hadn't "worked out" they were religious, or if they were misrepresenting it to HQ in order to work their way into the local groups?

If you fight against the tattoos, you lose out. If you accept the tattoos, then you can make friends and still sell religion - which clearly worked in the end :)

I'd say so. If you aren't assigning your teams time to review the mistakes of the past and actually fixing them, then you're not employing a strategy for success.

Only the biggest companies can really afford to have the scale and skill available from the vast range of people working for bug bounty money - and as one of the other posters mentioned - you still have to have internal staff to confirm and patch the bugs. It's almost like the best side of outsourcing, where the outsourced talent is driven to do their best work because otherwise they'll never get paid.

Then again, I can imagine some teams would get utterly spammed with inane, wrong or non-bounty-able reports, which could be an issue.

This is clearly a redesign done by someone who doesn't use GitHub, and doesn't look at anything but the main screen or why it is the way it is - especially when you start digging into the rest of the UI.

The tabs they want to take away from the "code" screen have little or nothing to do with the other main tabs, that's why they're not cluttering up the main nav bar (which doesn't fit into the author's screenshots.

No one cares about the description of the repo if they're trying to interact with the wiki or the issues modes, that's why it's in the code/main section.

Linus' post reminds me of the Slashdot thread where people were saying the iPod would never catch on.

Saying there's no ARM "at home" is closed-minded to say the least - it's already here - clusters of ARM boards are everywhere, laptops are rapidly gaining ground and I'm currently buying the parts for my first desktop-class ARM machine.

HTTP/3 explained 7 years ago

It's all well and good to opine for the days of old, but when you consider the real-world implications that led to the removal of Flash/Java from the ecosystem, I'd gladly give up the opportunity to experience your art installation without a clickthrough to keep our systems secure.