Looks like the tide is turning on the use of slop imagery. Comments calling out generated images are getting downvoted here, and over on Mastodon AI images are getting faved/boosted more than previously.

Is the neo-Luddite battle lost? Did convenience win out over environmental concerns?

So I work at DeviantArt, and we actually saw this in real-time. A few years ago, we added external ads all over the place, and had to add a whole framework to detect “ad-unsafe” works that wouldn’t get ads served against them. So we only got ads against a percentage of views, and people were getting pissed at the ads and leaving.

So we tore the ads back out, traffic’s recovered, and a focus on providing actual tools for artists to make money through the site has meant we’re doing better without ads than we were with ads.

So this came up with this user a few days ago, and apparently ð fell out of use later in Old English and its usage was merged into þ for hundreds of years.

I remain unconvinced.

So there are multiple people in this thread who state their job is to unfuck what the LLMs are doing. I have a family member who graduated in CS a year ago and is having a hell of a time finding work, how would he go about getting one of these “clean up after the model” jobs?

My leatherman was a little over a ton That thing must be huge!

That was kind of the author’s point: that HTTP is so broadly specified, and at that point had so many unnecessary RFCs extending it, that you could halfway-sensibly write a hardware control protocol by HTTP alone even if that was a terrible idea.

Source: I wrote the tea-brewing extension to HTCPCP, which takes it another notch into the ridiculous.

I’ve actually written exactly that before, when I needed to check the lowest bit in an SQL dialect with no bitwise operators. It was disgusting and awesome.

For real though, the shortest license is probably the WTFPL:

0. You just DO WHAT THE FUCK YOU WANT TO.

Might’ve used it a couple of times myself.

Essentially. If the end user is being asked to make a financial outlay to get to the same things they did before, it’s unlikely that will go down well.

Excellent. I’m on Stage 4 on the Thursday afternoon: “Brewing Tea Over The Internet”.

Should be fun times, see you there.

I haven’t been exploring in the depths of EFnet in …many years. I’m confined to the programming-related channels I found in the Way Back When, nowadays: at the moment, #c is probably the most active and it’s almost all old-timers.

Did the predilection for tea give me away?

I did go to a conference once where they were handing out laptop stickers, and in the pack was a 418 teapot.

Of course, a week after I stuck that to my machine, it died. Telling the laptop it was a teapot didn’t agree with it, I guess.

For “real” RFCs that aren’t Apr 1st jokes, there’s an independent submissions track for the public to write Internet-Drafts and then submit them into the review process.

With the joke RFCs, they get emailed straight to the editor at least two weeks beforehand. I’m not privy to the selection meeting, but I expect it’s fun.

I never understood the beef people had with that. The Internet is a series of tubes, of various widths and sizes, with inputs at random points in the stream.

Plumbing analogies are apt.

So replicators are kind of a special case: they can make anything already fully prepared, without the need for a brewing command to be sent. It’s possible that by the 24th century, there’s a compatibility layer between Replicator Intermediate Language and HTCPCP, but I’ll leave that to future generations to establish.

Out.

Can’t stand pineapple at the best of times, on pizza is another level of wrong.

The biggest problem IPv6 has is that IPv4 has been so hugely successful: gargantuan resources have been poured into getting the world connected on IPv4, and the routers/etc deployed in the field (especially in sub-Saharan Africa, south Asia, and other places which got the Internet late) are built around version 4: data paths 32 bits wide, ASICs and firmware developed with 4-byte offsets, and so on.

It’s a big effort, and more importantly an expensive effort, to move all that infrastructure over for what the end user perceives as no benefit: their websites load just the same as before.

I quite like the idea of HTTP 256 Binary Data Follows, which is just 200 OK but you asked for a non-text content type file.

I don’t think the extra address space of IPv6 is the problem holding back its adoption, so “IPv4 with another octet” would likely run into the same issues.

Not that it’s a bad idea, it’s just an idea that’s unlikely to catch on.