Stop using `user.info`
- It's not much more convenient than just having separate fields
- Fields in it are harder to index due to them being jsonb, so even using an indexed boolean from there screws with the query plans. Also things like mutes and blocks not being proper relations slows things down.
- Migrations are easier and faster to perform when they are not inside of jsonb
- You can't wipe everything with unsafe use of
jsonb_set
Thus, I think we should stop using user.info for new fields, and migrate old fields out of it over time.
Edited by rinpatch