@freemo @QOTO >> Test post, ignore me.

Yep. Could try an unlisted or DM style post, it's what I do for markdown checking if a post is more complex (to see if all is well; then delete/redraft and change to normal privacy).

@QOTO

@design_RG

Not really. The group server wouldn't work if it were a direct message due tot he nature of the group "standard" (it needs to be able to reboost your post for it to show as a group post effectively, though because its an actor type group it doesnt look like a boost).

I believe unlisted would work though.

@QOTO

@freemo

Ah, I see. ***Followers only*** would work, right? Yuo mentioned it as a possible **Private group** arrangement.

@QOTO

@design_RG

No because groups can not follow people and do not follow you, you follow the group.

When I suggested followers only for the group to make it private it would be the group that would set its status to followers only (in other words a locked account where followers need to be approved before they can follow you). The individual posts would still need to be public you just couldnt view the group itself

This is stuff that needs to be fixed, its not perfect. In a future release i will be adding the ability to post to the group in a private way. When it comes to truly private groups (your original post is private AND the group is private) it gets a bit complicated and so far all the solutions require some change in the clients themselves.

@QOTO

@freemo

Very nice that you are taking this on -- an enhancement to Fediverse features. Well done... 😃

BTW - seems **MarkDown formatting** ins broken at the moment? (noticed in an earlier post in this thread; some bold and bold-italic only showing as asterisks, plain text). Adding a bit of format to test this, via Pinafore.

@QOTO

@design_RG

Can you see the formatting you made in this post? Renders just fine to me.

My guess is you saw a plain text post that used asterisks for emphasis without the intention of bolding it. Its pretty common.

@QOTO

@freemo
The one you are replying to yes, it rendered as expected.

The one with no formatting is my own, [further above, this toot](https://qoto.org/@design_RG/105119247687187651)

I found it odd how it did not show MD - I have it **setup as default for all toots in Mastodon Preferences**, so I don't have to worry about changing back and forth.

@QOTO

@design_RG

Ok thats interesting if your own markdown post isn't rendering as markdown.. are you saying it doesn't format it with the markdown when you post from a mobile client specifically. Or do you get this error from the web too?

@QOTO

@freemo @QOTO

> Ok thats interesting if your own markdown post isn’t rendering as markdown.. are you saying it doesn’t format it with the markdown when you post from a mobile client specifically. Or do you get this error from the web too?

The post I referred to and linked above was done in my laptop, FF browser using the mastodon web client.

It's odd that it did not format as expected.

The next post I wrote in Pinafore, also on the same browser, just one tab aside. The Bold and Italic did display, I did that specifically for testing.

Odd since posting from the web client previously for testing, earlier this week, was working fine.

***Regarding Quoted paragraph*** - it shows properly in Pinafore, not in masto web client.

Odd... 😃

@design_RG

Very odd, you are the first mentioning it.. do you have an example of a post where the quoting isnt rendering properly in the web client too so i can see if that happens for me?

@QOTO

@freemo @QOTO

Yes -- the one just above, for example. https://qoto.org/@design_RG/105119371158013921

Screen captures in :
* Mastodon web client.
* and Pinafore attached.

@design_RG

So the pinnafore client is the one with the ">" or the webclient was? Does rich text content from other servers behave the same?

@QOTO