rc8s

programmer

[rc8s @rc8s1]

@k_effective_1 @APStylebook It isn’t incorrect grammar any more than their ridiculous space-emdash-space preference is. These are matters of style.

They have explained elsewhere their Black/white capitalization guidance.

[rc8s @rc8s1]

@Mikemaximum @Shedletsky @sleitnick Roblox already added vibe-coding. But anyone could vibe-code without a bespoke feature anyway.

[rc8s @rc8s1]

@k_effective_1 @APStylebook There are answers. You just didn’t look.

[rc8s @rc8s1]

@levigaming1207 @DavidBaszucki Nobody gets terminated for saying hi.

[rc8s @rc8s1]

@TRetrofied Thanks, Retro

[rc8s @rc8s1]

@VITAC_Captions VITAC... you know captions and subtitles aren't the same, though, right? You've been around for 40 years. A random person, sure, it doesn't matter. But you?

[rc8s @rc8s1]

@VITAC_Captions From VITAC?

[rc8s @rc8s1]

@TeamYouTube Thanks, but this isn't a device/app issue—it's a bug in how YouTube renders TTML captions with random placement. Basic troubleshooting won't fix this, unfortunately. Could you escalate this to your captioning team? Any workaround in the meantime? (Why DMs work better for this.)

[rc8s @rc8s1]

@TeamYouTube Hi. I have a very specific issue with a caption file on YouTube—can I DM you for more information?

[rc8s @rc8s1]

@TeamYouTube Hellooo, @TeamYouTube?

[rc8s @rc8s1]

@TeamYouTube (No, I didn't make the video in the image, but I did caption it and create the file.)

I mentioned DMs to share my file and see if you can spot what's causing this. The issue seems to be only on YouTube. Maybe some YouTube captioneer expert at your team can help.

[rc8s @rc8s1]

@TeamYouTube (Also, by "The issue seems to be only on YouTube," I meant "only on YouTube's end.")

[rc8s @rc8s1]

@GBH You guys are the first and best captioner. Why are you using Rev?

[rc8s @rc8s1]

@rev "Versions of the audio content found in videos"? Come on. Captions just display transcription of speech. Why are you guys so hung up on "converting"? That's why you were also hung up on captioning silence, even if necessary, for the longest time. Your style is very insupportable.

[rc8s @rc8s1]

@3playmedia @rev Rev doesn't handle reading speed either, but they don't have ridiculously long captions under one second (Full name + "THROUGH INTERPRETER"). I'm sure I've seen 3Play captions go under one second. That (and a lot of other things) is why transcription SHOULD be a separate service.

[rc8s @rc8s1]

@3playmedia I've seen some of your captioners make mistakes they really shouldn't. Your style guide isn't complete. It doesn't even cover ellipses. Don't pull a @rev.

Also, slightly delaying fast captions at least SOMETIMES is probably good for reading speed. You don't handle it at all.

[rc8s @rc8s1]

@ClementeJose @rev @PCMag Just don't use it for captioning. Use 3Play Media or whoever else, but not Rev. If you do, at least use Rev Pro, which is half decent.

I could write an essay worth of things wrong with the captioning style guide. Their transcriptionists are slightly more qualified.

[rc8s @rc8s1]

@3playmedia @USUAggies 3Play, can you either follow me or open your DMs? You can't DM others who don't follow you if you don't have Twitter Blue now.