Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request]: Reply to toot as a different user #1159

Open
1 task done
SimplyCorbett opened this issue Oct 12, 2024 · 2 comments
Open
1 task done

[Request]: Reply to toot as a different user #1159

SimplyCorbett opened this issue Oct 12, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@SimplyCorbett
Copy link

Describe the request

I don't know if this feature request already exists, but it would be nice if (like on mona) you can select which account is replying to the toot in question.

This is for when you have multiple accounts setup.

Implementation Details

@SimplyCorbett SimplyCorbett added the enhancement New feature or request label Oct 12, 2024
@SimplyCorbett
Copy link
Author

mona9

@GeopJr
Copy link
Owner

GeopJr commented Oct 12, 2024

It's partially duplicate of #223 (that issue is about all actions, including fav/boosts etc) which is quite a lengthy discussion but the TLDR from my side is that there are too many moving parts.

E.g. You are Person_1 and are trying to reply to Person_2 with your Person_3 account. What if Person_2 blocks Person_3? What if Person_3 has defederated with Person_2's instance? What if the Person_3 instance has a character limit of 3 and your message is 4 characters long?

This feature just expects you to fail at some point. There are other problems I described in that issue but I haven't revisited in a while.

With that said, I did somewhat do a POC around that time that was somewhat less prone to errors but it's not the same as the one you'd like

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants