You're currently posting from a proxy IP. If you disable that, you shouldn't be able to load the attachments domain, as it's known to be blocked by your ISP (1000s of other people have the same problem, and you can search for it on the forums).
I tried rate limiter (asynciolimiter instead of aiolimiter though, it's still in my fork), but I still was getting errors even with like 20 to 5 requests per minute. As I see it whole problem not is per-user, it's overall forum load (not "ratelimiting you" but "ratelimiting everyone at the moment"). For sure it's better than firing requests without any limits at all, but not sure problem can be solved without explicit retries on 429.
yes, as i mentioned here - it works with proxy in your modded version
Then I think Sam is probably right. Your browser is proxied somehow while checker app is not. It's either try ask/force your ISP to unblock attachments domain or use proxy/vpn in both.
Do you ever plan to release an offical one on the main github page rather than requiring users to login and hunt through extra menus? It's 18 months out of date, it's time to push a proper update.
From what i can tell, he is releasing only the final version of the checker, leaving beta and alpha builds in the action tab for people that want it and to be fair, i find it ok. That way you have a stable release, but if you feel adventurous you can go on Buggy side of the deal, albeit with a couple hoops to pass by. What i mean is that 10.2 is stable release even if old, and in action tab is 11 but beta build. Considering how many changes to get it back to stable are needed in the past week, to me at least it makes sense why he is doing this way.
My priority these days is another project. I wanted to finally release an update here but wanted to fix Linux Wayland issues. Seems like that not gonna happen easily, and now there's this huge new problem, once this current issue is fixed properly I'll make a release
Looks like I'll end up with a mixed solution then, use aiolimiter but retry indefinitely with some delay if a rate limited response is received. Do you have your rate limited fork code anywhere?I tried rate limiter (asynciolimiter instead of aiolimiter though, it's still in my fork), but I still was getting errors even with like 20 to 5 requests per minute. As I see it whole problem not is per-user, it's overall forum load (not "ratelimiting you" but "ratelimiting everyone at the moment"). For sure it's better than firing requests without any limits at all, but not sure problem can be solved without explicit retries on 429.
upd: place you'd put limiter restriction is better than what I did, now I'm embarrased
just checked back thought the logs for the night, no errors at all, and no activity currently. Looks like it's working well and so far it's been managing to keep up with demand (if it hadn't, it would've been going through a backlog of threads to cache slower than it is asked to cache them)
Over 580 full refreshes without an error. Was decently fast considering I had forgot to bump the number of workers back up.
Hmmm line 514 is in import_f95_watched_threads()... are you on latest build?
haha yea i edited my thoughts as i was brainstorming and even im struggling to read it now.
that would be a great idea, except for one thing: game updates. kinda the whole point of all this really lmao
LOL - I forgot to exit before updating so files were locked. I'm an idiot basically. Updated again to Beta 1227 and the sync took awhile (it is 2,539 games though and it just ran in background).
It's planned, I was working on it long ago but didn't get that far. Considering the new rate limits as of last week, it seems even less feasible now.
