Wrong API endpoint #3

Hello, I want to report that you are using the incorrect API endpoint for calls to the Bluesky AppView.

For example, in cli/src/utils.rs, at line 18, you call https://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle={handle}, but it should be https://api.bsky.app/xrpc/com.atproto.identity.resolveHandle?handle={handle}

The current endpoint is known to be problematic with some users (myself included): it fails to resolve the handle, whereas the correct one works perfectly. You can see it on: ttps://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle=massive.box (fails) https://api.bsky.app/xrpc/com.atproto.identity.resolveHandle?handle=massive.box (works) This makes it impossible for me, as well as other affected users, to create URLs.

You can see the correct endpoints and their differences here: https://docs.bsky.app/docs/advanced-guides/api-directory Further discussion about the topic: https://bsky.app/profile/sergio.bsky.col.social/post/3lcbzhxke3s2b

Sorry, I've messed up the markdown and it seems editing issues isn't supported yet. Let me try again:

Hello,
I want to report that you are using the incorrect API endpoint for calls to the Bluesky AppView.

The current endpoint is known to be problematic with some users (myself included): it fails to resolve the handle, whereas the correct one works perfectly. You can see it on:
ttps://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle=massive.box (fails)
https://api.bsky.app/xrpc/com.atproto.identity.resolveHandle?handle=massive.box (works)
This makes it impossible for me, as well as other affected users, to create URLs.

You can see the correct endpoints and their differences here:
https://docs.bsky.app/docs/advanced-guides/api-directory
Further discussion about the topic:
https://bsky.app/profile/sergio.bsky.col.social/post/3lcbzhxke3s2b