Sadly, no. I only have 2 digits on my email to form a pattern. As said in the post, the guy whose bank statements I received had 5-6 more characters than my name, and didn't even have a number in it.
I've never had such a problem before. My email is just not simply "darshit", but also has a couple of digits. Among the people whose mail I received, one of the guy's email had 6 characters more than mine, and totally unrelated.
We are on the educated side of the internet populace. I can only imagine worse things when this happens to the non-educated, especially in developing countries like India, where almost everyone has an (mobile) internet connection these days.
It's interesting to think about how the very basis of our internet identities, that is the email, can be so easily abused by someone who has bad intent.
In my undergraduate final year project, we used a "variation" of SSS called Thien-Lin Secret Sharing to enable bank locker security! Glad to see SSS being shared here!
It would possibly work with XLSX or PPTX or any of the newer Office file formats that rely on zipping a folder of XML files. Open Document Format files like those from Libre Office might be capable of this too.
XLS, PPT, DOC or other old style Office files don't follow this format so this specific approach wouldn't work on those.
I recently applied for the Backend engineer role in Sofia, but received a reply that you require trial work with a candidate before hiring and it would be expensive for SumUp to invite applications from abroad. How will someone get a visa unless you hire them? Seems a conundrum, and I'd like to know if it's the same case here
> This is what happened when one bad web server decided it was going to fail all of its requests, and would do so while incurring the absolute minimum amount of load on itself.
Good ELI5 explanation, but it doesn't really explain why the webserver failed the requests as it did. Or maybe I'm missing something?
> it doesn't really explain why the webserver failed the requests as it did. Or maybe I'm missing something?
That the article is about load-balancers and how a single "rogue actor" can have outsized effect on the entire thing. The failing webserver is besides the point.
Take your pick. There's a remarkable number of things that can cause a server to start returning 500s while the rest of the fleet is fine. Doesn't even have to be that specific server's fault (e.g. database behind it could have reached a connection limit handling the connection pools from all the other webservers, leaving this one in the dust. Fun part from this is it can result in the misbehaving server _moving_ as connections close and re-open)
