ReactiveJelly

They should patch that Global Device ID thing

:^)

You have coworkers who know what a test is? Hire me! ;)

"Nature cannot be fooled"

I asked it to remove "honest" from a draft once.

"Why say honest? We're talking to our coworkers. We would always be honest."

I'm going to look for prompts or skills that can train it in technical writing but I'm warning the AI enthusiasts in my company that its first drafts of code and prose are low-quality, you have to hold it to a high standard yourself.

I actually took a single technical writing class in college so I might be the only one who remembers "Omit needless words."

I'll try it next time I've got Greece vacation money

The king profits from the field

For the solution, read Henry George!

Yeah I've noticed this when role-playing with some LLMs

The regular table saw is still in the new workshop, and the new workshop adds a SawStop and another regular table saw.

I think Chromium already does sandbox ffmpeg in the renderer process because of their "Rule of Two": https://chromium.googlesource.com/chromium/src/+/HEAD/docs/s...

Thus:

1. Code which processes untrusted input

2. Code written in unsafe languages like C or C++

3. Code that runs without a sandbox

So ffmpeg should be sandboxed, same as the network code and GPU process are sandboxed.

I bought one because I had a feeling that the price of used EVs was about to shoot up

I swear John Carmack said somewhere "Time should be a double that starts from 1 billion" or something, for games or VR or something.

Of course when I search on DDG I only get "wow the fast inverse square root"

Then the repugnant conclusion is not that gaming is dead, but that games are made primarily for teenaged boys and most of us have aged out of the target audience, so games simply aren't made for us anymore.

Oh like in path tracing.

It might enable security but I wouldn't say it _ensures_ it.

It just means that visible or IR light (What are they using?) won't leak through walls the way Wi-Fi does. Depending on how wide the beam is and exactly how it all works, it _might_ still leak out of windows and under doors. But it's not like someone casually wardriving outside your house will get as much as they would from Wi-Fi, I would think.

I agree, seitan is a lot more like meat. I prefer less-realistic replacements so even though I've enjoyed seitan I actually quit buying it. It's too convincing.

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

The most primitive version is just launching one process per request, piping the HTTP request into stdin, and piping the response out of stdout.

It works, but you can imagine the startup latency is rough and it takes a lot of resources.

There are faster variations that try to reduce the overhead. Ironically FaaS is sort of a rebirth of CGI

I don't consider it an OS if it needs an OS to run. Something like a "Ship can carry a boat, boat can't carry a ship" rule.

I think GP meant they could hack it remotely. If an attacker hacks a fly-by-wire plane remotely, I'd rather not be onboard.

Cool! I kinda want a uterus some day.

Yeah. And that's why TV stores really like slow-motion shots or static landscapes to show off the TV. Any motion will cause "HDTV blur" as the encoder struggles to describe complex motion with the limited number of bits it's allowed to use.

Stuff like static, film grain, particles like snow or rain, those all suck up bits from the same encoding budget.

"Why Snow and Confetti Ruin YouTube Video Quality" by Tom Scott probably explains it nicer than I can https://www.youtube.com/watch?v=r6Rp-uo6HmI&pp=ygUaYnJlYWtpb...

This could be a problem for video game streaming, and it could affect the artistic decisions a game studio makes - Drawing a billion tiny particles on a local GPU will look crisp and cool, but asking a hardware encoder to encode those for consumer Internet (or phone Internet) might be too much. I think streamers have run into this problem already.

(For JPEG - Newer codecs may differ) The codec has these "Basis functions", 64 of them, which are used to encode and decode each 8x8 block of pixels. https://en.wikipedia.org/wiki/Discrete_cosine_transform#/med...

Sine and cosine waves have a property that you can approximate a signal by just taking the dot product with these basis functions to get a list of coefficients, and then you multiply those coefficients with the basis functions to get the original signal back. Not all functions are basis functions.

You can see that the upper-left one is all white, that's the "DC" (Direct Current) basis. As you go right and down, they increase in frequency.

So the encoder gets all the coefficients and then it quantizes the high-frequency ones to save bits. That's why JPEGs often have ringing / rippling artifacts where an edge will be sharp but have waves coming out on either side.

If you quantize the coefficients enough, then some of those bottom-right ones end up quantizing to zero. So JPEG encoders run a lossless compression step on the coefficients to squish all the zeroes and small values together. You can crunch a JPEG smaller by replacing this lossless compression with a newer algorithm.

And the decoder just inflates those coefficients and multiplies them by the same basis functions to get the bitmap back.

There's details I don't understand in the middle like loop filters and de-blocking filters to hide the 8x8 block artifacts, but the heart of it is just "take a dot product with these functions to encode, multiply those dots with the same functions to decode".

For a couple years I've wanted to write a subtractive synth from scratch in software. But I _cannot_ find any source that explains how to write a low-pass filter, in code, without assuming tons of knowledge about calculus and these odd things like Z-transforms?

Like, I understand FFTs and DCTs. But the explanation for how to construct filters in software is pathetic.

I looked at the code for VCVRack but could not understand it. It's already optimized for SIMD, processing 4 signals at once, which didn't help readability. (I'm sure it's very fast though)

Well, yes. I suppose one could enable caching in Nginx or some other reverse proxy but Mastodon itself is just the app, there'd be no point for it to implement caching or a CDN when the admin can hook that on in front.

I'm sure also insulting to actually good candidates

I don't mind it much. I don't have great social skills but I don't mind answering simple questions. If someone is insulted by simple questions, they're probably gonna be a bad mentor to junior devs, right?

If any startups are in this field, I'd pay at least $100 / month to have a substantially better family than I have now

It bugs me cause it's kinda true but kinda misleading, I don't know if casual web users realize it's a whole different domain. Sometimes it's not important, sometimes it is.

Even the ray tracing / path tracing is half-fake these days cause it's faster to upscale and interpolate frames with neural nets. But yeah in theory you can simulate light realistically

Yeah I've been wanting to have that "comment on anything" for a while.

It's possible in technical theory. But sharing the comments would be hard. Federation might work. Spam moderation could be hard. And most websites refuse to go into iframes, so your options are limited to browser extensions, SOCKS proxies, and Opera Mini style apps that re-render the page. Which means you'll get less than a percent of a percent of people to use it.

I want to live in the 90s. CD audio is a little bit nicer tech. They say vinyls release VOCs. There's Internet, but not enough to drown in.

To err is human, to seek profit is common to all lifeforms