Now if someone else a URI, is there going to be any confusion on how many times a URI needs to be decoded?

If the answer is yes, then we have a problem.

(and by looking at the other comments in this thread, the answer is most definitely yes)

Chrome's blink was the only major browser engine not supporting it and that prevented it from becoming a web standard and they refused to acknowledge they were wrong.

Chrome only backtracked once jpeg-xl was subsumed into the PDF standard because if Chrome did not support jpeg-xl, they would by extension also not be supporting pdf.

(too late to make edits)

Make sure you're not getting confused with random analog-horror / backrooms videos from random creators. Those videos are connected to the movie in any way.

Kane Pixels (Kane Parson)'s youtube series and the movie were both made by him and are in the same canon. It's definitely a canon where you need to pay attention and rewatch things to see the connections. It's probably the closest thing Hollywood has ever been to a House of Leaves style story.

Vg nafjrerq gur gvzryvar bs ubj gur onpxebbzf jrer perngrq.

Va 1972 Vina Orpx jnf qbvat culfvpf rkcrevzragf naq jnf noyr gb znxr znggre qvfnccrne sebz bhe fcnpr.

Bapr ur svtherq bhg gung vg unq orra genafcbegrq vagb n qvssrerag fcnpr, ur crgvgvbarq gur tbireazrag sbe rkgen shaqvat. Vs gur HF tbireazrag pbhyq perngr rkgen fcnpr ng jvyy, vg jbhyq or n fpvragvsvp oernxguebhtu ba gur beqre bs fcyvggvat gur ngbz naq jbhyq punatr gur jbeyq. Vg sryy haqre gur cheivrj bs gur Qrcnegzrag bs Raretl (gur fnzr qrcnegzrag vaibyirq jvgu ahpyrne jrncbaf).

Guebhtu gurve rkcrevzragf gelvat gb perngr n ynetre qbbejnl ("guerfubyq") gb n arj fcnpr, gurl pnhfrq gur snzbhf 1989 rnegudhnxr naq trarengrq gur onpxebbzf nf jr xabj gurz, qvfpbirerq gur ragvgvrf jvguva, naq jrer erfcbafvoyr sbe gur nppryrengvat zvffvat crefbaf pnfrf nf zber naq zber bcravatf orpnzr cbccvat hc.

Gurl xarj gur ceboyrz jnf trggvat jbefr, naq gurl pbagvahrq gb pbire vg hc naq pbagvahr gur rkcrevzragf, nyy va gur ubcrf bs zbargvfvat gurz be hfvat gurz gb tnva n fgengrtvp nqinagntr bire bgure pbhagevrf.

Gur zbivr fubjrq jung unccrarq jvgu bayl bar bs gubfr qbbejnlf. (naq gur qbbejnl gur frnthyy pnzr guebhtu, naq gur bevtvany guerfubyq va gur Nflap snpvyvgl).

Jr nyfb fnj gung gur onpxebbzf pbagvahrq gb ribyir bire gvzr orpbzvat zber ernyvfgvp, riraghnyyl sbezvat gur "fgvyy-yvsrf" jvgu rqvoyr juvgr znff syrfu.

Juvpu yrnqf gb gur gehr ubeebe:

Nf gur jnyy orgjrra obgu fcnprf orpbzrf guvaare ng na rire vapernfvat engr, naq nf gur onpxebbzf pbagvahrf gb ribyir, jung unccraf arkg, naq jvyy jr or noyr gb fnir bhefryirf?

Like the dvd logo screensaver

The movie was great but it's not a stand-alone movie, it is a small piece of the full story so don't go in thinking that everything will be explained and tied up in a neat little bow.

