• Salvo@aussie.zone
    link
    fedilink
    English
    arrow-up
    122
    ·
    5 days ago

    Well Akshually.

    Misconfigured MIME types on certain old web servers would display the raw data of any file.

    I had an Executive who wanted to watch a Video from some “Motivational Speaker” (scam artist) on her iPad. The Scam Artist (Motivational Speaker) had it wrapped in a Flash Applet and when she contacted them about not being able to watch the video, he started soap boxing about how terrible iPhones and iPads were and that Apple is Doomed.

    I checked the website and found that the MP4 file had the MIME type Octet/Stream instead of Video/MPEG4 and I created a dummy xHTML page with the appropriate tags.

    The video worked perfectly on her iPad and her husband went on to watch the video, believed the “Motivational Speaker” and was fleeced for thousands of dollars.

      • kboy101222@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        19
        ·
        5 days ago

        I’ve never quite managed to understand what the point of xHTML even was. Damn near all of the time, it was still sent as plain ole HTML

        • kautau@lemmy.world
          link
          fedilink
          English
          arrow-up
          35
          ·
          5 days ago

          The structure was meant to be more strict syntactically, but almost universally browsers didn’t give a shit because it was way better for users to just “do your best” to process broken or sloppy xhtml/html

          That being said, some of the rules meant to enhance the rigidity of html were brought in from the xhtml spec to HTML5.

          While browsers will still do a “best attempt” at rendering the page, most websites aren’t even written in raw HTML anymore by devs, it’s either front end single page apps populating the dom or backend generated templates spitting out generated HTML, most of which generally follow the rules of html (except Wordpress, which needs to die in a cave)

          • SteveTech@programming.dev
            link
            fedilink
            English
            arrow-up
            8
            arrow-down
            2
            ·
            5 days ago

            Just to be that guy, 'use strict'; is specifically for JavaScript, and should still probably be used. With xHTML there were a few different DTDs that went in the DOCTYPE, Strict being one of them.

        • Simulation6@sopuli.xyz
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 days ago

          Did xhtml come about as part of the semantic web project? I learned about the two at the same time, so I may be confused about that.

          • dejected_warp_core@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            5 days ago

            Potentially? I don’t recall, myself. But having markup that is more readily machine parsed would only help the semantic web’s goals.

    • riquisimo@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      14
      ·
      5 days ago

      Have you ever considered a job as a scam artist? They need people like you! You could be making thousands of dollars from home! First you need to be desperate, then you need to work for free…