Jesus quite literally loved prostitutes. It’s in the gospel.

Alaska was settled by Russian colonists in the 1800s but the colony didn’t do so well. The Russian emperor at the time decided to sell the territory to the US hoping to weaken the British Empire by preventing them from taking over the territory in the future (ie. to avoid it becoming part of Canada). The Russian emperor had hoped the entire West coast of North America would be US territory eventually but that never happened.

After all the gold was taken from it, Alaska’s benefit to the US is now extending its reach into Arctic waters which are being eyed as a potential international shipping route since climate change means ice breakers might not be needed to escort other ships through the Arctic. The US (via Alaska), Canada, Russia, Denmark (via Greenland), Iceland, Finland, Sweden, and Norway are all currently arguing over which parts of the Arctic ocean belong to them. They’re hoping to ensure any cargo ships that pass through will have to pay them a fee similar to how Panama and Egypt charge for the Panama and Suez canals respectively.

They could also avoid the Canadian fees by using ships but the US has the Jones Act which increases the cost of contiguous States shipping to non-contiguous States like Alaska. So their own government has already messed with Alaska which is why they truck shipments through Canada in the first place.

The cup is using Japanese letters that look somewhat like English letters to spell “Soul of Coffee”. The comment is how those letters are read in Japanese.

Here’s a excerpt from man chmod that can be summarized as “You probably want to mark the file you downloaded as executable. Run chmod +x FILENAME”

DESCRIPTION
This manual page documents the GNU version of chmod. chmod changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.

The format of a symbolic mode is [ugoa…][[-+=][perms…]…], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo. Multiple symbolic modes can be given, separated by commas.

A combination of the letters ugoa controls which users’ access to the file will be changed: the user who owns it (u), other users in the file’s group (g), other users not in the file’s group (o), or all users (a). If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.

The operator + causes the selected file mode bits to be added to the existing file mode bits of each file; - causes them to be removed; and = causes them to be added and causes unmentioned bits to be removed except that a directory’s unmentioned set user and group ID bits are not affected.

The letters rwxXst select file mode bits for the affected users: read ®, write (w), execute (or search for directories) (x), execute/search only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), restricted deletion flag or sticky bit (t). Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file’s group (g), and the permissions granted to users that are in neither of the two preceding categories (o).

A numeric mode is from one to four octal digits (0-7), derived by adding up the bits with values 4, 2, and 1. Omitted digits are assumed to be leading zeros. The first digit selects the set user ID (4) and set group ID (2) and restricted deletion or sticky (1) attributes. The second digit selects permissions for the user who owns the file: read (4), write (2), and execute (1); the third selects permissions for other users in the file’s group, with the same values; and the fourth for other users not in the file’s group, with the same values.

chmod doesn’t change the permissions of symbolic links; the chmod system call cannot change their permissions on most systems, and most systems ignore permissions of symbolic links. However, for each symbolic link listed on the command line, chmod changes the permissions of the pointed-to file. In contrast, chmod ignores symbolic links encountered during recursive directory traversals. Options that modify this behavior are described in the OPTIONS section.