🇳🇱
Test post, ignore me.
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.
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.
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.
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.
@freemo
The one you are replying to yes, it rendered as expected.
The one with no formatting is my own, further above, this toot
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.
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?
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… 😃
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?
Yes – the one just above, for example. https://qoto.org/@design_RG/105119371158013921
Screen captures in :
- Mastodon web client.
- and Pinafore attached.
So the pinnafore client is the one with the “>” or the webclient was? Does rich text content from other servers behave the same?
@freemo @QOTO
The webclient is the one displaying the ‘>’ markings.
In general, Markdown in Glitch-Social is the best rendered one - showing heading sizes, quotes, a blank line after a quote block or a Heading2 title.
Pleroma has some glitches in those - like not showing larger text size for Headings as expected, and not showing a blank line after a heading and before the next paragraph as included in the original. (I filled a bug report about those on their dev site).
Except for the unique handling of the links that screenshot looks very similar to how it looks for me here on QOTO.
