HN user

k4ch0w

703 karma
Posts14
Comments186
View on HN

I don’t think this is true. This is a lagging indicator and takes time to show the meaningful data. You’ll not get your productivity gains as your top talent leaves and everyone else who is salty will coast doing the bare minimum while looking for a new job. https://youtu.be/4ec_yZCWOCY?si=RQs2bo3w_ATv9X6e

I think companies that won’t adapt and embrace remote/hybrid will slowly decay.

I think this is absolutely one of the reasons. Addresses are very hard to remember in ipv6. You usually just have to remember the first 3 parts of ipv4 and then change the last digit based on the host you want. IPv6 I know it has shorthand but still it doesn’t register in my brain the same way.

You shared it with the employer HR, not the interviewer. Say you're an attractive person and someone now becomes obsessed with you and has your address to stalk you. That's more what I was thinking about

So, it seems a little strange now but when everything was a MS Word Document you had problems with the format. It would look amazing on your machine but if someone else opened it in a version higher or lower than yours or on a different machine things could look really funky and bad.

Thus, PDF was a game changer. Basically, no matter what machine you opened the file on it would look exactly the same. It kinda sucks you can't edit it or have to use special tools to parse it but when it comes to readability across devices it cant be beat.

You know, I think if you look in the home automation space you'll see a lot of interesting protocols in the works. Zigbee, Z-Wave, Thread, and Matter. I think people are working on this problem for the IOT space. Bluetooth is really a strong easy to support protocol and BLE is also an amazing feat when it comes to battery life. Terribly boring to reverse engineer though. I think you also see it more because phones support it by default.

I think a lot of the time it can be devices that implement the protocols poorly because I share your pain with my airpods max. However, I have a pair of a bluetooth headphones that have been amazing for 5 years.

I do want to say there are legitimate reasons to have your users have a forced reset. For example, you’re upgrading your encryption, you migrated to a new IAM system, you’re handling of UTF8 could have been wrong or your meeting a new compliance standard that requires stricter passwords. I don’t know what happened with GitLab, but a telltale sign it’s bad is if they do it for you and not on your next login.

I don't see any mention of regulations coming down on Facebook for the bear case. Same goes for Google. US law will regulate them after following EU's. I think it's very likely once we get more tech literate politicians in place

Your entire service is based on the security of your product. You owe everyone more of an explanation. The Lapsus telegram clearly shows they are using an internal Okta Admin tool to reset/disable passwords and 2FA. I'm more inclined to believe the evidence in front of my eyes than your statement.

It's clear some service team at Microsoft used Okta to SSO, or a contractor that did that's why they only got 37GB of code and Bing/Cortona not Windows OS or internal tools.

The group probably enumerated as much access from Okta as possible and when they had every juicy target decided to release it all for the lols. They probably have more in the works too.

I'd suggest everyone today revoke any Okta SSO sessions for your apps and force a new session as a precautionary measure.