It wouldn’t be a 30% higher electrical bill overall. It would be 30% more for whatever power you’re using for this specific device, which, if it’s ordinarily 10W while in sleep and an average 100W while in use, and you use it 50 hours per week, or 215 hours per month, that’s a baseline power usage of 21500 watt hours in use and 5050 watt hours from idle/sleep/suspend. Or a total of 26550 watt hours, or 26.5 kWh. At 20 cents per kWh, you’re talking about $5.30 per month in electricity for the computer. A 30% increase would be an extra $1.60 per month.

That wasn’t the real Tesla, though. It was actually the Goblin King.

Human life absolutely factors into predicted lawsuit losses. Wrongful death lawsuits are expensive.

Probably where AI learned that sheen from.

Worked for Christopher Nolan, too. Although he did make The Prestige and Inception during his decade making Batman.

In both of those examples, the actors played characters of their own race, pretending to be another race as the plot of the respective movies.

I feel the same way about the first and second Terminators, and the first Rambo and its sequels.

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.

Have you ever had to clean public restrooms? Nothing microscopic about the drops of splashback.

Gotta paint some faces on there, with puckered lips.

You’re paying way too much for antimatter, man. Who’s your antimatter guy?

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 giving 1-star ratings to weather apps because it’s too cold outside.

Oh this line of comments was serious? I thought we were making jokes.

I’m just trying to extrapolate to being supportive of government surveillance, and proving that other commenter right.

If they go and follow 200 users on 20 different instances, then they’ll most likely get followed back by someone on 90% of those instances. It’s not that much effort.

I don’t know, this sounds like an unnatural way to interact with a service. Following 4000 accounts and trying to spread it out evenly between servers sounds like a terrible way to curate one’s own feed and consume content on a service like this. I rarely follow more than 100 on any given service, and think it’s weird when people follow more than 500.

Following back seems like a pretty foreign concept to me on this type of service, and seems to me to be inconsistent with how people actually use Twitter or Bluesky. To me, these hiccups in user experience as either a lurker (can’t find anyone in-band who another person on your instance doesn’t already follow) or publisher (can’t be found easily from anyone off of your server unless you actively go try to spam follows in the hopes that some will follow back) would be a dealbreaker for anything less than the biggest server.