“We repeated the analysis on bot traffic hitting the “post”, “reply”, and “like” endpoints for a specific social media platform and similarly did not find an unexpected shift before or during the event period from either Russian-origin IPs or globally. Based on our assessment, the data does not appear to support the claims that the strikes crippled social media manipulation”
PSA: No, Russian bot traffic has not significantly decreased. Only Yandex’s network is mostly silent, which doesn’t have a huge impact on automated requests from all of Russia.
And neither has much to do with social media bots. Stop spreading this kind of misinformation.
Tried #Moltbot/ #OpenClaw today. Made it do 5 different things to try it out. It literally failed all of them. It didn't even manage to set up a simple RSS alert. It created the cronjob to check for a new article every 30 minutes and then just deactivated it right away.
I asked it multiple times whether it was disabled, because I could clearly see it in the UI as disabled, but it always tried to gaslight me into believing that it's activated and that the UI is wrong.
Needless to say, the cronjob didn't run once.
I don't understand how people can extract (even temporary) value out of these things. It's like trying to get a kid to help you with your taxes.
@aaribaud sounds like an issue with MySQL to me. If you have an application existing for so long, there’s going to be breaking changes. And it wouldn’t be the first braking change. We’re nearing 2038 rapidly. I don’t see “oh, we must support 30 year old systems that for some reason need to update to MySQL 10” as a valid excuse for not fixing such a big issue.
@aaribaud but it is a problem for TIMESTAMP fields. I don’t know why Kea uses TIMESTAMP instead of DATETIME, but honestly, I see no reason why a 64 bit database should struggle with 2038+ timestamps at all.