@LibertyBeta@mastodon.social

We be lit? 

Weird, I was trying to mention the European commission.

And here's a formatting problem, with Markdown's code formatting I get an opening chevron at the beginning of the link, and then a closing chevron after the underscore (it says /@EU_>commission)).

Hi, is there any plan for RSS support?

I'd suggest the following: threads would be treated as blog posts, and Bonfire posts as paragraphs or sets of paragraphs. The thread would be published after a timeout (e.g. 45 minutes or 24 hours) or after a post is ended with “EOF”.

And bam, you've got RSS feeds fixed with microblogging.

This could be opt-in, for example for academics, or for institutions (e.g. @).

around a bonfire, civilisations begin
around a bonfire, stories are told
around a bonfire, families grow
around a bonfire, revolutions are conspired
around a bonfire, alliances are strengthened
around a bonfire, futures are predicted
around a bonfire, evils are cured
around a bonfire, ancestors visit
around a bonfire, knowledges are shared
around a bonfire, what will you do?

Maybe… Bonfire emojos? Bonfire Signal stickers?

Low priority issue again, but I also can't fetch my blog posts from WriteFreely (article object type?) using the search function

It's weird because my post is formatted correctly in my local TL but not in the search panel

Low priority issue: my blog posts, available at @corail@xn--ocane-csa.fr, aren't properly formatted, for example you don't see the post title.

Ok, your replies count doesn't only show direct replies but basically the number of posts in the thread. It's a great idea! Is it deliberate? (It should be the default, IMHO)

That's enough bug reports for the day! Good luck!

Ok lol, I'm gonna describe it:

Imagine an opening chevron, like this <, then the https:// syntax, then the first r, then a closing chevron (>), then the rest of the link, presented like this by the verbatim formatting.

I think it's a problem in the way (a) tags are handled.

Edit: as I edited this post I saw that the (a) tag was followed by a closing (/a) tag at the end of the line!

Edit 2: the backticks syntax doesn't work for (a) tags so I've replaced chevrons with parentheses!

Ok, so I'll try to wrap this up:

1. /settings/profile returns a 404;
2. inserting links “as is” removes Markdown-formatted links (you just get the text);
3. inserting a first Markdown-formatted link works fine, but inserting a second one gives about the following syntax (in the composer, but not in the final output): https://r eflowproject.e(there was a u at the end of the link but I've erased it by mistake and I can't undo it, and I'm not sure to be able to reproduce the bug)

In the post above, I've inserteda link to Dyne and another to the Reflow Project. Well not like this, but this does highlight the problem, doesn't it?

Aaaand also, let's say that I'd add a link to Dyne and [another to the Reflow Project]( https://re flowproject.eu).

As you can probably see, there's a problem with the formatting of the second link.

But “a link” in the post above (in “as inserting a link would turn…”) was meant to point to the Dyne website. It seems to have been overridden by the insertion of Twitter and Facebook's tracking links.

I've only put the paths above as inserting a link would turn the entire rest of the line as the link. It works with the text syntax (and the code formatting is really pretty, good job!) but not if I insert the link uhh, in the usual Facebook/Twitter format, that doesn't accept formatting so posts can pretend it's a direct link and not a tracking link to e.g. fb.me or t.co.

Did my post get lost into the void? Anyway, the button to edit my bio (/settings/profile) from my profile itself (/@Oceane) returns a 404

Oops, we recently changed CW to use the summary field instead of the name (title) field, in line with what Mastodon now does, and need to update that in the edit form. Thanks @Oceane!