Clicking here and changing instance to .world so I can answer to it, takes too long
I don’t use summit, but why do you change instance? You can reply to a message using any instance that’s federated with it, you don’t need to use the same instance as the post. You only need one lemmy account, not one on each instance.
I’m not sure why the app does this, but instead of just taking you to a post normally when clicking a link, it does this
And if you want to interact with the post in any way, you have to click that button
I would argue this is the normal behavior. The “abnormal behavior” would be to look up the same exact post on your current instance and then redirect to that post instead without the user knowing. However this is a case where the “abnormal behavior” likely results in a better UX. It’s like when Apple had to make their music shuffle algorithm less random so that it was perceived to be more random.
The post is displayed on the post’s Instance, I have to switch to mine
I have noticed this too in recent versions. I don’t remember the exact point it changed unfortunately, but it used to be almost instant and I am now seeing very long load times after clicking “view in my instance”. I thought it was just something with my home instance.
I see the same thing loading messages, etc. I’d assumed the instance was slow, but maybe not.
This isn’t a new thing. Essentially every “object” has an id and there is a translation API built into Lemmy that allows you to look up “an object” associated with an id on the current instance. The app uses this API to let you see a post from any instance. The logic has been the same for a very long time.
This is one quirk of Summit that I’ve never gotten used to, is there any reason it needs to stay or be default behavior? On Sync (rip) I think it would just show posts from other instances from my own insance even if following links directly to a post on its instance.
There’s a lot of UX annoyances that come from switching instances while viewing posts (can’t cast votes or comment, have to wait to switch instances), so it would be really nice if there were some way to make this an optional behavior or remove it entirely.
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.
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.
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.
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.
