I suppose that makes sense, it would be nice if it wasn’t the default though since it makes it harder to interact with the post via comments or voting.
Maybe if it could default to viewing from your instance, but have an option under a context menu to open the post in its own instance? There are flaws in this approach though, and there are lots of other ways.
even if your instance is defederated from the instance of the linked post you can still view it
Should that not be reserved only for when a local version of the post can’t be found? It seems a bit silly to ask the user every time, when viewing the local version on the user’s home instance is almost always the desired behavour.
@idunnololz@lemmy.world, would you be able to shed some light on why this behaviour is coded the way it is? I feel like I might be missing something.
Back when Summit was first developed, federation could be hit or miss and pretty much everyone got a different experience of a post depending on which instance you viewed the post on. I’m not sure how true that is these days. So I made the decision that preserves the intended experience of link.
As an extreme example, let’s say someone asked what are some good recipes for beans and I knew of a post on !asklemmy@lemmy.world with some good answers so I link to the post. Now you open it on your instance but because of special instance settings and possible federation issues you only see bad bean recipes. So then you come back and yell at me for giving you bad recipes, but when I view the post on my instance I see good recipes only.
So as a compromise Summit, by default, shows the post as it is seen by the person who posted the link and optionally allows you to view the same post on your instance, while making sure the user knew what was happening.
I think it makes sense. It would be nice to have a setting to toggle it so you could have “view in my home instance” as default behaviour if you wanted, but it’s not the end of the world.
I think the idea might be that even if your instance is defederated from the instance of the linked post you can still view it.
I suppose that makes sense, it would be nice if it wasn’t the default though since it makes it harder to interact with the post via comments or voting.
Maybe if it could default to viewing from your instance, but have an option under a context menu to open the post in its own instance? There are flaws in this approach though, and there are lots of other ways.
Should that not be reserved only for when a local version of the post can’t be found? It seems a bit silly to ask the user every time, when viewing the local version on the user’s home instance is almost always the desired behavour.
@idunnololz@lemmy.world, would you be able to shed some light on why this behaviour is coded the way it is? I feel like I might be missing something.
Back when Summit was first developed, federation could be hit or miss and pretty much everyone got a different experience of a post depending on which instance you viewed the post on. I’m not sure how true that is these days. So I made the decision that preserves the intended experience of link.
As an extreme example, let’s say someone asked what are some good recipes for beans and I knew of a post on !asklemmy@lemmy.world with some good answers so I link to the post. Now you open it on your instance but because of special instance settings and possible federation issues you only see bad bean recipes. So then you come back and yell at me for giving you bad recipes, but when I view the post on my instance I see good recipes only.
So as a compromise Summit, by default, shows the post as it is seen by the person who posted the link and optionally allows you to view the same post on your instance, while making sure the user knew what was happening.
That was the logic behind this decision.
I think it makes sense. It would be nice to have a setting to toggle it so you could have “view in my home instance” as default behaviour if you wanted, but it’s not the end of the world.