Closed azulika closed 7 hours ago
It seems to be confusing two different problems.
Client
usually use your PDS (*.host.bsky.network
) API. This can only be obtained from the repo in that PDS.
On the other hand, bsky.network
refers to the relay. I was able to get all the repo until recently, but now it seems impossible.
Currently, the relay is in a mess with the upgrade process, so it may be a related (and possibly permanent) impact. (ref. #3036)
In general, if you want to get a repo, it is recommended to getRepo for the PDS address obtained by ID resolution.
I see, didn't know about the upgrade. Thanks!
Describe the bug
Trying to get a repo of other accounts than myself via com.atproto.sync.getRepo
To Reproduce
Steps to reproduce the behavior:
either directly try to access
https://bsky.network/xrpc/com.atproto.sync.getRepo?did=xxx
or run a code something like thisThe code results in:
As for https://bsky.network/xrpc/com.atproto.sync.getRepo?did=xxx, it results in:
Expected behavior
Other's repos can be downloaded.
Details
Additional context It works fine when I try to get my own account's repo through the same method(bluesky_client.com.atproto.sync.get_repo with authentication). Getting other's repo also worked when I tried it about a month ago, but now the exact same code suddenly stopped working. What happened? Is bluesky now restricting users from getting other people's repos?