Seems like a weekend hack to set up a fediverse-backed categorized market that, when you want to buy something- forwards to a “buy our download” link of the seller’s choice. Rabid moralists would have to challenge each producer/indie developer individually to take things down.

The real crux is to build a nice user interface on top of it so people would actually use it.

On server:

git init --bare ~/projects/project.git

On client:

git clone username@server:projects/project.git

One clip on Instagram, which has been viewed over 21.5 million times, shows a man ordering “a large Mountain Dew” and the AI voice continually replying “and what will you drink with that?”.

“Dude, Where’s my car” turning into prophecy wasn’t in my bingo card:

https://youtu.be/iuDML4ADIvk

Are you using x11 or Wayland? Is anyone running Wayland with NVIDIA drivers? Everything works well in x11, but I’m getting bad flicker in Wayland. When trying to track it down I was led down a rabbit hole suggesting there is some protocol mismatch between what the NVIDIA drivers implement and what Wayland expects.

An excellent opportunity to reference a bit of true Internet culture: Old Man Murray’s dressdown of one of the puzzles in Gabriel Knight 3. The most relevant part is their final summary:

https://www.oldmanmurray.com/features/79.html

Edit: oh, I find out now that this puzzle even has its own Wikipedia page! https://en.m.wikipedia.org/wiki/Cat_hair_mustache_puzzle

MasterCard’s and Valve’s statements seems to point at Stripe and PayPal as the ones who folded to the pressure. These payment processors then cited MasterCard’s rules to back up their change in policy.

MasterCard now clarifying that the payment processors are over-interpreting the rules and anything legal is ok seems a very good thing here. Valve should be able to go back to Stripe and PayPal with this and say: “Hey, you’ve misunderstood the rules you are quoting; MasterCard themselves say anything legal is ok, and that is the exact policy we’ve been using!”

I discovered that recent versions of the built-in photo apps on Android flat out refuses to do this. The UI for removing location info is there, but it is intentionally blocked if the exif info was added automatically by GPS (i.e., it only works if you manually have set a location). It seems so weird, and outright evil, to block one of the key ways for people to stay safe.

The only reason this is “click bait” is because someone chose to do this, rather than their own mental instability bringing this out organically.

This is my point. The case we are discussing now isn’t noteworthy, because someone doing it deliberately is equally “impressive” as writing out a disturbing sentence in MS Paint. One cannot create a useful “answer engine” without it being capable of producing something that looks weird/provoking/offensive when taken out of context; no more than one can create a useful drawing program that blocks out all offensive content. Nor is it a worthwhile goal.

The cases to care about are those where the LLM takes a perfectly reasonable conversation off the rails. Clickbait like the one in the OP is actually harmful in that they drown out such real cases, and is therefore deserving of ridicule.

Does the marketing matter when the reason for the offending output is that the user spent significant deliberate effort in coaxing the LLM to output what it did? It still seems like MS Paint with extra steps to me.

I get not wanting LLMs to unprompted output “offensive content”. Just like it would be noteworthy if “Clear canvas” in MS Paint sometimes yielded a violent bloody photograph. But, that isn’t what is going on in OPs clickbait.

And, the thing is, LLMs are quite well protected. Look what I coaxed MS Paint to say with almost no effort! Don’t get me started on plain pen and paper! Which we put in the hands of TODDLERS!

No shade on people trying to make sustainable choices, but if the solution to the climate crisis is us trusting everyone to “get with the program” and pick the right choice; while unsustainable alternatives sit right there beside them at lower prices, then we are truly doomed.

What the companies behind these foods and products don’t want to talk about is that to get anywhere we have to target them. It shouldn’t be a controversial standpoint that: (i) all products need to cover their true full environmental and sustainability costs, with the money going back into investments into the environment counteracting the negative impacts; (ii) we need to regulate, regulate, and regulate how companies are allowed to interact with the environment and society, and these limits must apply world-wide. There needs to be careful follow-up on that these rules are followed: with consequences for individuals that take the decisions to break them AND “death sentences” (i.e. complete disbandment) for whole companies that repeatedly oversteps.

After having a lot of sysvinit experience, the transition to setting up my own systemd services has been brutal. What finally clicked for me was that I had this habit of building mini-services based on shellscripts; and systemd goes out of its way to deliberately break those: it wants a single stable process to monitor; and if it sniffs out that you are doing some sketchy things that forks in ways it disapproves of, it is going to shut the whole thing down.

I very much understand wanting to have a say against our data being freely harvested for AI training. But this article’s call for a general opt-out of interacting with AI seems a bit regressive. Many aspects of this and other discussions about the “AI revolution” remind me about the Mitchell and Web skit on the start of the bronze age: https://youtu.be/nyu4u3VZYaQ

These two are not interchangeable or really even comparable though?

For GNU Make, yes they are. These are fully comparable tools for writing sophisticated dynamic build systems. “Plain make”, not so much.

[cmake] makes your build system much, much more robust, far easier to maintain, much more likely to work on other systems than your own, and far easier to integrate with other dependent projects.

This is absolutely incorrect. I assume (although I have never witnessed it) that a true master of cmake could use it to create a robust, maintainable, transferable build system. Very much like there are people who are able to make delicate ice sculptures using a chainsaw. But in no way does these properties follow from the choice of cmake as a build system (as insinuated in your post), rather, the word we are looking for here is: despite using cmake.

I apologize for my inflammatory language. I may just have a bit of PTSD from having to build a lot of other people’s software through multiple layers of meta build systems. And cmake comes back, time and time again, as introducing loads of obstacles.

Cmake

On the topic of things to never forgive Redhat about, aren’t there other things that are more pressing? Like, inventing a whole scheme to circumvent the idea of the GPL license via service contract blackmail?

I couldn’t agree more. If there only was a somewhat user-friendly setting that allowed the oom killer to be far more aggressive, killing or freezing processes as soon as their memory use starts to affect system responsiveness, and just tell me this is what has happened.

That’s On Me, I Set the Bar Too Low