search for [domain]/s/[id] when opening individual status?

[snarfed]

Hi @cheeaun et al! First off, thank you for building and maintaining Phanpy. It's awesome!

I'm experimenting with adding Mastodon API support to a non-Mastodon service (Bridgy Fed), and I'm using Phanpy to test it. That's going well, except I'm seeing an odd behavior when opening individual statuses.

When I log into Phanpy with a normal Mastodon account, and then I click on a status, Phanpy loads /api/v1/statuses/[id]/context, then renders the status in a sidebar. However, when I log in with my service and click on a status, Phanpy loads /api/v2/search?q=fed.brid.gy/s/[id]&limit=1&resolve=true instead, shows the interstitial page below, and hangs.

One difference is that my status ids aren't integers, they're URLs. Does Phanpy handle integer and non-integer ids differently? Mastodon's docs say id doesn't have to be a number, but I know in practice it is on Mastodon servers.

I see this in Phanpy's source, which could be what's generating this search query format?

phanpy/src/utils/get-instance-status-url.js

Line 35 in 57870e3

return `/${instance}/s/${id}`;

Thanks in advance! cc @quillmatiq

[snarfed]

Looks like URL ids are indeed the cause here. I changed account ids to URLs and got the same problem with them:

[cheeaun]

@snarfed I need more details on "when I log in with my service" part. You mean Bridgy Fed? How does that work? 🤔

[snarfed]

It's not a launched feature, just an experiment right now. Lets you use a Mastodon API client with a Bluesky account or web site.

Here are some example statuses (with accounts) that it returns. Note the URI ids.

{
  "id": "at://did:plc:thic7s3b4yedkd4zimlmshrq/app.bsky.feed.post/3mrt55r7af22j",
  "uri": "https://bsky.brid.gy/convert/ap/at://did:plc:thic7s3b4yedkd4zimlmshrq/app.bsky.feed.post/3mrt55r7af22j",
  "url": "https://bsky.app/profile/did:plc:thic7s3b4yedkd4zimlmshrq/post/3mrt55r7af22j",
  "account": {
    "id": "did:plc:thic7s3b4yedkd4zimlmshrq",
    "uri": "https://bsky.brid.gy/ap/did:plc:thic7s3b4yedkd4zimlmshrq",
    "username": "2dogphish.bsky.social",
    "acct": "2dogphish.bsky.social@bsky.brid.gy",
    "display_name": "2dogphish",
    "locked": false,
    "bot": false,
    "created_at": "2024-11-10T17:58:55.962571+00:00",
    "note": "I believe in dogs.\nPaws up little monsters.\n\n#IHateItHere\u2122\ufe0f",
    "url": "https://bsky.app/profile/2dogphish.bsky.social",
    "avatar": "https://shiitake.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:thic7s3b4yedkd4zimlmshrq&cid=bafkreihw2sbi275w4nzfnjibcohgdvjtqchul5jjeeh7g55x3yahj2hmz4",
    "avatar_static": "https://shiitake.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:thic7s3b4yedkd4zimlmshrq&cid=bafkreihw2sbi275w4nzfnjibcohgdvjtqchul5jjeeh7g55x3yahj2hmz4",
    "header": "https://shiitake.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:thic7s3b4yedkd4zimlmshrq&cid=bafkreibk3ey2om7a6ms4doedr7ueeuva4jmyvbiqkqmuyzhw4vlkvgshdi",
    "header_static": "https://shiitake.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:thic7s3b4yedkd4zimlmshrq&cid=bafkreibk3ey2om7a6ms4doedr7ueeuva4jmyvbiqkqmuyzhw4vlkvgshdi",
    "followers_count": 0,
    "following_count": 0,
    "statuses_count": 0
  },
  "created_at": "2026-07-30T00:01:51.516Z",
  "content": "Good question! I love pre & post show music stats and pairings.",
  "visibility": "public",
  "sensitive": false,
  "spoiler_text": "",
  "in_reply_to_id": "at://did:plc:te452l4j4m7ys7ivdmg7hrie/app.bsky.feed.post/3mrt4u47i6k2b",
  "in_reply_to_account_id": null,
  "media_attachments": [],
  "mentions": [],
  "tags": [],
  "emojis": [],
  "reblogs_count": 0,
  "favourites_count": 0,
  "replies_count": 0,
  "reblog": null,
  "pinned": false
}

{
  "id": "https://tech.lgbt/users/nelson/statuses/116986757400358795",
  "uri": "https://tech.lgbt/users/nelson/statuses/116986757400358795",
  "url": "https://tech.lgbt/@nelson/116986757400358795",
  "account": {
    "id": "https://tech.lgbt/users/nelson",
    "uri": "https://tech.lgbt/users/nelson",
    "username": "nelson",
    "acct": "nelson@tech.lgbt",
    "display_name": "Nelson Minar",
    "locked": false,
    "bot": false,
    "created_at": "2022-04-26T00:00:00Z",
    "note": "<p>Full stack homosexual.</p>",
    "url": "https://tech.lgbt/@nelson",
    "avatar": "https://media.tech.lgbt/accounts/avatars/108/199/162/655/756/639/original/35d12acf6d5cd404.jpg",
    "avatar_static": "https://media.tech.lgbt/accounts/avatars/108/199/162/655/756/639/original/35d12acf6d5cd404.jpg",
    "header": "https://media.tech.lgbt/accounts/headers/108/199/162/655/756/639/original/bb0f57a5517d787b.jpg",
    "header_static": "https://media.tech.lgbt/accounts/headers/108/199/162/655/756/639/original/bb0f57a5517d787b.jpg",
    "followers_count": 0,
    "following_count": 0,
    "statuses_count": 0
  },
  "created_at": "2026-07-26T14:30:54Z",
  "content": "<p>This <a href=\"https://www.southernliving.com/mississippi-roast-review-6530003\" target=\"_blank\" rel=\"nofollow noopener\">Mississippi Pot Roast</a> came out great! It always does. Look, it's not fine cuisine, but it's very easy and very satisfying.</p>",
  "visibility": "public",
  "sensitive": false,
  "spoiler_text": "",
  "in_reply_to_id": "https://tech.lgbt/users/nelson/statuses/116981876151508014",
  "in_reply_to_account_id": null,
  "media_attachments": [],
  "mentions": [],
  "tags": [],
  "emojis": [],
  "reblogs_count": 0,
  "favourites_count": 0,
  "replies_count": 0,
  "reblog": null,
  "pinned": false
}

[snarfed]

I URL-encoded these ids so they don't look like URIs, and Phanpy stopped doing this. Guess I'll stick with that for now.

[cheeaun]

You're right. I did a quick check, on Phanpy's side, will need to encode the ids, else they'll be treated like actual routes by React Router.

This will need some changes 🙇‍♂️

[cheeaun]

Side issue besides Phanpy handling the URL on the browser/client side. When fetching /api/v1/statuses/[id]/context, does the id need to be URL-encoded?

So it's either https://DOMAIN/api/v1/statuses/at%3A%2F%2Fdid%3Aplc%3Athic7s3b4yedkd4zimlmshrq%2Fapp.bsky.feed.post%2F3mrt55r7af22j/context OR https://DOMAIN/api/v1/statuses/at://did:plc:thic7s3b4yedkd4zimlmshrq/app.bsky.feed.post/3mrt55r7af22j/context

I'm not able to test this but I think masto.js doesn't auto-encodeURIComponent the id so it might end up the latter. Else I'll need to add URL encoding to every id for every masto.js API call 🤪

[snarfed]

Sorry to saddle you with this! I'm switching our ids to not be URIs, so don't feel the need to do anything on my account.