May 11 2020
Replaced by T405, which will be more detailed
Mar 22 2020
Mar 19 2020
Mar 11 2020
Jan 7 2020
Oct 27 2019
This is why we need a versioned API
Oct 22 2019
How about making "in stack" black (and gray in dark theme ;))?
Oct 21 2019
I'm liking the original Clovis proposal. However:
Jul 8 2019
TOTP should be prioritized.
Use email over username for admin login
May 18 2019
Require 2FA/MFA on admin
May 3 2019
This plugin fixes cors issues: https://github.com/cjvnjde/google-translate-api-browser
May 1 2019
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
Apr 28 2019
Search by ID, has pictures, anonymous, author, etc.
Apr 20 2019
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.
Apr 19 2019
Apr 15 2019
Apr 12 2019
Might just use a tinymce instead, need to analyze security risks
Apr 9 2019
Could it be possible to have a JSON array for this?
Apr 3 2019
Mar 28 2019
Mar 25 2019
Mar 24 2019
Mar 20 2019
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?