No no no, thank YOU for a great improvement :)
Well, they're not his though. They're mine 😉.
A requester does not get special privileges over the subs they request. On the other hand... 22 out of 112 is a bit much.
The thing is, the more communities are added, the longer it will take to update all of them. Right now there's over a 100 communities, and it takes a little over 7 minutes to update them all, and then it starts over again.
This isn't a problem right now, but it won't scale forever. At some point (probably sooner than later), it will probably mean having to remove the communities with the least subscribers.
I'll need to investigate what went wrong here, eh. Sorry.
INFO:utils.syncer:Checking for new subreddit requests...
INFO:utils.syncer:New subreddit request received
INFO:utils.syncer:Success! Let's clone the sh!t out of food
INFO:utils.syncer:Done.
Possibly not the most enticing log message to receive.
Doing the lord's work here, I see 👍 .
Thanks, I was gonna do this tonight, but are you sure about that format? (I'm still relative newbie to the Fediverse)
Just to test: /c/about.
edit: Looks good, I'll merge it :)
edit2: Deployed :)
Nope, it doesn't use the API, but relies on the RSS feed and scraping old.reddit.com And those will probably also die at some point in the future, this will probably keep working a bit longer.
I'm having similar issues on lemmy.ml, not sure what causes it.
Well... There is the thing that I had this service running on another host at some point, it got federated with quite a few instances (including lemmy.ml and some others), and I had to reinstall it. Maybe those instances have a hard time accepting the new installation?
I'm kinda hoping it will sort itself out over time, maybe those instances just need to restart 🤞 .
No biggie, that's on me for making this error so vocal ;)
It's a curious one, this. The good news the error only occurs on this sub, (and once when I restarted the bot), so it's probably just a database misconfiguration. I'll get around to it this weekend.