Joeboy

I think the closest thing to an actual "standard" is AES5-2018, "Recommended practice for professional digital audio".

Abstract:

A sampling frequency of 48 kHz is recommended for the origination, processing, and interchange of audio programs employing pulse-code modulation. Recognition is also given to the use of a 44.1-kHz sampling frequency related to certain consumer digital applications, the use of a 32-kHz sampling frequency for transmission-related applications, and the use of a 96-kHz sampling frequency for applications requiring a higher bandwidth or more relaxed anti-alias filtering. This revision further quantifies the preferred choices for higher sampling frequencies.

Edit: From my personal perspective, 44.1kHz is a legacy minor annoyance

I also have a tendency to say "Last century", thinking it comedically suggests "a long time ago" without it actually being that long ago. But as time goes by it obviously becomes legitimately a long time ago, and I suspect young people wouldn't see the attempted irony at all.

The big IP films got better distribution and marketing, but there hasn't really been a shortage of original films produced over the last decade. The big franchise movies are a small proportion of films produced.

If you're talking about introducing it somewhere where there's currently no social safety net, sure. Where I live if you were to replace the existing safety net with say £1k a month (the level of our state pension, which is widely considered a time bomb of unaffordability), that's like a million instant homeless people.

I suppose it's like a magic trick. It's less impressive once you understand how it all works. But still, it's clearly effective and you can admire the artistry.

Does the public really not know what editing is?

I think most viewers would be unaware of the cut unless it was pointed out. Hence this sequence being called a "shot".

My recollection from this era is there was a common argument that provocation and boundary pushing were the way to ensure an uncensored internet. To me, it seems like that argument has been defeated by reality, but I've never seen much discussion of it. Maybe it's a last-year's-war now anyway.

Not really answering your question, but the Belgian Congo photo is probably more notable and consequential.

https://en.wikipedia.org/wiki/Nsala_of_Wala_in_the_Nsongo_Di...

emails between her and her husband

If we're dropping random trivia it should probably be mentioned that her husband is https://en.wikipedia.org/wiki/Yanis_Varoufakis

Because it's Ubuntu policy to replace some foundational part of the system with some janky unfinished experiment in every release.

I agree with you that that's more the story here than "OMG, somebody wrote Rust code with bugs in it".

Maybe not what they meant, but Rust sometimes makes it tempting to just copy things rather than fighting the borrow checker. Whereas in C++ you're free to just pass pointers around and not worry about it until / unless your code crashes or gets exploited.

Speaking authoritatively from my position as an incompetent C++ / Rust dev.

Don't know if it counts, but my London cinema listings website just uses static json files that I upload every weekend. All of the searching and stuff is done client side. Although I do use sqlite to create the files locally.

Total hosting costs are £0 ($0) other than the domain name.

Also the Acorn Archimedes is, technically, an ARM / RISC desktop.

An opinion about the design of the website.

The most obvious reason for this is browser fingerprinting, right? So your visits to other websites can be linked to your Linkedin identity? Or no?

Maybe "Consider the ant" from The Bible?

Which I only know about from the John Wyndham story[0]

[0] https://en.wikipedia.org/wiki/Consider_Her_Ways

These end a few years before I started getting them. I have a large pile of NMEs and Melody Makers from I guess the late '80s / early '90s if anybody wants to collect them from East London, free to good home :-)

I find it a bit odd how much people talk up the Rust aspect of Tauri. For most cases you'll be writing a Typescript frontend and relying on boilerplate Rust + plugins for the backend. And I'd think most of the target audience would see that as a good thing.

Not related to the tech bits of this, but I finally got around to watching Aftersun a couple of days ago. It's a great, sad film about somebody watching home video from their childhood and reevaluating what was going on.

In the context of the Epstein files, I think Schmidt's actual quote looks pretty good ("If you have something that you don't want anyone to know, maybe you shouldn’t be doing it in the first place").

The problem is that even if Schmidt didn't do anything wrong (I don't know but all the link says is he may have been invited to a dinner but probably didn't attend), he nevertheless had something to fear.

Your comment reminded of the youtuber who changed the shop signs in his video into scary non-English script: https://www.youtube.com/watch?v=UPZxMVpnCBM

Edit: Changed to link I like a bit more

Anything else worth considering other than youtube (or self-hosting if scale isn't an issue)?

Apparently you can turn it on with about:config / dom.webgpu.enabled

But personally, I'm not going to start turning on unsafe things in my browser so I can see the demo. I tried firefox and chromium and neither worked so pfft, whatever.

I'm fairly agnostic to the headline question of whether social media should be banned for under 16s. The part that seems interesting to me is whether this will entail linking online activity to real world identity for the rest of us. It doesn't have to, but in practice I guess that's probably what'll happen. Unfortunately all the debate is "but freedom of speech" vs "but think of the kids" vs, and nobody will be lobbying for a better (or less worse) implementation.

If you read the comments with the other interpretation I think the conversation will make more sense.

I suppose, if you interpret "avoid" as "not care about".

My reading is not that they're saying it's something they necessarily have deal with themselves, but that it's something they can't practically avoid.

Is this not the job of the operating system or its supporting parts, to deal with audio from various sources

I think that's the point? In practice the OS (or its supporting parts) resample audio all the time. It's "under the hood" but the only way to actually avoid it would be to limit all audio files and playback systems to a single rate.

This isn't really a drawback

But, that's only true because people freely resample between them all the time and nobody knows or cares about it.

Unless I'm missing something?

I suppose the option you're missing is you could try to get pristine captures of your samples at every possible sample rate you need / want to support on the host system.