The flaw in your scheme lies in the fact that "it's simple enough to remember" ... this would imply that if one were to target you they could likely correlate your credentials across multiple leaked PW databases and guess at your scheme. That of coarse has plenty of assumptions...
Yes, a motivated attacker could figure it out. But before they could do so, they would need my password in plaintext for multiple unrelated accounts of mine, which is hard, requires the attacker to target me specifically, and by that point what is lastpass really going to do for me anyway?
By far the most likely way my gmail account would be hacked is that foo.com's database is leaked/cracked, and the hackers spam the credentials for foo.com at hundreds of other sites and see what sticks. My scheme defeats that. And it's one point of failure versus several.
Depends how simple. Obviously "add the domain name to the end of the password" is too simple. But there are other ideas that are equally easy to remember or regenerate.
Much better for newer features... for async/await dotpeek would show state machine ( which was actually cool to see), but JustDecompile would actually show me async await in decompiled code.
ALSO, coolest feature is decompile to csproj ... very nice ;)
I had the opposite experience. DotPeek created much better code. using statements were decompiled as usings, JustDecompile produced try/finally blocks.
I am rather sure that having so many phones exclusive to ATT is not helping their cause. I would call that sandbagging the numbers to have 1 phone (928), 2 "Nokia Generations" of releases behind on the largest (BY FAR) smartphone provider in the USA (Verizon). Lumia 929 has been FCC approved since November, WHERE IS IT? The holy grail 1020 still exclusive to ATT, if the numbers are so disappointing put a CDMA radio in it and SELL IT!
