Ah I found the issue. The link you posted is https://next.lemm.ee/post/27522337 however the instance is not next.lemm.ee. The instance is lemm.ee. This is a bit challenging to handle since nothing prevents instances from being hosted on a subdomain so Summit has no idea if next.lemm.ee is the instance or lemm.ee. I'll look into how I could resolve this issue going forward.

[–] sunaurus@lemm.ee 2 points 6 months ago (1 children)

Hey! Do I understand correctly that your app is trying to fetch any /post/<id> directly from its source instance API? If so, I have a few ideas:

If you detect anything that looks like a Lemmy post URL (<host>/post/<id>), you could first try to make a request to <host>/version, and only treat the post as a Lemmy post if you get a JSON response from that endpoint where .software.name === 'lemmy'. Otherwise, open that URL in the browser.

The above will already "fix" the issue, but custom frontends on subdomains is actually quite common, so if you want to handle those links without resorting to a browser, then: in cases where <host>/version is not a Lemmy response, but <host> includes a subdomain, you could repeat the same logic from step 1 for the parent domain as well. If you detect a Lemmy API at the parent domain, then just use that to fetch the post.

[–] idunnololz@lemmy.world 2 points 6 months ago* (last edited 6 months ago)

Thank you for the suggestion! Not to worry I've already implemented a fix. It will go out in the next release.