Can't follow @bsky.brid.gy@bsky.brid.gy from my misskey instance #1093
Comments
|
I just tried clicking the follow button from the misskey.io account, but the same thing happened. |
|
Hmm! Sorry for the trouble. I know we have at least some Misskey accounts using the bridge successfully. If you're ok with posting them, what are the two accounts that you tried from here? |
|
These are accounts who tried it. https://misskey.vermilion3.xyz/@gimlet_202312 |
|
Ah, looks like you're getting caught by the spam filters. Right now, Bridgy Fed requires a profile picture and display name that's different from your username. https://fed.brid.gy/docs#fediverse-cant-find |
I don't understand what you mean by "a profile picture and display name that's different from your username". At least on my first account, my profile picture is different from the default one, and my display name is different from my username. How can I change it? |
|
https://misskey.io/@gimlet_202312 |
|
Interesting. Looking at Bridgy Fed's logs for the last two weeks, it's never received a Looking at the Charts tab of https://misskey.vermilion3.xyz/instance-info/bsky.brid.gy , its requests to Bridgy Fed are failing too. |
Looks like you're up and running! https://bsky.app/profile/gimlet-202312.misskey.io.ap.brid.gy . You can unfollow and refollow @bsky.brid.gy@bsky.brid.gy to get it to accept your follow, follow you back, and start bridging posts. |
|
That's the instance that isn't working with Bridgy Fed, as I described above. Try from misskey.io. |
|
|
|
Bridgy Fed sent the {
"id": "https://fed.brid.gy/r/bsky.brid.gy/followers#accept-https://misskey.io/follows/9txg0s7ppz2y0dry",
"actor": "https://bsky.brid.gy/bsky.brid.gy",
"@context": "https://www.w3.org/ns/activitystreams",
"type": "Accept",
"object": {
"id": "https://misskey.io/follows/9txg0s7ppz2y0dry",
"actor": "https://misskey.io/users/9qdu744o1onc0cue",
"url": "https://misskey.io/users/9qdu744o1onc0cue#followed-bsky.brid.gy",
"type": "Follow",
"object": "https://bsky.brid.gy/bsky.brid.gy",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
]
},
"to": [
"https://www.w3.org/ns/activitystreams#Public"
]
} |
|
|
Definitely not wrong! You just need to configure it to not return 403 errors to Bridgy Fed's (and I assume other fediverse instances') requests. |
I don't have it set up to return a 403 and I can follow other Fediverse accounts. |
|
I don't know what to tell you. https://misskey.vermilion3.xyz/instance-info/bsky.brid.gy shows that your instance's requests to Bridgy Fed are all failing, and Bridgy Fed's requests to your instance all fail with HTTP 403 errors that look like they're served by Cloudflare. |
|
I made issue in https://github.com/misskey-dev/misskey/. |
|
I output the log of misskey.vermilion3.xyz. Does this give you any idea? error_logs_misskey.log |
|
There was a record of a Cloudflare WAF event. It seems that the bot fight mode was activated. |
|
Ah, good catch! Makes sense. I don't know what you can do, I've never used Cloudflare's WAF. |
So nothing we can do. If I turn off the firewall, my instance will quickly become a victim of malicious bots. I'm sure there are other instances that use Cloudflare, but I wonder if they are all like this. |
|
Regarding the issue where I can't follow on misskey.io, I received a reply to an issue I created in the misskey repository. It seems to be related to misskey-dev/misskey#9036. |
Is there anything you can do? I'd be in trouble if I couldn't use Cloudflare on my instance. |
|
I don't know of anything I can do on my end. Sounds like Bot Fight mode specifically is the problem, right? You're sure you can't disable it? https://mastodon.social/@andryou/108218913202599968 |
The issue isn't whether I can actually turn it off, it's that if I do, my instance open itself up to attacks from nasty bots other than yours. |
|
I'm pretty sure you'd realistically have to turn off Bot Fight Mode for the entire ActivityPub API for your instance to function correctly (also with regard to other legitimate servers), or at least have to make it use very loose limits. Automated/"bot" fetches are a pretty central part of the protocol. Generally speaking, services like this are incompatible with anti-bot measures built for general web pages. |
|
I ended up disabling bot fight mode. I got a follow back, but it's still processing. |
|
It should be working now. The follow being confirmed isn't actually necessary for it to fully function, I think. |
|
Glad this is working! Tentatively closing. Feel free to reopen if necessary! |
|
@excelsior091224 oh no, it looks like you blocked @bsky.brid.gy@bsky.brid.gy from that account at 08:54:45 UTC today, which disabled its bridging and deleted its bridged Bluesky account https://bsky.app/profile/gimlet-202312.misskey.vermilion3.xyz.ap.brid.gy . I see that you later un-blocked it, but right now Bluesky doesn't support undeleting accounts. https://fed.brid.gy/docs#opt-out I'm sorry. Hopefully they'll add that support soon! |
|
@snarfed
Ultimately, that's your problem. Can't you do something about it? |
|
For context: I wonder if it got confused because Bridgy also answers to Though, @snarfed please check which Line 1092 in 2ed8ba2 By the way, Line 550 in 2ed8ba2 Edit: As a side note, I keep misreading the public keys because I check the start instead of the end for identity. |
Just to clarify, while the issue with the |
|
Sorry this still isn't working for your Misskey instance @excelsior091224! We got it working with at least some other Misskey instances, but it sounds like it's not fully fixed. I'm happy to reopen. And thank you for the details on Misskey's hostname check! That definitely is a problem. However, nothing in ActivityPub requires activity ids and actor ids to be on the same host. If Misskey requires it, that's a non-standard requirement on Misskey's part that most other fediverse software doesn't share. I can look into moving these specific follow ids onto bsky.brid.gy to match the bot actor. Bridgy Fed generates many different kinds of activities, though, and it has logic based on those activities' hosts (subdomains). I doubt I'd be able to move every activity's host to match its actor. |
|
Huh, actually, @excelsior091224 the bot's follow activity ids are already on bsky.brid.gy after all. Here's an example that we delivered at 2024-08-19 17:05:35 UTC to https://misskey.vermilion3.xyz/users/9mvya5mf7tue0001/inbox , which returned HTTP 202: {
"@context": "https://www.w3.org/ns/activitystreams",
"type": "Follow",
"id": "https://bsky.brid.gy/r/https://bsky.brid.gy/#follow-back-https://misskey.vermilion3.xyz/users/9mvya5mf7tue0001-2024-08-20T00:05:35.434465+00:00",
"actor": "https://bsky.brid.gy/bsky.brid.gy",
"object": "https://misskey.vermilion3.xyz/users/9mvya5mf7tue0001",
"to": ["https://www.w3.org/ns/activitystreams#Public"]
} |
So what's this? |
|
Understood. I don't know why those aren't working yet, I'm sorry. Thank you for the information so far. And I'm sorry you can't currently re-enable fediverse =>Bluesky bridging after you disable it! Hopefully it won't be forever, the Bluesky team knows about this and will hopefully fix it eventually, but I don't know when yet. |
The problem in this case is the Accept activity I believe, not Follow. |
|
Ah! Good point, thank you. |
|
Oh also @qazmlp re your "@context": [
"https://www.w3.org/ns/activitystreams",
"https://w3id.org/security/v1"
],
"publicKey": {
"id": "https://bsky.brid.gy/bsky.brid.gy#key",
"owner": "https://bsky.brid.gy/bsky.brid.gy",
"publicKeyPem": "-----BEGIN PUBLIC KEY-----\n...\n-----END PUBLIC KEY-----"
},And yeah BF probably doesn't perfectly implement all of https://swicg.github.io/activitypub-http-signature/#how-to-obtain-a-signature-s-public-key (which I wrote 😂). I'm comfortable that it's as good or better than average on the fediverse, but it could always be improved! |
|
Thanks! I think I had the error message a bit backwards in my mind when I asked, but this is still helping me understand the protocol a little better. |
|
I can confirm my own follow never went through either, even after our server admin lifted the limit on the bridge, but the bridge was able to follow me. It's confusing but my account is being bridged fine. |
|
In addition, I recently made my blog compatible with Bridgy Fed, but the following from the misskey instance (misskey.vermilion3.xyz, misskey.io) is still in process and is not completed. I think this is the same problem as this one. This is a real problem because it will not appear on the timeline until the following is completed. Please look into it. my instance(misskey.vermilion3.xyz) |
|
The main outstanding thing to do here is move |
|
Recent example from send task 07286805063984658111: {
"@context": "https://www.w3.org/ns/activitystreams",
"id": "https://fed.brid.gy/r/bsky.brid.gy/followers#accept-https://capivarinha.club/follows/9zpti9k9fhub1bzu",
"actor": "https://bsky.brid.gy/bsky.brid.gy",
"type": "Accept",
"object": {
"actor": "https://capivarinha.club/users/9wo76ceniz9c0001",
"id": "https://capivarinha.club/follows/9zpti9k9fhub1bzu",
"url": "https://capivarinha.club/users/9wo76ceniz9c0001#followed-bsky.brid.gy",
"type": "Follow",
"object": "https://bsky.brid.gy/bsky.brid.gy",
"to": ["https://www.w3.org/ns/activitystreams#Public"]
},
"to": ["https://www.w3.org/ns/activitystreams#Public"]
} |
|
OK, Accept ids are now on the same domain as their actor. Anyone here on Misskey/Sharkey, feel free to try following @bsky.brid.gy, or any bridged Bluesky user, and see if your follow gets accepted! |
|
ok. it seems works on misskey. |
|
Awesome, thanks for confirming! |
|
From Sharkey, can confirm after unfollowing and refollowing, it's finally out of eternal Processing 🎉 |
I tried to follow @bsky.brid.gy@bsky.brid.gy from the account of the Misskey instance I set up on my home server, but the follow remains in progress as shown in the attached image and does not complete.
When I look at logs in the Misskey container, I see the following error, but I don't understand what it means. What is the reason why I can't follow it?
Misskey version: misskey@2024.3.1(docker image latest)
nodejs: v20.10.0
The text was updated successfully, but these errors were encountered: