Pleroma 2.0 tracking bug
This a tracking bug for Pleroma 2.0. The scheduled date is to be discussed in this issue, but I think it should be early February.
Things needed:
BE:
-
Integrated captcha, on by default (pleroma#1405 (closed) and pleroma#1017 (closed)) -
Frontend bundles removal (pleroma#1390) -
Ratelimiter on by default again (pleroma#1380 (closed)) -
Move activity (pleroma#1316 (closed)) -
Remove the remaining twitterapi endpoints (only register_user and password_reset remain) -
Groups (would be very nice to have, though I am not sure there will be something allowing us to give capabilities to use a follower collection by the time we need to release) (#14)dropped -
Support filtering on the backend for mastoapi filters (pleroma#1392 (closed))next release -
Figure out whether we should proceed with pleroma!1865 (closed) -
Emoji reactions (pleroma!1662 (merged)) -
Turn blocks & mutes into proper relations (pleroma#1335 (closed)) -
Fix group reports performance (pleroma!2220 (closed))requires complete refactor of the API endpoint -
Merge GUN adapter support (pleroma!1861 (merged))next release -
Improve Postgres performance (pleroma!2238 (merged))
FE:
-
MastoAPI lists (pleroma-fe#229 (closed))dropped -
MastoAPI filters (pleroma-fe#677)next release -
MastoAPI streaming (pleroma-fe#708 (closed)) -
Separate behaviour controls for user/thread mutes (pleroma-fe#658)next release -
Emoji reactions (pleroma-fe#709 (closed)) -
Status rendering performance (pleroma-fe!1066 (merged)) -
Fix broken user cards (pleroma-fe#777 (closed)) -
Bundle new FE with PleromaBE (pleroma!2255 (merged))
(I am well aware that there isn't much development workforce behind pleroma-fe, so feel free to drop items from this list)
AdminFE:
-
Working in-database config we can enable by default -
Final AdminFE build for 2.0
Feel free to add items to the list if you think I missed something.