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
    Neil Brown (neil@mastodon.neilzone.co.uk)'s status on Friday, 03-Mar-2023 21:22:05 JST Neil Brown Neil Brown

    # Mastodon and Markdown

    There's nothing stopping anyone using Markdown *now* but, as far as I know, no client renders it.

    And if a client did:

    * what about all the other clients that don't?

    * what about people using non-Mastodon AP/fedi systems which don't have clients which support Markdown?

    Do people on clients which don't support Markdown want to see Markdown-formatted posts?

    In conversation Friday, 03-Mar-2023 21:22:05 JST from mastodon.neilzone.co.uk permalink
    • Embed this notice
      Kevin Marks (kevinmarks@xoxo.zone)'s status on Friday, 03-Mar-2023 21:22:04 JST Kevin Marks Kevin Marks
      in reply to

      @neil The elk.zone client renders *italic* and **bold** client side but not bullet lists etc. The right answer is for the *posting* client convert to html (elk.zone does that too), so all clients should see the styling in this post.

      In conversation Friday, 03-Mar-2023 21:22:04 JST permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Elk

      2. https://xoxo-media.sfo2.cdn.digitaloceanspaces.com/media_attachments/files/109/959/313/115/850/670/original/94e804bed2aed746.png
      clacke likes this.
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Friday, 03-Mar-2023 21:23:03 JST clacke clacke
      in reply to
      • Kevin Marks
      @KevinMarks @neil All clients except Mastodon web, which sanitizes the HTML and removes formatting.
      In conversation Friday, 03-Mar-2023 21:23:03 JST permalink
    • Embed this notice
      Kevin Marks (kevinmarks@xoxo.zone)'s status on Friday, 03-Mar-2023 21:34:09 JST Kevin Marks Kevin Marks
      in reply to
      • clacke

      @clacke @neil Oh, really? I have seen html passthrough in mastodon web before.

      In conversation Friday, 03-Mar-2023 21:34:09 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Friday, 03-Mar-2023 21:34:09 JST clacke clacke
      in reply to
      • Kevin Marks
      @KevinMarks @neil It's possible it allows something, but not e.g. slanted text, bold text or block quotes.

      Glitch-soc corrects this unexpected behavior. Pleroma's Mastodon derives from glitch-soc, so it shows formatting too.

      Every other OStatus or ActivityPub frontend before and after Mastodon, as far as I know, has allowed harmless formatting.

      mastodon.social's rendering of the formatted post above is all plain: mastodon.social/@losttourist@s…
      In conversation Friday, 03-Mar-2023 21:34:09 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Friday, 03-Mar-2023 21:34:47 JST clacke clacke
      in reply to
      • Kevin Marks
      @KevinMarks @neil <a> elements are allowed by Mastodon, obviously.
      In conversation Friday, 03-Mar-2023 21:34:47 JST permalink
    • Embed this notice
      Kevin Marks (kevinmarks@xoxo.zone)'s status on Friday, 03-Mar-2023 22:03:18 JST Kevin Marks Kevin Marks
      in reply to
      • clacke

      @clacke @neil though only absolute ones; you can't link to id tags within the same post (eg for footnotes - see https://tantek.com/2023/043/t1/footnotes-unicode-links)

      In conversation Friday, 03-Mar-2023 22:03:18 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: tantek.com
        I got auto-Unicode & linking footnotes^1 working! In notes like this post, I can type "^1" (like after the word "footnotes" above) and the code on my server automatically: * turns it into a Unicode superscript '¹' * links it to the expansion at the end of my post Similarly, I can type "^1" at the start of an expansion line (e.g. at the end of a post) and that code automatically: * turns it into a Unicode superscript '¹' * links it back to the inline reference Since that code is part of my site’s CASSIS auto_link function^2, all previous posts with such "^n" style footnotes have also been updated, like my day 6 post^3 and since. Clicking an inline footnote reference scrolls to the line with the footnote expansion. Clicking the Unicode superscript number at the start of that expansion scrolls back to the inline footnote reference. I decided to postpone adding the small return arrows '⮐' at the end of a footnote expansions. Linking the superscript numbers to each other works well, and seemed sufficiently discoverable without being distracting. By using post-specific unique prefixes for the footnote reference & expansion links, those links also work even in the presence of more than one post with footnotes, e.g. on my home page^4. They’re also in my Atom feed entries. I’m curious how the footnotes links in a post work in other contexts, like when viewing in a reader. I also discovered that Unicode superscripts were inconsistent on some platforms, and added a bit of CSS to set an explicit font-family for footnotes numbers: /* CSS style rule to use a specific font for footnote refs and expansions */ a[id*='_ref-'],a[id*='_note-'] { font-family:"Arial Unicode MS",system-ui; } /* end of style rule */ I added this and some other tips to the #IndieWeb footnote page^5. This is day 30 of #100DaysOfIndieWeb #100Days ← Day 29: https://tantek.com/2023/037/t1/post-glossary → Day 31: https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox ^1 https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink ^2 https://tantek.com/cassis.js ^3 https://tantek.com/2023/006/t1/forward-in-time-links ^4 https://tantek.com/ ^5 https://indieweb.org/footnote - Tantek
      clacke likes this.
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Friday, 03-Mar-2023 22:07:14 JST clacke clacke
      in reply to
      • me
      • Kevin Marks
      @me @KevinMarks That's where the decision to make the wire format HTML helps. If your client supports Markdown you know which Markdown. As long as it looks alright on your side it'll look the same everywhere except on mainline Mastodon and command-line clients.
      In conversation Friday, 03-Mar-2023 22:07:14 JST permalink
    • Embed this notice
      me (me@social.jlamothe.net)'s status on Friday, 03-Mar-2023 22:07:16 JST me me
      in reply to
      • Kevin Marks
      @KevinMarks Especially given that there is no one universal standard for Markdown.
      In conversation Friday, 03-Mar-2023 22:07:16 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Wednesday, 08-Mar-2023 22:06:06 JST clacke clacke
      in reply to
      • me
      • Kevin Marks
      @KevinMarks @me Mainline Mastodon is being fixed! Suddenly the glitch-soc functionality is merged without further comment.

      github.com/mastodon/mastodon/p…
      In conversation Wednesday, 08-Mar-2023 22:06:06 JST permalink

      Attachments


    • Embed this notice
      Kevin Marks (kevinmarks@xoxo.zone)'s status on Wednesday, 08-Mar-2023 22:06:19 JST Kevin Marks Kevin Marks
      in reply to
      • clacke
      • me

      @clacke @me nice, though <ins> as well as <del> could be good for showing edits, and <s> as a <del> synonym

      In conversation Wednesday, 08-Mar-2023 22:06:19 JST permalink
      clacke likes this.

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.