The movie takes place in Kane Pixel (the movie director's) youtube series: https://www.youtube.com/playlist?list=PLVAh-MgDVqvDUEq6qDXqO...

It makes a lot more sense if you watch the full youtube series first.

The QR example works fine though

Whenever I'm watching lectures / talks / podcasts, I tend to watch/listen to them at 2x to 2.5x times speed.

I only need to lower it if someone flubs an important word in a definition, I'll replay that part at 1x speed.

If the person is talking particularly slowly (usually for international audiences) I put the speed up to 3x to 4x speed so it sounds like normal 2x to 2.5x speed.

---

My youtube muscle memory:

(standard video controls used by every video editor ever)

J = back 5s

K = play/pause

L = forwards 5s

(youtube specific controls)

Shift F = toggle fullscreen

Speed controls (this part is muscle memorised as fast as a password input):

1. Cmd/Ctrl Shift K: opens console

2. Up arrow: loads previous command, typically: document.querySelector('video').playbackRate = 2.5

3. Enter: runs command

You have to type in the command for the first time, after that to change the speed, change "2.5" to whatever number you want and console history will remember the change so you can go through the different values with up/down arrows before pressing enter.

Those literally work with text prediction.

If you take the text prediction out of it, nothing happens.

You stick a harness around a text predictor which then triggers the text predictor.

If you think I am missing something then please do point it out.

So, bsd pledge-likes, capabilities, design-by-contract, linear types, effect systems, ZKPs, provably correct systems, etc...

See: https://fediverse.zachleat.com/@zachleat/116529994444529036

How?

It all still functions with text prediction

If pointing out the flawed approach to making something more productive isn't productive, then what do you consider to be productive?

> Less than a decade ago the idea that a computer could take a fuzzy human-readable description and turn it into executable code was science fiction

Cobol was sold to people on the idea that anyone could create something with fuzzy human readable description that would result in executable code. That was back in the 60s.

What lessons did we learn?

1) Leaving things to the people who make fuzzy human readable descriptions turns out to be a terrible way to have things implemented.

2) Slowly and deliberately thinking things through before, during, and after implementation always leads to better results.

It's a lesson that keeps needing to be re-learned by people who don't/can't look at things through a historical lens.

It was the same with cobol, as it was with programming in spreadsheets in the 80s, as it was with the nocode movement in the 00s, as it is now again with LLMs in the 20s, and it will be again with a future generation in the 40s.

---

> As is the ability to write long form text, and be so hard to distinguish from real that placing an em dash in your text will cause an uproar on this forum.

Long form text generation that is hard to distinguish from human authored text also goes back to the 60s.

That's when we got the first instances of the Eliza effect.

> You can describe things by their fundamental functions and make many things sound elementary but I find it counter productive given the capabilities we've seen from this technology

The capabilities we've seen are:

- Text prediction/generation

- Inducing the Eliza effect

Transitioning components to rust eliminates certain categories of bugs leaving the rest of the bugs to be dealt with.

We'd likely end up needing another language with stronger type and effect systems to eliminate more categories of bugs. Probably something which enforces linear types, capabilities, units of measure types, and effects.

And you'd have to update linux itself to switch to capabilities.

My example: https://codepen.io/spartanatreyu/pen/xggjWz

------------------------------------------------

Overall, CSS tends to be the better tool for the job.

SVG has better paths and more interesting filters, but it's held back by a few critical issues.

1. A small amount of filters are not hardware accelerated in firefox/servo's webrender engine, which causes them to fallback to software rendering. Usually it just freezes the web page for a second or two while the image software renders before returning to normal performance, but if you try to animate any of the values it locks up the entire page.

That basically animated SVGs with filters a no-go.

2. Safari doesn't draw SVGs properly, it has a built-in "performance budget" where it just stops drawing the rest of the SVG if it isn't finished within a split second. Which is fine for something like an icon, but terrible for things like the main feature graphic / background of a page.

Meanwhile CSS keeps getting better. Its filters are improving (filter, mix-blend-mode, backdrop-filter), and its animations are improving too (keyframes + animation, transition, offset, custom-properties + @property's syntax, scroll-timeline, cross-document view transitions).

The two things that CSS is worse at than SVG are:

1. Paths (in which case, you can just put SVG paths into your page and style them with CSS for anything more complex than a static stroke/fill anyway)

2. Generating textures (which you can't guarantee look consistent thanks to Safari, so you're usually better off sending a hand optimized texture over the wire anyway)