Thank you ~cloutier 😇.

FYI, images (avatar & cie) are back only after an operation like unfollow/follow.

~davinkevin I pulled the commit. Even if it's small code-wise, I want to recognise your contribution in testing it. Thanks!

~freamon I have updated bird.makeup with the patch. Can you confirm that it works with Lemmy now?

I have the same issue with all accounts being pulled constantly in an infinite loop.

When I work on a local instance, with only one followed account, it's checked 4 times a second in this loop.

in bird.makeup context, with thousands of accounts, it potentially makes sense… but for a single-user consumer (-ish) mode, a pause could be good for CPU/IO and rate limiting.

wdyt?

I did a change just to try it out. I don't know if there is any other implication for the insta part or other element in the code.

~cloutier The code is just a one letter change, but the code is available on GitLab

~davinkevin if you have a patch already I will gladly accept it! (you can just link to a git repo with the fix too and I will figure out the rest)

~davinkevin what change? i see the issue as well

I did the change on my instance and I confirm it has fixed the issued. IMO, it appeared after 4.2.8 patch on my private instance.

+1, with local and bird.makeup instance, as an example: https://bird.makeup/users/eightsleep/remote_follow.

I got:

Error.
An error occurred while processing your request.
Request ID: 00-477100c77fabd1cdb41ee98248d06d2f-70e404ce9e91bca8-00

Development Mode
Swapping to Development environment will display more detailed information about the error that occurred.

The Development environment shouldn't be enabled for deployed applications. It can result in displaying sensitive information from exceptions to end users. For local debugging, enable the Development environment by setting the ASPNETCORE_ENVIRONMENT environment variable to Development and restarting the app.

~rursache from the code, I don't think this app calls a nitter instance. It seems to use the graphql endpoint on twitter itself directly.

See TwitterUserService.cs. I didn't find anything about nitter in the code.

After 2 or 3 days, I got in the same situation again, impossible to see tweets in the UI and a lot of error fetching tweets from a lot of accounts.

To solve that, I've automated the restart of the app every 8 hours, it should be enough to keep the log quiet and to make the app working.