💬 Chatbot Module Update

Chatbot module has been permanently unloaded from Saitama, All Might and Mob.

Please use our dedicated chatbots moving forward, they do nothing else but chat.
╔• @RinRobot
╠• @IkarosRobot
╚• @NymphRobot

See @Kaizoku for more | @OnePunchSupport

🗃 Bug Fix Update April 2022

• Fix sibyl var in sample config
• userinfo: use better logic when printing gban info
• userinfo: don't check gbans for health
• welcome: Enable formatting for /welcome and /goodbye
• sibylsystem: add to the help with placeholder text
• move sibylClient to sibylsystem module and make /check disableable
• remove all prints and use LOGGER.debug() instead
• sibylsystem: connect to sibyl only if loading the module
• welcome: fix random files when welcomemute is strong

@Kaizoku | @OnePunchSupport

♿️ @ShigeoRobot got limited

🔎 Problem:
• Copyright infringement
• What exactly was infringed is currently unknown

Yep, Telegram straight up limited a bot for copyright infringement without telling the affected party what was infringed, so we cant resolve it until either end gives us an update. Splendid!

❕ Actions Taken from our end:
• Emailed telegram and the reporting party
• Contacted TGLib
• Contacted contacts I know of
• Contacted support through the app


📝 Updates so far:
• Day 9+ and noone replies, not the reporter, not telegram - noone
• Telegram gives no fuck unless your bot has maybe 100M users, no replies to us so far

To this date we dont even know what is wrong here, let alone fix it.
Many thanks to telegram and their support for developers.

Further updates will be posted by editing this message.

@Kaizoku | @OnePunchSupport

⚛️ Heroku scheduled to shut down free dynos forever!

Last date for free dynos is November 28, 2022. Source

For those who have their group management bots on heroku and have no place to host them, feel free to reach out to @Sawada

♿️ @ShigeoRobot is back up!

As most of you may already know that Telegram had limited Shigeo on June 29th for copyright issues, looks like the limit has been lifted now (after 65 fucking days).

For those who maybe seeking answers for the future safety of their own bot here are some key points

• We still have no idea why the bot was limited
Telegram has given 0 information on "what was infringed" on the bot. Even after us repeatedly requesting them (and the alleged party) for information.

• Lack of response
Both the alleged party and telegram have given 0 responses about this to date, even after us repeatedly reaching out to them over email (like telegram asked us to do)

• 65 Fucking days to fix or confirm an issue
Huge upset on telegram's side where they took 65days to lift the restriction and still haven't actually responded to any of our emails.

⚠️ Devs Message for those who host their bots

Be prepared, if for some reason telegram limits your bot - they have the shittiest support and verification in place to take your side, to this day we have no idea what was infringed as there isn't anything to infringe on the bot in the first place.
The infringer email bounced for days and still has 0 response, suggesting that the copyright notice was most likely bogus and telegram still acted on it and then took 65 days to resolve it.


That said, @ShigeoRobot is back up and running like it should be!

@OnePunchUpdates | @Kaizoku

@GroupHelpBot gave user data to the Italian police solely because they were sharing copyrighted media. Payment info, group members, group admins, and messages were provided.

This is what happens when you use bots without understanding who is hosting them.
Stuff like this is the reason its more important to use your own bot or fully understand what you are doing around third party bots.

To add, Kaizoku understands a level of privacy and respects it. No such issues will ever be found on ours (for obvious reasons if you ever saw @Kaizoku)

Stay safe, stay alert, trust no one blindly.

Torrent Freak | PrivSecGoy

📉 Downtime

The SQL server is having some issues at the moment.
All bot services are down and we are working to get things back up and running.

Sit tight, eat popcorn.

Edit: Everything is back up

✨ Major update

We know its been long since an update, so here is a quick one.

We are now slowly rolling out our Golang rewrite of Saitama.

@NekoyaRobot is the first instance running the latest code.
This change will later on be also rolled out to the rest of the Saitama copies.

Look forward to it.

For any questions head to @KaizokuBots

Shifting Saitama to the new version, the bot will be down for approx 30minutes or less.

Saitama is now running our latest Go lang version.

For any queries, ideas, rants please visit @KaizokuBots

✨Update Changelog:

• Reworked federation, guestbot, and lock handling for better stability and security
• Added Grafana dashboards, Prometheus metrics, and improved monitoring coverage
• Improved i18n/localization across greetings, leveling, feds, misc, and admin modules (EN/ES/JA/RU)
• Added wildcard blacklist support and improved pattern matching
• Added configdoctor tool for config drift detection and startup validation
• Improved webapp permission handling and admin verification flow
• Optimized dispatcher concurrency, async logging, sticker handling, and DB insert performance
• Hardened panic/error handling across callbacks, chats, messages, and captcha flows
• Fixed multiple federation, greetings, callback, channel, and database edge-case bugs
• Added new commands/features including /cash, guest info/stat commands, new locks, Android module, and uptime aliases
• Improved deployment/build tooling, dependency updates, and CVE/security fixes
• Large internal cleanup/refactors across cache, logging, monitoring, and error systems

Support: @KaizokuBots | @Kaizoku