I'm failing to understand GP's logic here. Why would someone who's posting some TV show's content in complete disregard of their intellectual property rights be bothered about AI scraping?
Thanks, that would be great!
I am trying to think how this could work. Generally, subtitles are embedded as a separate track in the video container or as a sidecar .srt file [1].
Perhaps they can be converted and shown using the WebVTT API[2] or <track> tags [3]?
Edit: Maybe that wouldn't work, here's a relevant stackoverflow post [4]
I used to stream movies from my desktop over the local network with VLC and the main issue I faced was that I could never get the subtitles to work. I took a quick look at this repository and it doesn't look like they support subtitles either.
Microsoft Design also released 4K renders of nostalgic wallpapers (including bliss) a few years ago. I can't find the original link but here's the reddit post with the pictures.
It really grinds my gears that the uploader had to ruin the "Greatest Shot in Television" by stretching the 4:3 video to 16:9.
I know I sound like a pedant but so many of these old TV recordings are uploaded this way on youtube. I was so annoyed by this infact that a few years ago I made a dumb extension that squeezes the video element back to 4:3 [1]. I'm not sure if this still works though.
I've been pronouncing both of them as /dʒis/ like hiss and not /dʒɪz/. I however am not a native english speaker of English. I wonder if native speakers gravitate towards the z more?
While I know that it may have been a security liability, I'm particularly sad that they're removing the AX.25 module from the kernel.
> and since nobody stepped up to help us deal with the influx
of the AI-generated bug reports we need to move it out of tree
to protect our sanity.
This thread from the linux-hams mailing list [2] has more insight into this decision. I guess the silver lining is that, more modern protocols (in userspace), written in modern languages will become the norm for HAM radio on linux now.
I agree with the notion that having multiple passes makes compilers easier to understand and maintain but finding the right number of passes is the real challenge here.
The optimal number of passes/IRs depends heavily on what language is being compiled. Some languages naturally warrant this kind of an architecture that would involve a lot of passes.
Compiling Scheme for instance would naturally entail several passes.
It could look something like the following:
Thanks for working on LispPad, I'm really enjoying using it.
> Polar complex number literals are actually not part of R7RS
I actually thought they were part of the spec. Specifically, I am referring to the last paragraph from section 6.2.5 of R7RS small <https://small.r7rs.org/attachment/r7rs.pdf>
This is the excerpt from the pdf:
6.2.5. Syntax of numerical constants
...
There are two notations provided for non-real complex
numbers: the rectangular notation a+bi, where a is the
real part and b is the imaginary part; and the polar no-
tation r@θ, where r is the magnitude and θ is the phase
(angle) in radians. These are related by the equation
a + bi = r cos θ + (r sin θ)i. All of a, b, r , and θ are real
numbers.