yaleman

The local emergency services uses it as a duplicate method because it's mostly more reliable than any service they can afford to offer... and historically a lot of people were using the site, so sharing helps get things noticed.

Seems like curious timing that this also happened? https://www.sparkfun.com/official-response

The fact that tensorflow takes up 12.9TiB is truly horrifying, and most of that because they use pypi's storage as a dumping ground for their pre-release packages. What a nightmare they've put on other people's shoulders.

It does, works great. Not sure about vaultwarden's support for it though.

Run your own Kanidm instance for free ^_^

It's literally a big red X on the OSS version, so no, it's not "in the base pricing".

I think you'll find that's google's services, not Apple's....

OIDC support's been merged, which would likely help with that?

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.

Yes, it's a replacement for both - still in (a rapidly developing) Alpha stage currently.

So far LDAP and PAM/NSS modules are fully operational, and OAuth's being tested.

Authentication is part of the "accounts" part. :)

The front page says "the research and education system for IAM" ... that reads like it's not for production use and would turn me off immediately.

Turns out, even before you click on "OK" to start watching, it's doing it in the background - my watch history is now full of hours of this junk :(

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.

If you require PCI DSS I hope you're not just blindly following some random post on hackernews for your policy ;)

6'9" guy checking in, thankfully just a tourist to the town for a week - it was always leg day when I was on the tube.

They removed the man pages a while back and broke so many links. It just seems punitive and petty.

Most external USB enclosures I've used run hot, die early and are dog slow...

It's the same as the Helios in OP's article, seems to be a Kickstarter doing limited runs.

> No one on our team is an Erlang expert

... and neither did we.

Hipster ipsum (https://hipsum.co/) is (good|bad) if you want text :)

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 :)

An IPFS node would help significantly more people with a much lower overhead, however. :)

Working in secops, we aren't always the ones building the tools, and the products we're required to support never come with this kind of documentation.

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.

Definitely backed up by the tiny text on OP's page:

"We have already dropped maintenance."

... so, don't use this one?