GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    localzuk (localzuk@ohai.social)'s status on Friday, 24-Nov-2023 10:33:21 JST localzuk localzuk

    I find it outrageous and incredibly offensive how often subtitles are censored.

    I've experienced it on broadcast TV. On Amazon. On YouTube. And elsewhere.

    Deaf people do not need swear words hidden. Those of us with hearing loss don't suddenly decide, "Ah, yes, because I can't hear fully, I don't want to experience swearing anymore."

    Stop censoring our content!

    #Subtitles #ClosedCaption #Censorship

    In conversation Friday, 24-Nov-2023 10:33:21 JST from ohai.social permalink
    • clacke likes this.
    • Embed this notice
      alcinnz (alcinnz@floss.social)'s status on Friday, 24-Nov-2023 17:08:52 JST alcinnz alcinnz
      in reply to

      @localzuk You know, there was device from the late 1980s or early 1990s which used the closed captions to mute swearwords (during which it'd show the subtitles with a euphemism).

      Ironically prudish captions like you're rightly complaining about would break this prudish settop box...

      Not that I see any point in this tech, it comes from the same misguided place...

      In conversation Friday, 24-Nov-2023 17:08:52 JST permalink
      Haelwenn /элвэн/ :triskell: likes this.
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 24-Nov-2023 17:11:59 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      @localzuk I think the only one where it could make sense is like "f*beep*ing *beep*" but I'd much prefer putting the actual words and crossing them out (given actual text formatting support, not one of those unicode hacks).
      In conversation Friday, 24-Nov-2023 17:11:59 JST permalink
    • Embed this notice
      David Schuetz (darthnull@infosec.exchange)'s status on Friday, 24-Nov-2023 21:53:38 JST David Schuetz David Schuetz
      in reply to
      • mybarkingdogs

      @mybarkingdogs @localzuk The <foreign> I agree with totally. If other characters in the scene are expected to understand it, caption it “[in language] whatever”. If they’re not, then maybe caption it in the spoken language? If a bilingual hearing viewer can get a leg up on the characters, why couldn’t a deaf bilingual viewer?

      The <untelligible> I think works when it’s truly background speech, not meant to be heard. Often you can’t even hear it on the soundtrack, so the note helps clarify that deaf viewers aren’t missing anything — you see people speaking but you’re not meant to know what they’re saying.

      In conversation Friday, 24-Nov-2023 21:53:38 JST permalink
      clacke likes this.
    • Embed this notice
      mybarkingdogs@mastodon.sdf.org's status on Friday, 24-Nov-2023 21:53:39 JST mybarkingdogs mybarkingdogs
      in reply to

      @localzuk ARGH this and the "[foreign]" and "[unintelligible]"

      I'm not Deaf but I often use captions and subtitles to understand more (auditory processing + age and loud music when younger related loss) and seeing this shit makes me almost incandescent with rage.

      Like it's a sign they're definitely not paying the captioner well, using AI captioning, and/or not providing their captioners with a script/employing people who can translate languages

      In conversation Friday, 24-Nov-2023 21:53:39 JST permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.