DreamSpinner

Entirely likely, though possibly there are potentially flaws that could allow people to identify it through other means.

I've never used TOR so I didn't realise that this would apply (and it makes perfect sense it would work that way).

It may be that whoever requested the data knows as little about it as I do (or more likely, they know a lot more about what they want and my speculation is completely wrong).

It's interesting, the article discusses that the request is for a relatively short period of time (35 minutes) - however for a popular website that could still be thousands of viewers.

It suggests that there's something they're specifically looking to match against - but if that was the case, I would think that specific IP addresses could be provided in the request - e.g. Did any one of these 10 IP addresses view the article in the time period. Much more specific and likely easier to justify.

I'd rampantly speculate that perhaps that time matches to the link being posted in a pedophilia related forum (with the forum behind TOR) - and the FBI would like to get a list of who might have followed it there.

wormh_o_le mono_c_le

The although both words have the same last two letters - "le", the third last letters are different. This produces a different syllable when pronounced.

This is interesting, particularly in light of skissane comments about melatonin being prescription only.

Here in Australia, you can buy Asthma Inhalers "over the counter" (no prespcription) from pharmacies (Salbutamol). They sometimes do ask if you're seeing a doctor for your asthma, but that's about it. (I take a regular treatment for it)

I think an interesting variation on this is that even if a safety system is not required by law, but is available - then disabling could constitute criminal negligence. Consider what happens if safety equipment on industrial equipment is disabled and injuries result. I'm fairly sure that criminal charges could result for whoever disabled the safety mechanisms (though the there are likely differences between workplace safety criminal law and road safety).

Yes, it was real.

Keep in mind that it was also used as a significant contributing factor to replace a lot of major legacy IT systems (especially accounting systems) at big organisations (a lot of SAP rollouts in the late 90s had Y2K as part of the cost justifications).

The company I worked for ran a Y2K Remediation "Factory" for mainframe software - going through and change to 4 digits, checking for leap year issues, confirming various calculations still worked.

I worked on a full system replacement that was partially justified on the basis of (roughly) we can spend 0.3x and do y2k patches, or spend X and get a new system using more recent technologies and UIs.

There were still problems, but they were generally in less critical systems as likely major systems had been tested, and were remediated or replaced.

Keep in mind that there was often much more processing that occurred on desktop computers (traditional fat client) - so lots of effort was also expended on check desktop date rollover behaviour. Once place I worked at had to manually run test software on every computer they had (10's of thousands) because it needed reboots and remote management was more primitive (and less adopted) at the time.

I also wonder if encouraging this form of meetings could be viewed as discriminatory if you have employees who have physical disabilities that might make walking unpleasant or slow.

The reason that trust is important could be to do with verifying breaches.

In some of his articles discussing various breaches, he mentions reaching out to selected (potential) victims to verify some of the details.

Doing that does require a fair amount of trust by various victims of the people asking to verify.

If I was randomly contacted to verify some details in a breach, I'd be skeptical it was a phishing scheme.

If I was randomly contacted by Troy Hunt / HIBP - then I'd look at it much more seriously.

This makes me think of an interesting point around the potential virus outbreak in the US.

If there is a non-trivial outbreak, then could it effectively be (for the US), not just a mass virus management exercise - but be followed by a mass-bankrupting due to medical expenses (which are already a big deal just for "normal" life events)

Although there are a number of socially related reasons - there are likely some significant immediate commercial reasons to do so.

If you're in a service related industry - do you want staff coming to work if they are (or recently) suffering from digestive illnesses? How would an outbreak of people getting sick after being at your facility look? It could potentially result in very very bad publicity - to the point of destroying your business.

If you're running a smaller business / facility - do you want an employee coming in and spreading the illness to your other workers in the early stages of being sick (and then later taking time off)? This could result in your business lacking sufficient staff to open if you can't use labor hire staff.

The reason why it might be good for businesses to provide an incentive (like sick pay) not to work when sick is that it reduces the risk of negative outcomes to the business.

Quite some time ago, I needed to do a big cleanup of email aliases (I have 500+) and various

My approach was to use IMAP integration with my provider to copy all the emails down to my laptop.

I then used VBA in Outlook to create a list of source email addresses and counts - then I could update places using those emails.

In your case, i'd do something similar.

Analyse your existing emails to get a list of emails by source address (or domain).

Use that list to figure out what places you need to get updated.

Then (per Sydney1's suggestion) - forward old emails to the new address. Preferably tag it somehow so you know that it means there are other places that need to be updated.