robotrobot
Joined 14 years ago
Karma
22
Submissions
20
Member since
Jan 21
Recent submissions
Comment · 1 day ago
I've already something similar - https://city.scaleupcto.com - including datacenters and AI research labs with associated disasters... I have a v2 with multiplayer which I need to finish off, exactly as you describe!
Comment · 1 month ago
Depends on the disaster!
Comment · 1 month ago
The AGI disaster mode is particularly fun. Start a city in 2050 and deploy.
Comment · 11 years ago
Talis, Birmingham, UK.
EdTech 100% employee owned, SaaS software already in use in 50% of UK Universities, plus growing Oz, NZ, Malaysia, China and Norway.
Post-revenue and pre-profit (not for long). Every position comes with equity share via options scheme.
Various roles including dev, microservices architecture Node.JS, Java, AngularJS
Check out our ethos: http://careers.talis.com/
Comment · 12 years ago
Hmm. Another one for your security audit. I was able to change the registered email address on our account
1) Without re-entering my creds following login 2) With no notification to the old email address that this had been done.
Comment · 12 years ago
Thanks (can't reply direct to the reply for some reason)
Comment · 12 years ago
Me again.
"he was only able to reach less than 1% (our estimate is 5,000 users)"
So you have 500k registered customers then? Surely not.
Comment · 12 years ago
OK, I want to make sure though. How can these creds be regenerated? What happens if we had leaked them accidentally, there seems no way to regen them?
Comment · 12 years ago
Another thing to mention here - we've received no direct contact from BS at all following this - if we hadn't been following this on HN (and we were a little naive) we might still not know this email was not genuine. The blog post mortem is great, but I think it's a poor show not to reach out to affected customers directly.
Comment · 12 years ago
Is anyone from BrowserStack monitoring this thread? We received the email so we can assume our account was accessed by the hacker. Passwords crypted and salted (ok - changed) but what about the BrowserStack automate username and token, generated by BS themselves, that we are unable to edit or regen?