They just really wanted to release on 9/9/99 no matter what.

Clearly yes, as this post outlines, these candidates weren’t smart enough to use ChatGPT

This 100%. I hate getting added to a PR for review with testing commits in the history, and I’m expected to clean those up before merging into main.

That’s not an allowlist though, SimpleLogin was on a denylist, possible because of high rates of spam. An allow list would be if they only allowed @gmail.com for example. If you have your own domain and set it up to use Proton Mail, you shouldn’t have any problems.

I’ve never encountered a site which had an allow list of domain names. The hardest thing about self hosting an email server is most home ISPs will block SMTP as it’s a source of spam. Usually this requires business level ISP or an SMTP relay, both which aren’t usually free from what you’re already paying for home internet.

https://www.srenity.online/

I just was reading Wikipedia and it said he was arrested previously for hacking.

In 2015, when he was still a teenager, a Finnish court found Kivimäki guilty of more than 50,000 aggravated computer break-ins. Among other targets, he attacked large educational institutions in the US, hijacking emails, stealing credit card details and blocking site traffic.

Kivimäki received a two year suspended sentence for those charges.

https://yle.fi/a/3-12669196

You’re probably right he had some connection and stumbled onto the data, but this wasn’t his first rodeo.

This. For example, if you have a DNS entry for your DB and the TTL is set to 1 hour, an hour before you intend to make the changes, just lower the TTL of the record to a minute. This allows all clients to be told to only cache for a minute and to do lookups every minute. Then after an hour, make the necessary changes to the record. Within a minute of the changes, the clients should all be using the new record. Once you’ve confirmed that everything is good, you can then raise TTL to 1 hour again.

This approach does require some more planning and two or three updates to DNS, but minimizes downtime. The reason you may need to keep TTL high is if you have thousands of clients and you know the DNS won’t be updated often. Since most providers charge per thousand or million lookups, that adds up quickly when you have thousands of clients who would be doing unnecessary lookups often. Also a larger TTL would minimize the impact of a loss of DNS servers.

??? Is when the underwear gnomes send you a massive bill because you’re paying per 1k lookups. They profit, you don’t

I have a coworker who always forgets TTL is a thing, and never plans ahead. On multiple occasions they’ve moved a database, updated DNS to reflect the change, and are confused why everything is broken for 10-20 minutes.

I really wish the first time they learned, but every once and a while they come to me to troubleshoot the same issue.

What shell is this that it outputs the duration after exiting the loop? Looks nifty.

Are you referring to hashicorp with recently changing license terms? IIRC the change in license was to prevent competitors (i.e. AWS) from releasing a service using the open source software from directly competing with their cloud offerings. It’s sad it had to come to it, but I think the reality of the situation is that AWS could come up with a competing cloud offering, has the built in user base, and can run the service at a loss, because they make money elsewhere.

A company like Amazon totally could afford to pay, but won’t if they don’t have to. Ultimately, I think part of the license change was in response to Amazon and AWS being a monopoly. Without the license change, their company was at risk.

You list great points of information that should be shared to admins of other instances. Thanks for clarifying.

I assumed as much after reading it several times, but just wanted let you know and point out that statement could be misconstrued. Thanks for clarifying!

I hope people share the positive hits of CSAM and see how widespread the problem is…

It sounds like you’re encouraging people to share CSAM images found, which is obviously not the intent of this tool. There’s probably a better way to phrase what you were trying to say.