MurdoMaclachlan

Image Transcription: Screenshot

[The screenshot is from a GitHub commit summary. It is zoomed in to show just the tab headers for the "Checks" tab and the "Files changed" tab. The "Checks" tab has a number 1 next to it, and the "Files changed" tab has an infinity sign next to it.]

I am a human who transcribes posts to improve accessibility on Lemmy. Transcriptions help people who use screen readers or other assistive technology to use the site. For more information, see here.

Theoretically they might be able to, but it would be a very difficult case fought against a massive corporation. I doubt they'd consider it worth the trouble and legal fees, especially given there's no guarantee of winning.

Easily one of my favourite episodes in years. I'm a sucker for creepy monsters, cosmic horrors and monsters whose origins are only vaguely hinted at and this had all of that. Overall much more polished, better-paced and intriguing to me than The Star Beast (which I still liked!). This was Doctor Who back at its best for me.

Somehow, Altman returned.

Oh, so it's shit in the way I originally thought, then.

And also shit in the second way I thought, since adblock is a symptom of how terrible they've made the experience on their platform and if they want less people to use it they should make that experience more reasonable.

Given the shit big companies have got up to in the past and continue to get up to, as exposed in past and ongoing antitrust cases, that conspiracy theory you mention really isn't all that unrealistic. Yeah, it's not what happened in this case and it isn't the simplest solution, but it's absolutely a believable thing for YouTube to do, though I think they would have hidden it better if they had.

Ah, I was wondering why YouTube was taking so long to load recently. I thought it was just because their code was shit, and it turns out I was right, but not in the way I thought.

Image Transcription: YouTube Comment

@davidm.313

"Debugging. The game where you are the criminal, the victim, and the detective at the same time. But you probably don't know where the crime took place, or what it was. But there definitely is a crime."

I am a human who transcribes posts to improve accessibility on Lemmy. Transcriptions help people who use screen readers or other assistive technology to use the site. For more information, see here.

Still needs to be checked over to make sure it didn't get anything wrong. In my experience the mistakes AI make with monospace fonts tend to be very awkward to notice (like 1 and l and I and | being interchanged), so I'd have to go over with a fine tooth comb which, for me, since I type quickly, isn't noticeably faster and is a lot more boring.

Image Transcription: Code

[Transcriber's note: the first line in the following transcription is incorrect. After the equals, there should be eight instances of the word "Option", each succeeded by a less-than symbol, then two brackets, like (), before the first greater-tha symbol. However, if you type a less-than symbol on Lemmy, it seems to strip that symbol and whatever word comes next out of the source when you save the comment.]

type Wtf = Option>>>>>>>;
let two = Some(Some(Some(Some(Some(Some(None))))));
let three = Some(Some(Some(Some(Some(None)))));
let six = Some(Some(None));
unsafe {
    assert_eq!(
        std::mem::transmute::(two) * std::mem::transmute::(three)
        std::mem::transmute::(six)
    );
}

I am a human who transcribes posts to improve accessibility on Lemmy. Transcriptions help people who use screen readers or other assistive technology to use the site. For more information, see here.

I'm also experiencing this problem, however I don't see anything about being blocked by Cloudfare. What I do see in the network tools is that on the image's POST request, Lemmy is returning a 400 (Bad Request) error. Issue is happening on both the normal Lemmy UI and the Photon UI.

Neither, it'll be included as-is without a [sic]. I follow the guidelines of r/TranscribersOfReddit, since they were developed in cooperation with members of rBlind.

The policy there was always that doing any sort of change affects the message and delivery fo the original content, so it should be avoided. [sic]s are avoided because they affect the flow of the content, and particularly in posts with multiple typos they can be very distracting.