I'll start by just commenting on things you may have missed:

• You can opt out of search indexing in settings (and this interoperates with a similar setting on Mastodon, and possibly other apps)
• The create profile form asks for a name/pseudonym and a username, with a preview like you suggested. It does pre-fill the username field based on the name you enter, which you can then edit, maybe that feature is actually not helpful?

Yeah that's a good point, I wanted to experiment with it being part of the signup flow rather than a power-user thing hidden in settings that only a minority would look for and enable. But yeah after email confirmation may make sense.

Playing with Bonfire! Trying to see what's different from Mastodon… the UI seems to be identical!

Hello Ivan, thank you for the Welcome! Here's my #bonfilre_feedback

Nice:

• It is great to have formatting options here! Very easy to use.
• The search is great! (Most masto instances I use have search disabled)
• It is good that content warnings are carried over into quotes and replies.

To improve:

• The default "quoting" option when replying to a post seems excessive. It is always possible to follow a link to the quoted post. Also it is possible to manually quote. (Maybe this could be done by default when copying/pasting text from the post you're replying to.
• It is nice to be able to switch in between identities, but I wasn't clear on signup what input field would become what piece of data. My expectation was that my "real name" would just be used for display, but it became my "user name" and is now part of the URL. Maybe show a preview of profile and URL while editing the signup information.
• Search is cool, as mentioned above, I think many masto instances have it disabled because of privacy concerns. It would be interesting to have users or identities having the option to opt out of being indexed by the local search.
• Images + CWs and images + quotes don't seem to work.

That's all for now, really enjoying the new effort.

We're replying so much!

Let's also reply to this one then

Ah, sometimes it does. But not when loading more posts on the timelines.

Let's reply!

Yes, but I have to admit that I didn't record the exact error ... I would say that my validation code was no longer valid at the time of submission, and then I tried to re-generate one without changing the registration TOP code... Sorry I wasn't very conscientious about evaluating the error.

But finally, I found it confusing to have to create this two-factor authentication directly on the account creation form ... From an interface point of view, it might be more smooth to provide it on a second step, maybe after email confirmatinon page ?

Hi, just testin' here! Looks great!

Testin replies

A testing post