this post was submitted on 11 Mar 2025
1 points (100.0% liked)

ActivityPub

0 readers
3 users here now

Focused discussion related to ActivityPub integration in NodeBB


This is a forum category containing topical discussion. You can start new discussions by mentioning this category.

founded 9 months ago
1
submitted 5 days ago* (last edited 5 days ago) by [email protected] to c/[email protected]
 

I followed [email protected] from my account on this instance, and another nodebb instance. This one shows Following, the other shows pending! Follows dont need acceptance do they, why the difference? 1000042774.jpg 1000042776.jpg

Also, why a settings icon only on my nodebb instance?!

top 5 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 4 days ago

Yea, odd, I made a second account on mysite and that follows and unfollows normally. So its a mystery why my first Admin account is doing it differently. Maybe one day we will figure out whats altering the behaviour

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (1 children)

Thanks, I tried unfollowing and following again, but its always the same. On this instance it says following and my one it says 'cancel follow request' although the pop up box said 'You are now follwing etc'

Edit: I tried from an non admin account on my instance, that does the normal follow/unfollow, like here.

So wheres the code that makes it different for admins, as that doesnt make any sense to have it different?

[–] [email protected] 1 points 5 days ago

@eeeee there's no difference in follows if you're admin vs non-admin.

[–] [email protected] 1 points 5 days ago

@eeeee follows do need to be accepted, although it's configurable. Most software auto accepts, but delays in messaging mean sometimes the requests or responses get lost.

Cancel that follow and try again, and it might be accepted.

You see the settings cog because you're an admin on your instance.

[–] [email protected] 1 points 5 days ago

I've been noticing a lot more hanging follow requests with/from Lemmy since upgrading to 4.1. It's not consistent, though -- some Lemmy sites continue to process them fine, and some don't. I initially thought it had to do with the Lemmy version, but I'm seeing both behaviours from 0.19.9, so... *shrug*.