Mark Tomczak @mtomczak@qoto.org

@AAKL@noc.social @howelloneill I think back then, people understood that freedom of speech wasn't even a factor. There's no free-speech justification for showing up in someone else's forum and taking a dump on the floor---their house their rules.

@ernie And importantly: it's not going to be a path to success for most movies. Most aren't working from that depth of nostalgia, or that much of a tabula rasa of character development.

@mattblaze People sure do take social media seriously sometimes.

@aes @joeyh Yeah. I have FSF bucketed in my brain as "that org that used to be relevant and did good work back in the day, but missed the pivot from 'software as technical practice' to 'software as community undertaking' and they became irrelevant in the era of SaaS and GutHub."

@Hemera Wait, is '=<' actually an operator in Rust?

@bynkii The only solution is to run your own node. Then it can be controlled by an autocracy of one. ;)

@rauschma I did development in opengl for a game engine back in the late aughts. I'm really excited to see the industry start to converge around a thin shell atop the hardware abstraction; it creates a higher barrier to entry for touching the metal, but I think overall it's far preferable to trusting every company that offers a graphics card to successfully implement a thick API based on what I saw back in the day.

@ernie Wow, ChatGPT is legit pretty good at this.

---

Hi ChatGPT! I'm making a commercial for a law firm specializing in suing insurance companies. Can you write the copy for that commercial for me?
>---<
ChatGPT
Certainly! Here's a draft of a commercial script for a law firm that specializes in suing insurance companies:

Opening shot of a person staring at a stack of insurance documents.

Voiceover: "Insurance companies promise to be there for you when things go wrong."

Cut to a scene of a person in a car accident.

Voiceover: "But what happens when they refuse to pay what you're owed?"

Cut to a shot of a person on the phone with an insurance company.

Voiceover: "If you're tired of dealing with insurance companies that don't have your best interests at heart, we can help."

Cut to a shot of a law office with a sign that reads "Insurance Litigation Experts."

Voiceover: "At [Law Firm Name], we specialize in holding insurance companies accountable for their actions."

Cut to a shot of a lawyer in a courtroom.

Voiceover: "Our experienced team of attorneys knows how to navigate the legal system to get you the compensation you deserve."

Cut to a shot of a satisfied client shaking hands with a lawyer.

Voiceover: "Don't let insurance companies take advantage of you. Contact [Law Firm Name] today."

Closing shot of the law office sign.

Voiceover: "[Law Firm Name]. We fight for you."

Of course, you may want to adjust the script to fit the specific tone and messaging of your law firm. But I hope this helps give you a starting point!

@jsatk @gruber One thing I'll be interested to see is how much Mastodon admins are driven by maximal connectivity.

Twitter, Bluesky, &c are driven by maximum user uptake and connectivity metrics (and with money in play, that's what they chase). It creates incentives to keep troublemakers if they don't make *enough* trouble.

If most Mastodon node admins aren't driven by a maximization mindset, blocks, bans, and defederation will flow a lot more freely and it'll end up being a more fragmented network than a Bluesky.

(Now, whether that's a bad thing is left as an exercise for the reader).

@lauren That got mentioned in the TRON documentary I watched yesterday. Bridges channeled a lot of his CLU character for Starman.

@gruber It's a feature, not a bug. ;)

(... but yeah, the expected result is that the network will probably pull against itself over time and fragment into pieces that are "closer" to each other and pieces that are "further."

Like all human communities.)

@jgoerzen @rothomp3 I'm glad both ecosystems are out there. Because sometimes I want to write whatever with whatever and sometimes I want to use a toolchain and kit that has been tested end-to-end.

@lauren First printer in the household was an Okidata dot-matrix.

We had a strict family rule: "No printing before 7AM. If it's important, do it night before."

@lindsay I mean, if it is... Thank you!

Watched a neat documentary on the making of #TRON.

There are "glitch" effects where everything is lighter for a quarter second. Those weren't intentional. The movie used literally tons of film from Kodak to shoot it, and they didn't realize until halfway through production that they hadn't controlled process to keep the film the same order it had come off the truck. If you keep it in order, small manufacturing fluctuations end up continuous through your shots and the human eye doesn't really notice; if you jumble raw film canisters, the difference can be up to half an f-stop and it's very noticeable.

But since the entire film was ultimately animated at the end, they solved the problem by animating in a little sprite or circuit surge or something every time the film quality jumped and several brighter frames spun through.

Fixed it in post. ❤

@bhollis I'm going to have to bring myself up to speed on this feature. Our CI is in a bit of a state right now, but if I can learn how to set up a distributed build cache I'll look into donating time to the build team to make it happen.

@GlowingLantern@mastodon.online @shibayashi Ideally, I'd like it to work that way.

My conern is cert orgs will have incentive to lean on C++'s mere age as proof that it's reliable, leaving a language like #Rust to fight an uphill battle like "We understand that if you do XYZ, you can panic the Rust compiler. It's really hard to crash a C++ compiler. Can we prove that a compiler that panics can create safe code / the language it compiles is sound if it can crash its own compiler?"

... completely ignoring that C++ might just generate undefined behavior instead of crashing.

A lot would come down to getting the rules by which a standards committee operates to be sane.

@GlowingLantern@mastodon.online @shibayashi

I like this idea but I'm always torn on this idea, because I don't know, if such regulation already existed, that #Rust could ever get off the ground in a world where C and C++ already exist.

Those languages are already certified (where such certification exists) for safety-critical and performance-critical applications, and how can places justify the cost to certify yet another language if they already have one? In some ways, the lack of regulation leaves room for better to come along.

@codinghorror @gruber I don't understand because you've just named two of the best things. ;)

Seriously, I don't know if this is an our-codebase problem or a general C++ problem, but I generally use three configs: debug symbols, production-optimized, and address sanitizer.

We use Bazel as our build management system, and changing configs is a "go get coffee" change. Ten to twenty minute recompiles.