@matigo Never. I've had 1Password since forever. And I did check for dupes.
@phoneboy The bigger question, of course, is what to do about old and "weak" passwords. There are definitely no dupes in my entire vault, but there are plenty of old ones that could perhaps be longer. Fixing them one at a time is a royal pain though. I'm inclined to do nothing.
@phoneboy Right! No pwnage detected. No dupes in 1password. I'm going to guess brute force, as it wasn't very long.
This is worrying. I received a message from Fastmail saying I had reached my sending limit for the day. Impossible. I raised a ticket and 8.5 hours later got confirmation my account had been compromised. I'll say this for Fastmail; the recovery process is superb. The worrying part is that I know I did not reply to any phishing expedition. So how did it happen? Brute force, maybe. Pwned, maybe.
@konrad I disagree. Link rot is the responsibility of the creator of the link. You may try, if the link matters to you, to have it saved, for example in the Wayback Machine, but ultimately, it is not your responsibility.
It is actually quite easy to ensure that any page you link to is automatically added to the Wayback Machine when you link to it. If you really care, you should be doing that. And supporting the Internet Archive.
// @matigo
@matigo You are overthinking it. The displaying source is displaying what it was sent. If the sender shuts down, that's not really your problem. Presumably the link to the origin of the comment would break, but so what?
@matigo Those are surely not the problems of the receiver. Disappearing gives a 404, and changing its name could give a 301, both of which can be coped with.
@matigo My reading of this part of the spec [indieweb.org] suggests that it depends on you receiving an updated webmention with same source and target. It tells you how to treat that information.
In other words, if you are storing data, you shouldn't need to worry about how far back the original is, because the original should send the fresh webmention if anything changes.
@matigo Let me have a poke around. I think you are correct that m.b looks at your recent feed items for changes, but does not go all the way back in time.
@matigo Yes, it should. There is an updated or edited aspect to webmentions that the receiver is supposed to implement. There may be time limits imposed. M.b will revise a post that it has pulled in, I believe, if you edit it at source.