So as I understand it, Bonfire doesn't do a character limit like Mastodon does. This is potentially a long-form posting thing.Is is a commenting-on thing? No, I guess not. But it does otherwise feel a lot more like G+, particularly in that it has a close analogue to Circles.Does this do Markdown? It does, and live in the composer.Of course, all of this is fine for other Bonfire implementations, but I'm also curious how it'll show up for Mastodon instances. So I've followed this with my main Mastodon-self, and we'll see what comes of it.I can attach an image, but I can't embed it in the post. So here's my cat, just attached to this. He's a cutie. He had a brain tumour a few years ago, but got good treatment and he's doing well. He's on a lot of meds, as a result, but we love him and he's happy and cuddly.He's a #ragdollcat, which I wouldn't normally hashtag, but I am trying that out to see.OK, I think this is about baked. Let's see what we get!Oh NOOOO if I set circles after setting an image description, it clears the image description.And if I write a long post, I can't reach the "post" button.
+
-
Oh, looks like you can get discussion on a post, and it's threaded, too, simply by virtue of replies being themselves posts that you can reply to.TBH I did like unthreaded replies on G+; it was more like a normal conversation.Also, I think that the editor expects single newlines, but doesn't visually display that quite like it'll end up in a published post. I have a habit, from text editors, of doing double-newlines! So I thought, based on the look of the editor, that I should, and then the resultant post looked spaaaaaaaced ouuuuuuuut.Also, cmd-return doesn't post. Let's see if ctrl-return does. Nope!
Oh, and Masto displays things fine but:Strips all Markdown formatting.Ignores CWs.The first I can live with, but the second would seem to pose a defederation risk, because it makes it seem like you're not playing along nicely.