News for hackers. Stuff that matters.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by matai_kolila on Thursday October 13, 2022 @05:03PM (#33196462)
> Note: the invite input box actually autocompletes ALL github usernames.

I'm sorry, but that's wild. That's like, not even an easy engineering problem to solve necessarily, given their size!

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by gw99 on Thursday October 13, 2022 @05:16PM (#33196596)
Not really. They only have 83-90 million users. That's not really a big table, at least in my world...
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by matai_kolila on Thursday October 13, 2022 @06:05PM (#33197060)
In my world 20 is a lot because finding customers is hard... :(
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by count on Thursday October 13, 2022 @09:46PM (#33198725)
It blew my mind after upgrading to enterprise that was still how it worked.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by kuschku on Friday October 14, 2022 @05:01AM (#33201215)
Sorry, but string prefix search over a few hundred million entries is something you can do with the same performance using just postgres on a single server with just a few hours of dev time.

I've done it before, it's not as impressive as it seems.

With trigrams you can even do precise substring search on this scale with good performance.

If you'd like, I can build a small demo.

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by matai_kolila on Friday October 14, 2022 @02:46PM (#33207343)
Lol no thanks, once you hit the server I’m good, it’s more about the UI for me.