Separate Interacting and Browsing users
Is Your Feature Request Related to a Problem?
Currently there is a great feature for replying to posts and comments using another user.
This is great, but requires you to change it on every response, and doesn't work for up/down votes and saves.
Feature Description
It would be great if you could pin a default interaction user, so that if I up vote a post while browsing another server, it would:
- Request the post on the server for the interaction user (to federate the post)
- Do the up vote
This has an added benefit for people who run really small servers at home, in that it enables them to subscribe on a more stable server, but "own their account and interactions" locally.
Alternative Solutions
No response
Additional Context
No response
Hey @Fmstrat, this doesn't completely solve your problem, but you can change which user you're viewing a post as, which does allow you to vote/save as a different user. Then if you reply, it'll be that same user as well.
https://github.com/user-attachments/assets/8cf98370-eafb-4dda-9fc9-ba4d8f7d6c30
@micahmo Interesting.. What does this actually do?
For instance:
- On Account 1
- Default feed of Subscriptions (as Account 1, served up from Account 1s server)
- View post (served up from Account 1s server)
- Switch to Account 2
- Post refreshes (served up from ???)
- Go back to feed
- It is now All Posts (as ???, served up from ???)
I'm guessing it switches the server its viewing on as well, since I get a Post not available on server in some cases.
To solve that, executing an API call to search for the URL of the original post before loading in the UI would federate just that post. Which would also be the method I mention above.
This seems pretty close to what I describe, but still dofferent enough it doesn't solve the issue (as you mention). Thanks!
You are right that it fetches the post from the second account's server, which is why it's not always available. In fact, for all intents and purposes, it is just switching the active account that you are using in Thunder. The trick is that, when you navigate back to the feed, it switches back to the original account for you without refreshing the feed so you can pick up where you left off. (BTW, if you are seeing the feed switch from Subscriptions to All, that is a (separate) bug.)
executing an API call to search for the URL of the original post before loading in the UI would federate just that post
This is an interesting idea. When in the flow would you propose making this call? I don't think we could do it for every post for every account (that would just spam the servers). But if we did it at the time you attempt to switch accounts, it might not be federated in time for us to re-fetch and display it. And then, it might not work at all if the two servers don't federate.
Maybe it would work better for the user to have a way to request a federation? Maybe when we show the message that the post isn't available?