79
MASH (1977, & TV intro link) (media.piefed.ca)
submitted 3 weeks ago by to c/vintageads@sh.itjust.works
26 comments fedilink hide all child comments
 

M*A*S*H ran from 1972 to 1983, and is widely regarded as one of the greatest TV series of all time. Mobile Army Surgical Hospital units were real, but the show's 4077th was fictional. It was loosely based on the experiences of US Army surgeon Hiester Richard Hornberger Jr during the Korean War, who wrote the book MASH in 1968, spawning a film and a TV show.

The 2.5 hour final episode of M*A*S*H, set to the war's ceasefire, remains the most watched series episode in US TV history as of 2026, and for 27 years was the most watched TV production ever (not counting the Apollo 11 moon landing, which was categorized as a news story). The ad spots sold for more money than Superbowl spots.

This is the intro theme from the TV show (youtube).

Dr. Hornberger died in 1997 at age 73 from leukemia. This is Hornberger during the Korean War, serving in the real life 8055th MASH unit.

Hornberger

The main characters from the show are still household names 43 years after the end of the series.

M*A*S*H cast

M*A*S*H

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 4 points 3 weeks ago* (last edited 3 weeks ago) (11 children)

Hmm. ISWYM, but for some reason it looks fine for me (on web site). Edit: which is why I didn't notice.

Is this something that looks different on mobile? Here's my SS, before editing to add escapes. I'm not sure why it isn't italics.

fpOchIhLy0rfT7V.png

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 11 child comments
    •
  • [–] 2 points 3 weeks ago (3 children)

    If a mobile client doesn't render Markdown correctly, then it won't render that Markdown correctly, which would be desired in this rare case :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 2 points 3 weeks ago (2 children)

    I'm using the web site though, not a mobile client.

    I can only guess that it detected mismatched asterisks and decided not to italicize. It certainly does in other case. Like this for example is italics.

    Butthisisnt*italics for me. Probably is for others, sounds like.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 weeks ago* (1 child)

    https://i.imgur.com/US1fPnc.png

    If a frontend interface doesn't render Markdown properly… :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 3 weeks ago

    Seems like there isn't really a "properly" here. Stackoverflow thinks markdown doesn't have a single official spec, but lots of different specs saying different things, which people tried to unify, which resulted in yet more specs and yet more MD parser behaviors. Wikipedia agrees:

    At the same time, a number of ambiguities in the informal specification had attracted attention.

    Example, some italicize if the asterisk comes after a non-alphanumeric character, and others don't.

    Sounds like a mess. But it doesn't seem as simple as "if an interface doesn't render markdown correctly."

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 3 weeks ago (6 children)

    Not sure if you already edited but it looks correct (just like your screenshot) for me on Voyager.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] [S] 1 point 3 weeks ago* (3 children)

    Yeah I did edit the text body after it was pointed out.

    I didn't know it was messed up in the title too (didn't expect markdown there) so I'll fix that too.

    Edit: tried to fix the title, but now it shows the single backslashes visibly, instead of escaping the asterisks. Maybe there's no way to have the post title right for everyone?

    Maybe clients are not supposed to use MD in the titles, but since it seems to be different for different people, I removed the bloody things entirely, so now it just says MASH.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 weeks ago* (2 children)

    I'd leave the title as-is, don't try to accommodate those of us with app issues!

    Frontends shouldn't be applying it to titles at all, they should be raw text

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 weeks ago (1 child)

    I’m on voyager and this is what I see in the title:

    I wonder if it’s an instance thing?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 3 weeks ago

    Oh yeah, you're right. The title does look like that but his comment looks normal.

    Can't blame that one on OP, though. Voyager really shouldn't be applying formatting to title! The dev is really responsive but I forgot their name or I'd ping them

  • permalink
  • fedilink
  • source
  • parent