Replaced by T405, which will be more detailed

This is why we need a versioned API

How about making "in stack" black (and gray in dark theme ;))?

I'm liking the original Clovis proposal. However:

TOTP should be prioritized.

Use email over username for admin login

Require 2FA/MFA on admin

This plugin fixes cors issues: https://github.com/cjvnjde/google-translate-api-browser

I'm creating a document with a lot more details on what the areas could look like, please take a look and tell me if I've done any mistakes: https://docs.google.com/document/d/1iSdB2DzvXzk8oqGnTTAFmQY9bSj9VyfuYMJeQ4oKAYk/edit?usp=drivesdk

Search by ID, has pictures, anonymous, author, etc.

@Pregenun
Sorry if it wasn't clear, what I meant was that anyone would have 2 "virtual" areas: "world" which is just everything without sorting, and "subscriptions" that would be every area the user is interested in. Because the posts that are very popular would spread to neighbor areas, you would discover areas that are similar to the ones you know that way. By default, the user would be subscribed to the main ones, but they would slowly discover other ones.

My proposal:

Another proposal:

Might just use a tinymce instead, need to analyze security risks

In T194#3313, @WyldBot wrote:

We should change post.text to post.text[] to allow for easy parsing client side

Okay. I thought about the other because it's not breaking (and more detailed)

I'd like to keep this one, because it removes unneeded nesting in serializers and therefore having data in multiple places

Wait, is this for the Client (web) or app?

Why would we restrict editing?

In T256#4663, @CLOVIS wrote:

This could be replaced by T290, which gets the same results in a non-breaking way.