Please remember to follow our Code of Conduct, making unprovoked insults will lead to admin action. Continued breaches will eventually lead to temporary and permanent ban. for more information, see https://legal.programming.dev/docs/administration-guidelines/#protocols
Hi, I've sent you a new DM
Hey
Please check your DMs, you got unresolved reports from c/linux
Please respect our instance's Code of Conduct when interacting with our communities. Repeated breaches on admin moderated communities will lead to temporary instance-wide ban.
For the last ~2 weeks the infrastructure team have been actively investigating performance with our server and actions are currently being taken. You should expect us to post an announcement with more detailed information soon™.
Appreciate you had the awareness to delete the comment before we got around to the report. It was still a breach of the instance's Code of Conduct (1.1, 3.2) and repeated breaches may result in a temporary ban.
Not sure why, but lemmy.world keeps logging the bot out. I'll look into it this evening.
The bot is up and running again
The bot should update very 30 seconds or so, if it doesn't, there is likely some connection error that causes it to restart. I'll have a look soon.
Which issues are you referring to? Instance shouldn't matter as long as federation works properly, I think the bot has simply crashed and I don't have access to restart the server before next week.
You can use @LiveThreadBot@sopuli.xyz in the meantime though.
Yes, I've noticed an uptick in connection errors from the lemmy.world servers, which is likely the reason. I am planning on rewriting the bot in Erlang/Elixir from python and will look into the fixing any potential issues once that happens. I don't have access to the server at the moment as I'm away on holiday, so if the bot is down, I can't restart the process unfortunately.
Hi
Can you update the title to be the same as the updated title in the news article?
The (successful) end of the kernel Rust experiment