Add Conversation/Thread Muting

Adds Mute/Unmute conversation options in status ellipsis menu

added 41 commits

• 7ed9d17c...e9b45257 - 40 commits from branch develop
• 3370dd80 - Merge branch 'develop' into 'feat/conversation-muting'

Compare with previous version

1. Backend (at least my version) is increadibly wonky, doesn't always report posts as muted
2. We update muted for only one status, but probably should go over entire conversation, but we need conversationId, don't remember if we still have that or it's KIA during MastoAPI wars

I noticed the BE issue as well, I told people about it on IRC but not sure if there's an issue. I don't think the 2. is something we should decide, it gives you more granular control if it doesn't nuke the entire conversation but just one branch, I think it's up to BE to decide how it works when user mutes one status.

We update muted for only one status, but probably should go over entire conversation, but we need conversationId, don't remember if we still have that or it's KIA during MastoAPI wars

you do have pleroma.conversation_id https://docs-develop.pleroma.social/differences_in_mastoapi_responses.html#statuses

2. is something we should decide, it gives you more granular control if it doesn't nuke the entire conversation but just one branch, I think it's up to BE to decide how it works when user mutes one status.

The current implementation just mutes the entire conversation if one status is muted.

Backend (at least my version) is increadibly wonky, doesn't always report posts as muted

Not sure why it's happening, considering it's queried from the db every time, but we could fix it to be consistent when muting at least.

added 37 commits

• 3370dd80...4827e4d9 - 36 commits from branch develop
• d3f6b581 - Merge branch 'develop' into 'feat/conversation-muting'

Compare with previous version

merged

mentioned in commit 92380652

mentioned in commit 1f63431e

mentioned in merge request !907 (closed)