https://youtu.be/_hBH8Gy9kFE

Fried cheese…with club sauce

Popcorn shrimp…with club sauce

Chicken Tenders…with spicy club saauuce

Spit out a random e-mail address and record which e-mail address was given to each IP.

The author mentions it’s a violation of GDPR to record visitors’ IP addresses. I’m not sure that’s correct, but even so, it could be possible to make a custom encoding of literally every ipv4 address through some kind of lookup table with 256 entries, and just string together 4 of those random words to represent the entire 32-bit address space, such that “correct horse battery staple” corresponds to 192.168.1.100 or whatever.

Base64 encoding of a text representation of an IP address and date seems inefficient.

There are 4 octets in a ipv4 address, where each octet is one of 2^8 possible integers. The entire 32-bit ipv4 address space should therefore be possible to encode in 6 characters in base64.

Similarly, a timestamp with a precision/resolution in seconds can generally be represented by a 32-bit integer, at least up through 2038. So that can be represented by another 6 characters.

Or, if you know you’re always going to be encoding these two numbers together, you can put together a 64-bit number and encode that in base64, in just 11 characters. Maybe even use some kind of custom timestamp format that uses fewer bits and counts from a more recent epoch, as an unsigned integer (since you’re not going to have site visitors from the past), and get that down to even fewer characters.

That seems to run less risk of the email address getting cut off at some arbitrary length as it gets passed around.

The use of a “+” convention is just a convention popularized by Gmail and the other major providers. If you have your own domain, you should be able to do this with any arbitrary text schema, and encode some information in the address itself, especially if you don’t care about sending email from those aliases: set up your email service to have a catchall inbox that can further be filtered/forwarded based on other rules.

It can be cumbersome but I could see it working at getting the information you’re looking for.

Thompson’s Teeth: The only teeth strong enough to eat other teeth!

Dental printers are a pretty standard way to make these things. There’s a whole regulatory process for testing and certifying the printers and their resins for continued contact with gums/skin/teeth for toxicity, infection, irritation, etc.

But there are still significant drawbacks to using dead synthetic stuff as a replacement for living tissue.

Slang term for ejaculating, usually with some projectile distance implied. Very popular term in the mid-2000’s, see Get Low by Lil Jon.

I’m with you.

For meat, I generally prefer dry heat. If we’re doing low and slow, I like slow roasted in the oven, or smoked in an outdoor smoker. If it’s fast heat, like steaks, I prefer it over charcoal. Or burgers on a griddle.

For things where wet cooking works better (steam, poach, braise), a pressure cooker can be a good substitute, but even then I generally prefer the control that comes from being able to add ingredients at different times, open the lid to check on things, adjust temperature or seasonings as necessary, etc.

Basically I very rarely use my pressure cooker. It’s fine for making stocks, and is fine for making beans quickly from dried, but it’s almost never my first choice for any main.

Glad they’re happy but I would be pissed off beyond measure.

Isn’t that the whole point of relationships? For us to understand what we like, what we want, and what we don’t, and find partners who fit those things (while simultaneously fitting their preferences)? And then let people with different preferences and different characteristics find their own matches?

I certainly wouldn’t be this person’s soul mate because like you, I’d be annoyed at the lack of planning and not at all charmed by this particular style of quirkiness. But let other people enjoy the things they enjoy.