Minor downtime as service crashed, looking into this.
Edit: it is up but wont reply to missed messages.

Fucked up, probably some chats saw that saitama suddenly removed their filters, this was not supposed to happen and we are now looking into it. You might have to add the filters back again, we apologize for the inconvenience caused.

Saitama would be down for approximately 10minutes.

It's up.

📈 Major updates:

‣ Fixed feds (at least we hope so)
Translation, past bugs and stuff are mostly fixed now.
This version would be on stable feds (hopefully)

‣ Revamped entire help documentation of feds
Way more neat, way more commands to play with and way easier to read.

‣ Added Sticker pack blacklisting
Admins can now blacklist a sticker pack whole and saitama would delete if any sticker is sent from that pack.
While users can kang to a diff pack and bypass, this should at least let administration keep tabs on some cancer stickers around your community along with some recuded eye cancerous stickers.
We hope that this would let some chats have some mental peace.

‣ Check admin permissions if they use /promote.
If an admin does promote on someone but they dont have the "add admin" rights, saitama wont listen to their /promote command. This should add some sense of security to group chats as the owner can now have more precise control on users.

‣ Check admin ban permissions before listening to ban commands.
If you have admins that arent given ban perms then this update will make sure that saitama doesnt listen to their /ban commands either.

‣ Reports are fixed and improved.
Check them out and you will see

❗️ Important:

‣ Reverted "Allow Admins to use disabled commands"
This was getting in the way where you had multiple bots and disabled some saitama commands and hence we reverted this bit.

‣ Reduced the welcome mute timer down to 120 seconds.
This used to be 160seconds but we believe that 2 minutes are plenty.

‣ Quick unmute by showing an "unmute" button for a flood muted user.
On flood muting someone saitama will now show an unmute button attached to the flood muting a user message.
Save time typing those unmute commands!.

‣ Sed is now working.
Most of you know it as "s/owo/uwu"
Yeah that's up now.

‣ Grammar correction is added back cause yall need it.
Correct typos and lang check by sending /t when replying to an existing message.

🛠 Bug fixes and smaller improvements:

• Translation updates at some places.
• Removed some non relevant and redundant messages from welcome.
• Fed broadcast is now owner of fed only (bug patched).
• Bug fixes to welcomes.
• Deleted backups.py cause it doesn't work anyway.
• Improved the output for gbans in log channel and info command.

Trivia:

• The Shiken branch had a commit to change the license from gplv3 to agpl, this plan is dropped.
• Our support chat is now aiming for a more progressive FOSS community.
• Technical queries around Marie forks are welcome on the support chat, you wont get bans for asking help.
• Lets all aim for a more progressive community by helping each other out.

Anyone who finds bugs around is invited to please join us at @OnePunchSupport to let us know of the same.

Signed
Heroes Association

🏷 More updates and bug fixes

New Module
• Wiki is now added.

Prefer this over UD and use via /wiki wordhere

Improvements
• Disasters are fban immune.
• Help of each module is given a fresh look.
• Improved documentation for feds.
• Fixed parse mode issues in gbans.
• Translation improvements to blacklist sticker.
• Fixed bugs in welcome and corrected typos.
• Added group blacklist function(incomplete)
• Help section redone because too many modules.

🏷 Some more quick updates to the bot

Important:
• Any group admin can now turn chatbot on and off.

Other stuff:
• Changed tg_bot to SaitamaRobot across the repo
• Fixed broken markdown in /markdownhelp (ayy lmao)
• Corrected some typos

Note: We will now put some effort into transition towards ptb version 12.

Those who are confused as to why Saitama is not responding, this issue is from telegrams end as the boi api itself is down.

In short, every bot on telegram is most likely facing issues.

Edit: it's back up, Saitama would catch up soon.

Temp issue with temp muting and slap mute where it's muting forever and not the specified time.

Will look into this tonight. Muting is unloaded until then

Muting is loaded and I did nothing except restarting the bot process, lol.
And it seems to work.
In case anyone else notices tmute is muting "forever" instead of a temp mute, please let us know immediately at @OnePunchSupport

Unexpected downtime, looking into this.
Meanwhile all admins of their own chats are requested to be on alert as saitama wont be watching your back for a lil while.
I'll keep you posted on updates.

Edit1: Okay, someone on server touched the ptb version, looking into this as shifting it back might break some other bot.

Edit2: Shifting this to venv and testing quick, will also load gbans side by side (they were not unloaded past month)

Edit3: We are back up, slightly more stable than before. (shifted the bot to venv)
Side note: I have loaded gbans back, so we will be protecting your chat from spammers and other shits.

Very minor downtime reported on saitama.
❗️ Cause: Unknown
✅ Status: Resolved
📋 Mode: Debug

Saitama has crossed 300k users and 3k group chats.

Current stats:
950 blacklist triggers, across 193 chats.
42 blacklist stickers, across 13 chats.
4845 filters, across 556 chats.
639 disabled items, across 163 chats.
20176 The user is banned, on the 61 Federation.
170 gbanned users.
52 log channels set.
2792 notes, across 462 chats.
239 chats have rules set.
313880 users, across 3007 chats.
3250 overall warns, across 356 chats.
110 warn filters, across 47 chats.

Source link

Message to bot forks that deployed their bot but the support chat points to @OnePunchSupport. Update the support chat to your own support chat, OPM support is NOT to support your bot instance.

Please do NOT bring us questions that are NOT of @SaitamaRobot or its own repo as we cant help you with those(literally).

Message to Thunder Bot owner:
No, your code is not even close to Saitama repo, you need to post your own repository there and you need to update support chat to your own support chat.

I wont recommend anyone use thunderbot, its not respecting the license and its simply offloading its own users to our chat for support.

Minor downtime of less than 10minutes. shutting down a game server and rebooting the node for some updates to take effect.
Forgot to edit, already back up.

Minor downtime on Saitama as the bots server is being rebooted to pass some updates.

Edit: Windows server, installing updates.
I'm just gonna sleep on this.

Edit2: Its up.

We are aware that the anime module is causing issues for causes unknown. (Most likely server side and not on us)
We aren't gonna debug this as Saitama's next update that is under stabilization is expected to be done soon.

Next update would bring improved anime module and major backend overhaul to the bot.

Edit: Saving time, i just temp unloaded the module.

Minor Downtime. Buckle up.

Bot is up, chatbot is up.

Feeling saitama is slow today? non responsive perhaps?
Well, I don't care, had enough bullshit for the day.

Please do not spam the support chat saying its slow.
We know, we are working on it and there are plethora of things to do this week.

Thanks for your patience and continued tags. ^_^

Okay, killed all encodes and qbit on the server.
Unloaded 'rss','cleaner','anime','feds','connection','math','sed' for the night.

Bot is up and hopefully tomorrow we will look into setting up a logger that would print spammed queries (it wont log anything sensitive dont worry and i'll keep you guys posted IF we do setup one)

Testing some experimental stuff, saitama might be up and down for the next 20-3-minutes.

Edit: We are now running experimental Dev version on saitama, its slightly unstable here and there.
But we will push this to saitama and improve as we go along.

Next update will list all changes