I'm familiar with your region. It's currently nighttime in this first-world dystopian country. But hey, there's always something to be grateful for when you're alive. Even if you'd rather paint roses red, you can't change the fact it's still a rose. Can't change the past, only the future. For all that you're powerless to change, you're free to change your perception of it.
@hikerfromva
I'm surviving, thanks for asking.
@nyx
Slightly relevant:::
www.973-eht-namuh-973.com
One more note::: unless it's a sh## creditor/banker, I doubt DB mistakes would slip past unnoticed for long. Customer data is valuable to financial institutions to sell to 3rd parties. On top of that, your debt is their income. Something will not balance somewhere and someone's life will flip over pennies.
@onelson @caranatar
Obviously fake names will appear obvious, but the trick we're discussing here is to fool the human element into believing the fake name to appear as a legitimate mistake.
Assuming such login info is stored in a SQL DB, it would seem more appropriate to snake in an attack using relative approach- rather than an aesthetic that only appears to be a mistake.
Furthermore (correct me if I'm wrong), if we're talking about a BIG DB, it's unlikely that the search queries will go through entry by entry- and we would have to assume their approaches to navigating and querying the DB accordingly.
Considering the DB admin is working for a good/store chain, it's unlikely they get paid well enough to care for diligence. So I'm going to assume at least _a little_ bit of leeway in terms of obviousness in approach.
why not "Drop Table" ??
If you can't find an account you _know_ exists, chances are someone in your timeline blocked them or their server.
@hikerfromva
Home: immediate serve(your home)
Local: servers yours is connected to (your neighborhood)
Global: their connections or choice connections of yours (state-wide)
Fediverse: Universe (all countries, regardless of connection)
@icedquinn
Where does it come out?
Ask me about my keyboard