| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Lint | Tusooa Zhu | 2023-01-20 |
| | | |||
| * | Add confirmation for following | Tusooa Zhu | 2023-01-20 |
| | | |||
| * | Merge branch 'fixes_for_deactivated_profile' into 'develop' | HJ | 2022-01-19 |
| |\ | | | | | | | | | Improve the user card for deactivated users See merge request pleroma/pleroma-fe!1417 | ||
| | * | Improve the user card for deactivated users | Ilja | 2022-01-19 |
| | | | |||
| * | | Allow canceling a follow request | Ilja | 2021-12-12 |
| |/ | | | | | | | | When a follow request is sent, but not (yet) accepted, the behaviour is now to cancel the request instead of re sending. The reason is double * You couldn't cancel a follow request if you change your mind and the request wasn't answered yet * Instances don't always correctly process a new follow request when the following is already happening. If something went wrong (e;g. the target server thinks you're following, but your instance thinks you're not yet), it's better to first sent an unfollow. This is the behaviour that Mastodon and most probably most other clients have. Therefore this flow is more tested and expected by other instances. | ||
| * | fix follow | Shpuld Shpuldson | 2020-04-22 |
| | | |||
| * | make relationships separate from users | Shpuld Shpuldson | 2020-04-21 |
| | | |||
| * | updated FollowCard component | Maksim Pechnikov | 2019-10-17 |
| | | |||
| * | change icon | Maksim Pechnikov | 2019-10-08 |
| | | |||
| * | updated user_card | Maksim Pechnikov | 2019-10-08 |
| | | |||
| * | Revert "added acccount_actions component" | Maksim Pechnikov | 2019-10-08 |
| | | | | | This reverts commit 188b6f56ed2f983d8f0fba4dc8f7327ebbee321d. | ||
| * | added acccount_actions component | Maksim Pechnikov | 2019-09-30 |
