The app itself remembers what subs to show you

https://github.com/mattdiamond/fuckitjs/blob/master/README.md

Could ask a journalist or lawyer to send it?

It’s definitely possible to have a hardware token which allows confirming the transfer details - https://www.manua.ls/nationwide/card-reader-security-for-internet-banking/manual

https://en.m.wikipedia.org/wiki/Double-entry_bookkeeping f.t.w.

Computer equivalent of vacuum decay in our universe…

Is 🍌 also the safeword, or do I have to remember two words?

Signing the key was certifying that anyone who knows him should trust her - https://en.wikipedia.org/wiki/Web_of_trust

Maybe not relevant to this news about the Ruby on Rails part of the website, but when Frederick did a talk about the map-rendering server, it needed an extremely specific combination of postgres version and options, and kernel version and options, to have a chance at being efficient enough to work, even on the enormous amount of memory available at the time.

TFW “npm install somePackage” adds hundreds of names to your supplier list, some of whom aren’t even adults let alone companies, and the policy says that each new supplier needs to go through a thorough vetting process.

deleted by creator

Do you not have banking licenses (someone mentioned FDIC)? Over here, that’s how you tell real [regulated and insured] banks from pretend banks.

Seen in a code review (paraphrased):

“Why does this break when you add comments in the middle?”

Definitely. Can’t remember if it’s in the base game (update: no, it’s a mod) but it works like cotton and tobacco.

Apparently they didn’t include the single quote at the beginning because they wanted to hint at the exploit without actually triggering it.

(and Lemmy seems to combine two dashes into one)

With an address in 's-Hertogenbosch to help people who are lazy about escaping.

Just noticed that the listing for ; DROP TABLE “COMPANIES”; – LTD has been redacted by the government website‽

Reminds of this bucket-line system

Seems excessive to convert everything to rust when you can use std::shared_ptr and std::weak_ptr to eliminate the memory safety issue?