*banned 4 MarkDown love* @design_RG@social.cleverlibre.org

@freemo I think you can use the smallest heading sizes as not really large text.

They might work as smaller text sizes than normal -- for the Fine Print when wanted, like legalese and insurance forms, lol...

H6 is not used much at all, by the time you get to H3 it's so close to normal text size that there's not much use for it.

I would assume H4 to H6 might all be subsized compared to normal text size.

Nice news that the Pleroma project is alive and well.

@freemo

> But I particularly like how our users can respond to an announcement with emojis :)

I have seen that being used as a user Survey tool in a pleroma node. Pretty cool. No text reply needed!

@freemo I think the Pinafore rendering is spot on. **5% decrease** on Heading size as you go down **is too little**, too small a difference to note.

And **Heading 1 is show as huge**, which is correct (and not recommended for Toots, as it annoys people )

Been there, done that and learned -- Header 2 works well for titles of posts.

* H1 works well for my Blog page titles.
* H2 for all subtitles from that point on.

Nice looking text results.

@freemo Thank you.

Here's how the post above renders on Pinafore. And on Mastodon web.

@freemo Thank you!!

I already noticed the Hidden URL is working perfectly, how on to try some Block Quote?

> Ok so some of the minor formatting issues you guys have mentioned with markdown such as a lack of space around bullet points or the inconsistent size of headers has now been fixed. The rich-text rendering and markdown should look a lot nicer now.

And let's see how it appears.

# Header 1 is TOO big for most cases.

## Header 2 works well as a Post Title

### Header 3 is good for Subtitles.

#Markdown love...

## MarkDown is simple, looks Good.

.
And here's a quick snapshot of some commonly used MD formatting commands.

Easy peasy as mentioned. See [the original page with more here too](https://www.markdownguide.org/cheat-sheet/).

#MarkDown #Reference for Content Producers. #GlitchSocial and #Pleroma, #Friendica all support it.

Now #Qoto does too. 😃

why stay in vanilla plain text Mastodon ?

## Set MarkDown as your Default Toot Format ?

* There is a place in Settings where you CAN lock in this preference.
* It will NOT do any harm - plain Text still looks normal.
* And if you use any MarkDown, it will be processed and rendered properly.

See the screenshot below for the location of this - a one time switch and done. Same as in Glitch-Social instances.

#MarkDown is rich and makes much nicer posts when wanted... 😃 ❣️

#Qoto new features.

@abloo @hansw Yes, just went to check and GS offers plain text, MarkDown and HTML but no BBCode, which Pleroma does support.

@abloo @hansw Glitch-Social does not offer BBCode support, as far as I know.

@hansw@mastodon.social @freemo
This thread might be useful -- it discusses the use of a group at guppe for a Book Club.

It has been in use and working. The main problem at the moments is that guppe does not have moderation or any anti-spam features built in.

https://discourse.qoto.org/t/technicolorrainbow-a-proposal-for-a-user-group-mailing-list/183

@gioypi @freemo Yeah, it's a lot different than a full screen width client.

I asked the author of Pinafore if he could maybe create a two pane mode like I like (full screen width use) and he politely declined. It would be a big change in the project.

@hansw You are welcome. Yes, things are going ok, I have not been using fediverse much in the last few months.

Glitch-Social instances have the best Markdown rendering that I have seen so far. Pleroma had a couple of issues, like not rendering Header2 text larger than normal text, and sometimes stripping a needed blank line after a block quote of text.

All of those rendered perfectly in Glitch-Social.

The code maybe could be looked at to use here as well? It's mastodon based and open source.

@gioypi @freemo Yes, sadly it's been a while that it stopped working.

In other mastodon instances, we could notice it much sooner, as it appears that mastodo 3.1.x was when it broke. Here it took a little longer to be noticed, since the code was based on 3.0 until now.

Maybe try Pinafore? It's a very nice client, although single column and leaving all kinds of empty space on the screen.

I just gave up on the add on and have used Pinafore or regular web client with wide screen mode.

I sent a feature request to the Glich-Social github, asking them if possible to incorporate that same functionality.

Which indeed makes for a great work space.

https://discourse.qoto.org/t/mastodon-screen-use-in-wide-screen-displays-a-search-for-better-results/280/4

and on Github : https://github.com/glitch-soc/mastodon/issues/1359

@freemo @gioypi

> That sounds like a fix that needs to be done by collapsed mastodon, but if you give me some more details I can look into it.

Indeed -- it has been reported previously on the git site for the add on. Mastodon 3.2.x broke something on it. It's been a few months, but it's just that Qoto moved to that branch level now. :(

https://github.com/Eskuero/collapsed_mastodon/issues/9

@hansw as rendered on Pinafore client.

@hansw Not quite...

@hansw

The Headers are displaying on the same size test -- an H1 should be larger than we see here.

# header1
## header 2
### header3

**BOLD**
*Italicized*
`Code works too`

@freemo @rgx

Yes, that seems to be correct -- something specific to Browser or possibly the Theme in use.

I took a screenshot on MS Edge (Chromium based) and it displays things very nicely.

[Quick Testing a Hidden URL](https://www.artstation.com/zhangxii),

I use a Dark Theme, Widescreen from the Qoto settings default theme choices.

The MS Edge screenshot is from a generic user's view, not logged in so it's the default theme (the blaring white one, lol)

@freemo @rgx
And a couple of minor things, formatting wise :

* in a **QUOTE block**, as seen in Pinafore, there was a Blank line introduced at the Beginning -- before the start of the Quote text.
* in a **Bulleted List**, the normally present blank line at the end on the list is suppressed (in mastodon web client), while it is displayed in Pinafore as expected.

Both of those can be seen in the screenshots above.

@freemo @rgx
Two screenshots of the same post.

1. as seen in mastodon web client.
2. as rendered in Pinafore client.

**CODE** formatting works perfect.

The **Hidden URL** one not, and it's a pity as it cleans up the posts a lot. But I am sure you can add it in.

Thank you...