When tapping on a URL in the post content that points towards a linked post, Summit leads to Page Not Found.
Post to test here. Tapping on the link roadmap for lemmy-ui-next in the post leads to Page Not Found.
Thanks for reporting this. I’ll look into the issue later today.
Ah I found the issue. The link you posted is
https://next.lemm.ee/post/27522337however the instance is notnext.lemm.ee. The instance islemm.ee. This is a bit challenging to handle since nothing prevents instances from being hosted on a subdomain so Summit has no idea ifnext.lemm.eeis the instance orlemm.ee. I’ll look into how I could resolve this issue going forward.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>/versionis 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.
Thank you for the suggestion! Not to worry I’ve already implemented a fix. It will go out in the next release.
- If you detect anything that looks like a Lemmy post URL (
