Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Still can't follow from Mastodon #3280

Open
eishiya opened this issue Feb 7, 2024 · 9 comments
Open

Still can't follow from Mastodon #3280

eishiya opened this issue Feb 7, 2024 · 9 comments
Labels
bug Something isn't working

Comments

@eishiya
Copy link

eishiya commented Feb 7, 2024

I am still experiencing the same problem as #2545 and #2734: When I attempt to follow my Bookwyrm account from my Mastodon account, Mastodon thinks the follow request has not yet been approved, while no follow request appears on Bookwyrm. I have "manually approve followers" disabled. I tried waiting for about 50 minutes, nothing happened.

To reproduce
Try to follow https://books.theunseen.city/user/eishiya from mastodon.ART
On Mastodon, the "Follow" button turns into a "Cancel Follow" button, which usually appears when a follow request has been sent.
On Bookwyrm, no follow request appears, and the follower list is not updated - the follow seems to have completely vaporised.

Expectation
The follow goes through automatically (or, if the account has "manually approve followers" enabled, a follow request appears), and the follower list on Bookwyrm is updated.

Instance
Bookwyrm: https://books.theunseen.city, which is running version 0.6.6
Mastodon: https://mastodon.art, v4.2.5

Additional context
Mastodon.ART uses authorized fetch, perhaps it's related to that?

@eishiya eishiya added the bug Something isn't working label Feb 7, 2024
@skobkin
Copy link
Contributor

skobkin commented Feb 8, 2024

Did you try the same from another instance?

Mastodon.art is somewhat famous for their defederation with almost everything, so it's not impossible that there's no federation with your bookwyrm instance or your account could be suspended there.

I've tried to follow your account from mine on lor.sh. No problems there.

Also it could be useful to get in contact with your Bookwyrm instance admin and ask them for logs if you know the precise time when you tried to follow. If there was something strange like errors they can see that. This data could be very useful if it's really a Bookwyrm problem.

@eishiya
Copy link
Author

eishiya commented Feb 8, 2024

I do not have other Mastodon or Bookwyrm account to try with. Thanks for checking for me, I do see your follow as normal, so presumably this is something about .ART's config causing problems.

My Bookwyrm instance is not blocked or limited by .ART, and the account is not suspended there, it shows up normally. The authorized fetch thing is the only thing I can think of, and it's .ART's admin's theory as well: https://mastodon.art/@welshpixie/111891429205948907
Another user in that same thread, who is on a different Mastodon instance, mentioned having this issue and that following from Bookwyrm first helped. I tried to test this, but looking up my Mastodon account on Bookwyrm pops up a "server error" message consistently (looking up accounts on other instances seems fine). Perhaps the Bookwyrm instance is trying to fetch data from .ART when I look up my account, and failing.

I will attempt to contact my Bookwyrm instance admin about this.

@fofwisdom
Copy link
Contributor

image

image

@eishiya I sent you a request from each of your BookWyrm and Mastodon accounts.

Now, if you could take a screenshot showing only one of the requests, it would be easier for others to understand.

@eishiya
Copy link
Author

eishiya commented Feb 10, 2024

I don't understand what you mean by "sent you as request from each of your BookWyrm and Mastodon accounts"? Do you mean you followed from your BookWyrm and Mastodon accounts? Because I do see two new follows (not follow requests), are these you?
image

One of these is from Mastodon, one appears to be your BookWyrm. The Mastodon one is from mastodon.social, which has been shown to work fine with BookWyrm in the past, and does not use authorized_fetch.

The fact they show up as follow requests for you even though they went through as normal is itself an issue though, I think. Probably a separate one from mine, though.

The Mastodon account does not appear on my Followers list, but I don't know whether that's due to a bug or if the account unfollowed:
image

@fofwisdom
Copy link
Contributor

fofwisdom commented Feb 10, 2024

Accounts that followed you.

image

image

Both accounts are marked as awaiting your approval.

"Manually approve followers" feature of BookWyrm doesn't seem to be working properly. I don't use this feature, so someone else should probably take a look at it.

@eishiya
Copy link
Author

eishiya commented Feb 10, 2024

I have "manually approve followers" turned OFF, so the fact that even on BookWyrm you're still seeing it as a follow request is definitely strange. It's just a regular follow on my end.

I see no follow or follow request from your Mastodon account on netsphere.one, so I guess that answers your initial request :D

@skobkin
Copy link
Contributor

skobkin commented Feb 10, 2024

These "Follow requests" when follow approval is not required on the receiving side are reminding me about Mastodon->Pixelfed follow problem which one of our instance users experiences.

@msub2
Copy link

msub2 commented Mar 14, 2024

As this affects my instance I definitely want to get this figured out. I'm going to spin up a test Mastodon instance with authorized fetch on so I can troubleshoot on both ends, hopefully that'll shed some light on this.

@hughrun
Copy link
Contributor

hughrun commented Mar 24, 2024

This is extremely likely to be related to "authorized fetch"/"secure mode". Would love to know what you find, @msub2 as we keep thinking we've fixed this and then it pops up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants