✳️ 2nd Cumulative Update for December 2021

• Admin button verification for telegram ID ⚠️
• Bug fixes and general improvements
• Improved crime coefficient logic
• Fixes to connections notes, filters
• Fixed Admin permission check for filters
• /promote now gives manage voice calls perms by default
• Fixed "/help module name" in pm

With the recent telegram update Saitama and other bots wont be able to ban "telegram channels" for some time until the next ptb update and until we shift from ptb v12 to 13, this gonna take a while, ensure that you and your admins are on latest telegram app and are able to handle telegram channels posting as users cause shit just got real

Tip: one way of not letting telegram channel post in group is to run "/cleanlinked on"

For those tormented by jerks posing in your groups as channel, no longer!

Here is our solution as @DisableChannelRobot

Add as admin, it will delete channel messages and ban them on sight, no configuration required.

Your linked group channel is ignored.
You can disable cleanlinked and simply switch to the bot!

Powered by @Kaizoku

🎉 Final Update for December 2021

This is most probably going to be our last update for Saitama, Shigeo and All Might on the Python versions
Python private repo will be archived and we will actively work on the go version starting 2022. Nothing to worry about, the bots will still run and when we go version catches up-to the python ones we will hot swap them to the go version. Happy new year! 🥳

Version Upgrade
• Bumped up PTB version to v13.9
• Moved all PTB hacks to proper lib functions

Anime
• Removed kayo from handlers list
• Anime results now parse links and hide spoilers
• Removed /user command from anime module

Approval
• Fixed /approve gives error when not replying to anyone

Admin
• Fixed /purge x messages not working
• Design improvements for channel logging
• /del command deletes message above it if sent in the group without replying to target
• Added support to ban channels
• Added warning and ban button for channel mute, tmute, kick, warns because these do not work on channels anyway
• Rewrote admin cache logic

Connections
• Saitama now pins a warning when you connect to a chat in PM

Devs
• /broadcast now spawns a new thread to avoid blocking

Extras
• /paste now pastes documents
• /id command is now on steroids, provides media and other details
• Added a warning to UD results because dumb people think its an actual dictionary
• Added a google search button to UD
• Paste now uses telegraph instead of nekobin
• Minor changes to strings here and there
• Added some more bugs to fix later
• Added an easter egg for Lord Full Metal

Filters
• Fixed filters not storing caption

Fun
• Removed /rlg and /sanitize commands
• Added gif support using an API for /pat
• /pat replies to you if you try to pat the bot

Greetings
• Fixed sending stickers as a welcome message
• Welcome mute now deletes user joined message (service message) and its own kicking user message if the user failed captcha verification, this results in no spammy messages if a user fails multiple times

Locks
• If lock forward is on, do not delete linked channel forwards
• Fixed lock messages and media not working

Reminders
• Bug fixes and improvements to remind

Sibyl System
• Changes to hue and cc logic

@Kaizoku | @OnePunchSupport

🐞 Bug Fixes January 2022

Starting with this update no new feature will be added to the bot until we finish up the bot in go, bug fixes maybe pushed depending on severity.
There are plenty other bugs to be fixed, we might release updates on those if we can.

• Fixed errors in purgeto
• Ran autopep8 through the bot
• Made /warn disableable because of this convo
• Bug fix for bare welcome

Suggestion for Rose support:
Please have the flexibility to help your users, not everything needs to be professional to the point it becomes a pain instead of help. If the only team on the planet who can help wont help, who will?

@Kaizoku | @OnePunchSupport

🪲 2nd Bug Fix Update January 2022


• Fixed trying to translate🐞 non-text in translate
• Fixed 🐛no results found, no args
• Fix local variable referenced before 🐞assignment errors
• Fix getting anime 🐞description, character description in anime
• Fix passing 🐛unnecessary arguments
• Ignore errors when sending the No idea who this user is text
• Ignore 🐞Unauthorized errors
• Point to right lang🐛 codes list in 🐞translate
• Fixing🐛 passing invalid value for URL when kanging

🗒 Note 1: As you can see, lots of bugs here and there that were fixed for this update.

🗒 Note 2: For those expecting us to add spoilers to lock, we have no plans to add a spoiler lock type as spoiler is just another markdown like bold, italics - there isn't a need to lock it.

@Kaizoku | @OnePunchSupport

👁‍🗨 Reactions are now enabled!

🗃 Cumulative Update April 2022
• Added a new module - SibylSystem
• Fixed /paste command
• AFK, setbio, setme, stickers, and similar stuff will not work for channels now
• Fixed translate module not working - we added our own pip module
• Fixed error when running setfloodmode tmute
• remove undocumented stickers feature
• Debug mode hides spamwatch token if specified
• Send a message if logs are empty
• Use empty string as note name if nothing is specified
• Download profile pic to a temp file for user info
• Sticker blacklist now checks if replies to messages have a sticker or not
• Some more quality changes to blacklist stickers functions
• Fix double url'ing in filters
• Treewide - connection takes CallbackContext instead of a bot
• Connection returns false by default
• Removed group requirement for flood and set flood commands
• Some string changes to connection
• Some more message sending tweaks to custom filters
• Clean service message even if the welcome is off (if you turn on clean service)
• Bump PTB version to 13.11
• Allow Kang on video stickers
• Sibyl based enhancements to user info command
• Ignore telegram bots in sibyl and spamwatch info
• Always print chat count at the end of info
• Refactor to user info and sibyl mode
• Added /check command into sibyl module that anyone can use
• Fixes to health and reply_markup for sibyl banned users
• Fixed bug where a user without promoting permissions can promote users
• Improved user logging to admin defined log channels
• /info command can now get information on channels
• use BytesIO for the user and channel images
• Welcome now sends a random message when the bot is added to a group
• Fixed /purge not working without an argument
• Suppress some pm annoying shitty errors
• Anti flood bans if a channel floods the group because they cant be muted
• Added feature to send random media and documentation
• Fixes to welcome mute and clean service
• Fixes to random welcome types
• Notes now send a button even if there is no text by taking the note name as the text

@Kaizoku | @OnePunchSupport

Saitama, Mob and AllMight were shitting themseleves past whole day, this has been fixed with a temp module unload.
Will post further updates down the line.

I go back to sleep, night night

💬 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