ActivityPub 플러그인에 Discourse-to-Discourse 링크된 액터(linked actors) 지원을 추가하는 커밋을 방금 병합했습니다. 그러나 두 개의 다른 인스턴스에서 테스트를 해본 결과 문제가 발견되었습니다. 이들을 한데 묶어 정리하기 위해 모두 여기에 등록합니다. @angus
Discourse-to-Discourse 검증: 개인용 Discourse 인스턴스에서 meta.discourse.org의 Discourse 링크된 액터를 추가할 수 없습니다. 처음에는 "failed to verify"라는 클라이언트 오류가 발생했고, 그 후에는 타임아웃이 발생했습니다.
Discourse-to-Mastodon 검증: 개인 인스턴스에서는 이 기능이 정상적으로 작동했습니다! 그러나 meta에서는 mastodon.social에 대해 검증 단계를 넘지 못하고 다음 오류가 발생합니다: An error occurred: The access token is invalid Failed to verify client.
@pmusaraj Just as an initial measure I’ve made a PR that adds settings for the rate limiting of user api key clients (which will make this hard to test this).
Could you also just check that discourse-activity-pub:read scope is added to the allow user_api key client scopes site setting. It should be automatically, but worth checking.
This change is now live on meta. With my own self-hosted instance (also up-to-date with this change), I am getting a step further, but got this error after authorizing:
I think this means we’ve fixed this issue. This error will currently occur if you don’t already have an actor on the instance as user actors are created on demand (i.e. it’s expected, albeit the message could be improved). I think this is one case where we should create them if they don’t exist. This will do that:
I think this may be indicative of an old/destroyed OAuth app on the Mastodon side of things. Just a note that in my own tests with mastodon.social (on production instances), I was able to verify without issue. I’ve raised a PR to address this potential cause of the issue:
@pmusaraj Thanks for the merge. Just a note that I was just able to successfully authorize my Mastodon account on mastodon.social here on meta, so it looks like that PR has fixed it, but let me know if you have any more issues.
that last PR fixes Discourse-to-Discourse authorization on my self-hosted instance, thanks!