sounds like a skill issue to me, get good n00b
okay, okay.
I don't know how things are supposed to work when you are hosting a masto instance (is yours masto? or something else?) on the same domain name as another website.
The search finds you because it's using the mastodon dot social search API, but then when it tries to hit /api/v1/ on saagarja dot com, it's getting 404s; code is here:
@saagar @ricci the search endpoint isn’t the problem, you need for resolve the handle using webfinger to find where the instance actually is
if you want to work with software that doesn’t implement the mastodon api (pleroma does, misskey/etc. don’t), you need to use the activitypub outbox endpoint to fetch the posts
@shadowfacts saagarjha.com doesn't do webfinger in the way that the Mastodon documents suggest: https://docs.joinmastodon.org/admin/config/#local_domain
... they suggest doing a 301 redirect on the webfinger URL to the domain where the instance actually lives. I've just implemented support for this in mastodon.academy, but saagarjha.com returns its webfinger response directly from the saagarjha.com domain without a redirect. While it does return some useful URLs at federated.saagarjha.com, none of them are specifically to the Mastodon API. I *could* guess the correct domain from this, but I would have it do it for *everyone* and I'm worried that might break other instances.
Any suggestions for what the right thing to do in this case is?