Red Rozenglass on Nostr: The Real Grunfink Hi ^-^ can't imagine what is causing the spurious unfollow I have a ...
The Real Grunfink (nprofile…73zh)
Hi ^-^
can't imagine what is causing the spurious unfollow
I have a few more notification objects of such cases, I can give you access to them too, if you wish. They differ in some ways, including the 'to' field, but all seem to share not having an embedded msg.object (but have a link there instead), and all don't include my user in the 'to' field (but normal good unfollows do).
your patch improves the process logic, so I'll merge it.
Go ahead, and thank you for your work :)
The patch seems to have saved me from one unfollow so far, I think, where utype and id both were null, at which case the previous code would have tried to delete the follower, but the new code stops instead. I still need to figure out how to set my followers as followers again on my side at some point, or be a nuisance and ask them to unfollow then follow me one by one :p
Hi ^-^
can't imagine what is causing the spurious unfollow
I have a few more notification objects of such cases, I can give you access to them too, if you wish. They differ in some ways, including the 'to' field, but all seem to share not having an embedded msg.object (but have a link there instead), and all don't include my user in the 'to' field (but normal good unfollows do).
your patch improves the process logic, so I'll merge it.
Go ahead, and thank you for your work :)
The patch seems to have saved me from one unfollow so far, I think, where utype and id both were null, at which case the previous code would have tried to delete the follower, but the new code stops instead. I still need to figure out how to set my followers as followers again on my side at some point, or be a nuisance and ask them to unfollow then follow me one by one :p