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
Open posts and profiles in your own instance even when opening a new page #19967
Comments
Agree on all cases except "copy link to post" should probably copy a link to the canonical version of the post. The idea is presumably to get something you can share with others. |
We could have both if they were to add a new option alongside that called "copy link to original post" or something. |
#19652 is possibly related or a duplicate |
It seems this has been implemented in v4.0.0. |
Pitch
Usually when you normally click on a post it opens it within your own instance even if it's from an other instance. What I mean by this is that I'm from mstdn.social and when I click on Eugen's latest post from mastodon.social it's going to open it in "https://mstdn.social/@Gargron@mastodon.social/109301198014267634" instead of "https://mastodon.social/@Gargron/109300967725833789".
But when I want to open the post in a new window by clicking on the time stamp with the middle mouse button or by right-click with "open link in new window" it's not going to open it in my own instance mstdn.social. It's going open it in mastodon.social.
Same goes if want to open their profile in a new window.
Would it be possible to add the option within the preferences to change every link on every post so they will going to open in your own instance?
Motivation
It's much easier to navigate posts within your own instance. You can also immediately interact with posts and users within your own instance and follow users with a single click. However when you go onto other instances you have to go through multiple steps before you can interact with posts and users there which makes it clunky and off-putting.
The text was updated successfully, but these errors were encountered: