J-Kuhn

Yes, this is one application.

Google "Software Guard Extensions" and "Intel Enclave"

[1]: https://en.wikipedia.org/wiki/Software_Guard_Extensions

Read about Bottom (⊥).

null can be considered bottom (if it were not for primitives)

tl;dr: Forged document claims to be from 2006, uses a font (Calibri) that was introduced 2007. Newsletters headline: "Sans Sharif".

certbot?

You can edit the cron job for certbot and add a script that should be called when certificates were renewed.

John Ousterhout is the inventor of the Tcl language.

The problem with eggdrop is that it does TOO much things.

* Keeping an internal ban list? Check.

* Removing stale bans from the channel? Check.

* Keep the bot opped? Check.

* Has built-in user management? Check.

* Uses telnet or DCC to manage the bot? Check.

All that features have it's use, but most of the time they are not needed. Instead people new to eggdrop have to "fight" with that features.

* User keeps getting banned when he enters the channel, even after an op removed the ban. Channel op has to learn about the internal ban list.

* Eggdrop removes all bans after 180 minutes (default).

Eggdrop admin has to disable that feature or add the user to the internal ban list.

* For non-channel admin bots, the bot does not need to be op.

Eggdrop will complain about it.

* Built-in user management uses part of the hostmask.

You got a new ISP, good luck restoring your access to the bot.

And it doesn't play nice with the accounts from IRC services.

* DCC doesn't work behind if you are behind NAT. And using telnet means using a different program.

In the past, I tried to solve several of that problems with Tcl scripts, with variable success.

* Allow the bot to be managed through commands in IRC.

* Bind to raw events, hide them (return 1) from eggdrop and send a replacement command through an internal API.

I had to use that to make eggdrop aware of the popular +qa modes (channel owner and channel admin)

Or replace the user host so eggdrop sees a fake host with the account name in it. Solves the problem with the user management through hostmasks.

In the end, I gave up. I wrote an IRC Bot in Tcl and re-implemented the Tcl API, so I could use the old eggdrop scripts.

Usually Mail clients send mails as multipart/alternative with both a text/html and text/plain.

It makes sense to keep the entered markdown as the text/plain part. But if this looks ugly, then the plain text view won't be as pleasant.

PS.: I hate all companies that think their newsletter only needs text/html, and put a "Please read me with an HTML-compatible mail client" as text/plain.

This remembers me of the Blub paradox from "Beating the average" [1] from Paul Graham.

Learning new ways how to express things is never bad.

[1]: http://www.paulgraham.com/avg.html

A acquaintance once worked for two different companies for several years as watchman. He was fired on the spot when they found out. How did they notice?

One company bought the other.

Stupid move.

Messages send to telegram with the bot-api can be forwarded to anyone who has the chat_id and the bot token with the forwardMessage method. And the message id is an increasing number starting with 1.

So if they did not already disable (or got telegram to disable) the bot, they can now extract the infection id with the seed key.

tl;dr: All the information required to restore the data is accessible if you have the bot_token and chat_id.