mattbis

plus one when in programming mode; i have playlists on YT; but this helps to focus... and mostly I find HN has very interesting things that spawn a ton of thoughts...

people like us don't have that much time...

Still can't really forgive any of them for essentially stealing most of this knowledge regardless...

Stop playing games ;

Can't see how an independent developer would ever be able to do this. We need more independent things not less... this would be my concern.

Better legislation would be to force developers to at least allow people to run their own servers.

This and just use it instead of a .pdf.. stay libre make it work for all platforms of all ages and all over the world...

no rtf nothing needs to be fancy

a canonical .txt resource, is parseable and universal. Don't restrict your audience. For example:

If a repo has a .txt backup of some changelog it's therefore not tied to whatever platform.. The repo is a living project and memory.. don't assume anything: ( ie if for some reason your a/c is gone... that information is not lost its saved forever... )

usually if I must reference a pdf it means a browser.. And often I don't want a browser running..

That's why keepass is really useful since you aren't ever typing in the password.. its generated and then copied to the clipboard.. That clipboard is then wiped after X seconds.

So then you know that you have been rooted => If that fails to resolve it.

Reduce the number of vectors to know what you have to change asap. in this scenario you don't want to be guessing about how they did it.

The randomised gibberish just means you can rule out certain things. I can agree on part of what your saying but a string high entropy password, makes it harder to brute..

Many services don't really do that whole retries thing properly. So make it take as long as possible.

If you don't use a random gibberish your password can be cracked on any consumer device in a surprisingly short amount of time...

This way you can then focus on that a session token is probably how they got in.. It's the most common vector these days...

Honeypot sure I didn't think of that.. But I was under the impression the FBI confirmed it ? So we can rule it out.

Making the password impossible to guess - how could that not be?

Since then you know you have a breach, as its randomised gibberish, if you then get the 2nd device asking " is this you trying to login " you can definitely know you are compromised....

I can't see your logic here, that isn't " theatre " ????

If you think that is theatre what is better then? Words and numbers.. easily brute forced.. Sorry can't agree.

You are probably right... I tend to change my password semi often. It's always a super complex impossible to remember string - and always keep an eye on the account activity.

Not to mention ; you would assume he should have more than one device linked to the account and then that adds another layer, since Google will ask you " is this you trying to logon ". <-- that is the only way to get Google to do the unrecognized flow you mention.

If you are suggesting it was exposed and he didn't immediately randomise all his passwords.. WORDS FAIL ME

It's all security 101 the irony is immense...

if the US government / FBI need someone to give some talks on how to do security ...

I really want to know how they did it.. was it some terrible password?

He doesn't strike me as the kinda person even using a local password manager; like keepass.

Somebody needs to find this out.

I doubt it was gmail support... surely it could not be via his phone sim, and if he didn't have two factor on; That would be so funny.

I'm tempted to check out the dark web or the telegram, but i'd rather not do either of those things.