Unexpected downtime:

Edit: 02:11 PM - Saitama is down right now, This post will be updated once It's up.

Edit: 03:30 PM - bot is up, going back to bed ⚰️

🎉 @SaitamaRobot wishes you a happy new year, be brave, be strong and do not forget to do 100 push-ups, 100 sit-ups, 100 squats, and run 10 km every single day! 👊

Announcement to all users running Saitama forks or any other Marie fork.

Key points to keep in mind before moving forward:
• This information is valid only for Telegram bots licensed under the GPLv3
• DON'T consider this information for other platforms or programs
• This does NOT apply to bots licensed under the AGPL license
• Don't blame us if other bot owners refuse to pay heed to this
• This post does not aim to be legal advice

You may know or have noticed how we and many others have gbanned or asked those who run Saitama or similar forks to provide their source code; some have been gbanned, others complied under the pressure of the same.

However, misinformation regarding the terms of the license has been floating around in the Telegram bot community. It is indeed true that the GPLv3 license asks to "disclose the source" of a distributed application or to provide a way to download/access the source. However, this does NOT apply to Telegram bots. You can, legally and without violating the license, keep your Marie fork closed source.

This is because Telegram bots don't count as "conveyed works" and hence the conditions of the license don't apply to them. [¹] [²]

I've been gbanned for GPL violation. What do I do?
If you were banned on Saitama or Sibyl, we will unban, you can reach out to us @OnePunchSupport or @PublicSafetyBureau respectively.
DO NOT PM us for that.

Why was I banned in the first place then?
Lack of information would be one reason, the other being the norm that a closed source on a code-as-a-service is violating the GPLv3 (which it isn't, as stated above).
Some bot owners probably already knew about this but refused to acknowledge it.

Wait? So I can keep my bot closed source?
It is your decision to make. You're not legally obligated to make your bot open source.

Is Saitama going to be closed source now?
Unlikely.

Someone (g/f)banned me for keeping my Telegram bot source code (licensed under the GPLV3) closed. What should I do?
Try letting the bot-owner know of the terms of the license that allow you to do so. If they refuse to unban you, that's that, don't come to us for help.
However, if you do decide to keep the source closed, just know that you're doing a disservice to the open-source community which made the existence of your bot possible.

Regarding the AGPL license
Some Marie forks (eg: Haruka) have shifted to the AGPL license, in which case you are liable to release the source code, no way around it.
[Source]

Stats as on 05-01-2021:
• 3884 blacklist triggers, across 562 chats.
• 474 blacklist stickers, across 101 chats.
• 16465 filters, across 1853 chats.
• 1800 disabled items, across 472 chats.
• 22080 banned users across 262 Federations
• 630 gbanned users.
• 125 log channels set.
• 8389 notes, across 1288 chats.
• 830 chats have rules set.
• 1006227 users, across 10425 chats
• 12594 overall warns, across 1281 chats.
• 379 warn filters, across 120 chats.

We hit a million users, thanks for all the spam 🥳

Roses are red
Violets are blue
Ohayo! minna san!
We have an update for you

🌟 Feature updates
• Added approval module
Most of you have seen this in rose as well, this module lets you approve users to be exempt from flood, locks, etc.
It's a local whitelist.

• Added silent ban and delete-warn
We added 2 green commands to Saitama
/sban command works just like ban but will clear any command text
/dwarn warns a user and deletes itself and the target message

• Added check to leave the group
A feature to allow the bot to "leave a group" if added.
We recently disabled Saitama to further groups using bot father but this way existing groups cant promote or change permissions/title of the bot, so this check just makes Saitama instantly leave a group if its added but lets existing groups toggle its permissions or promote and demote

Disabled as its buggy still, we will push another update on this.

• Error handling simplified
Saitama now dm's the owner with errors

✨Enhancements
• Some new welcome messages
• Fixed some stuff pointed out by deep source
• Log special users (disasters) to welcome logs
• Improved gitignore
• Added code of conduct
• Replaced hardcoded instances for a support group to a variable
• Lots of edits and improvements to the readme
• Format code with black
• Removed neofetch from stats command
• Updated donate command
• Added channel links to kayo and kaizoku commands

🐞 Bug fixes
• Fixed some typos
• Handle spamwatch connection errors
• Fixed bad URL string in kaizoku command
• Fixed muting admins using /mute bug
• Added some more bugs to fix them later

🚮 Stuff trashed moving forward
• Deploy help and config help
• Heroku deploy button and its help
• Dragsama's social life

Pull request #355

🔽 Downtime!

Looking into this, bye bye sleep!
Edit: Saitama is up.

⚜️ Anti-spam blacklisting checklist
The following must be subject to when gbanning or fbanning a user under Sibyl or Saitama network.

• Sensible reason or as per layout
• Screenshots, videos by random people arent considered
• Ungbans depend on the severity of case
• Memeing with blacklists or threatening civilians is unacceptable
• Gather proof before pushing bans or testimony is on the line

• The following types are considered for blacklisting
- Porn flood in sfw groups
- Adverts such as subscribe, join, follow this or that
- Private messaging users with promotions
- BTC or trading adverts in non btc/trading groups
- Raids in group to spam, threaten, abuse

• The following types are viral-bans
Viral as in, depending on the severity of the case all the group admins of such a group will be considered hostile
- Mass adding
- Raids and ganged abuse
- Alt accounts will be bundled in as well
- If the add count is high, the ban will be permanent

• Consider taking non sibyl bots reports to Spamwatch or SPB
• Ungban/Reverts can be considered on case basis

📍 Sibyl Template:
> reason // By ID | #caseID

Explanation:
- reason - reason for the Ban
- By ID - ID of the user who pushed the Ban
- #caseID - Case ID which has the proof, source, enforcer ID (if available), logged.

To help solidify gbans and blacklisting on Saitama and to provide more transparency we have made a detailed listing about all this.
Those curious can visit here and those with queries can visit @PublicSafetyBureau

Do note that Saitama does not support mass adding users, spamming, raiding and such activities will get you blacklisted in multiple bots and bar you from a very wide range of groups.

Saitama is down as the postgres service went down.
Will be up shortly.

Edit: Back up.
Edit2: wtf is still not up
Edit3: nvm edit 2

He is still a little slow to respond, will look into this.
Edit4: Sounds like telegram api at fault

❕ For those confused as to why the /anime and similar commands are not responding, the reason is that anilist is having issues. They enabled ddos protection by cloudflare so clearly something is up with them today.

🤖 Saitama is busy fighting off massive raid (11k raiders) in @Kaizoku
It might feel slow but its busy gbanning a very large list and defending a group from mass joins past 24hours nonstop

@master_raider the invite link to @OnePunchSupport is open.
What are you scared of? come

Or is 11 million a little to exaggerated?
Might as well raid @OnePunchUpdates and gimme some members while you are at it.

" I'm not a big fat Pajeet. I'm THE big fat Pajeet "

"It's bonk time"

🔱 Federations for dummies

• What is a federation?
A federation or short for fed brings control for multiple groups into a single group with centralized control.
Groups that join a federation (will be explained later in this post) can quickly act on commands given by designated fed admins from anywhere around Saitama, as long as they are in the said fed area.
Example: If you have 10 groups all joined to your fed, then one fban in any group will ban the target user in all 10 groups.

• Whoa! How to use this?
Head over to @SaitamaRobot's pm

/newfed Name of the Fed here

This creates a fed and the one who creates (you) will be the federation owner.
Now you will get an ID that would look something like
8387f3cc-c72c-4824-88fc-6a2df6409688 (this is the ID for the fed @Kaizoku on @SaitamaRobot)

Note: Fed IDs are generated by a bot for that bot, you cant use a Saitama fed on any other bot.

• Now what is next?
Simply go the groups you want (you must be the owner there or the owner should run the command) and run

/joinfed 8387f3cc-c72c-4824-88fc-6a2df6409688

Should you get a success message then you did all the steps here correctly.
✨ Congratulations! you have your first group in fed now, roam around all your groups and join them as well into your fed.

• So what happens now? groups joined to this fancy stuff.
Now you can designate federation rules (optional). Most people don't know this bit but if you have a lot of groups and most groups are having common rules then you can use /setfrules to set up common rules.
Set it in any group in your fed and it can be used for all groups.

Boop! Now you have a set of common rules (you need to decide how you want to display these btw)

• How to handle bans using fed?
It's simple, works the same as /ban but the command is /fban
Simply do that and the fbanned user gets banned in all the groups in your fed.

• Can I add more admins?
Yes, you can do /fpromote /fdemote
Note: Fed admins are not the same as group admins, do note that a fed admin ban can affect all the groups in your feds.

• How to check where I have been fed banned?
The command /fbanstat can help you with that, you can also look at other user's fed bans.

❕ Some other FAQ's around Feds

• Hi, I have been fbanned from some fed, what do I do? can Saitama Support help me?
Well yes but actually no, if you are fbanned or banned then ask that fed owner.
Saitama support will NOT provide any help for fedbans

• Possible to join more than 1 fed?
No, you can subscribe to fbans from other federations though.
The command is /subfed ID here. This would mean that any bans done to anyone will also reflect in your subbed federation anywhere

• OwO This is powerful, I will make dozens of feds and destroy someone whole!
No LMFAO, feds only work in groups where a group owner has joined a fed, fbanning people in a fed no-one uses is just you wasting your time.

Still have questions? make sure you read up well on the federations help section on Saitama
Whoa! you still have questions? Well head over to @OnePunchSupport then

Purge wasn't working, restarted the bot and that fixed it.

🏆 And the best pull request award goes to...this guy

⚠️ Unplanned Maintenance

Our host is doing an unplanned maintenance on the dedicated node/dc that our bots are hosted on.
All our services are now down.

Ultra rare (at least we haven't seen this happening ever) and no timeframe is provided on this, so we have no workaround but to sit and wait.

Downtime: 1h 36m
Edit: Server is up!

『 ✳️ Major Improvements: 』

• Filters now do not reply to anyone
Triggering filters now sends a message to the group but does not reply to the user-triggered or the user replied to.
We gave a lot of thought and this is the best solution moving forward.

• Fixed /rules reply pointing to target user
If you reply to someone with /rules then Saitama will reply to the user you replied to with output.

• Added last seen to afk
Afk now shows when it saw you last

『 🐞 Fixes and Improvements: 』
• Fixed a deploy bug
• Fixed a typo in the anime module in the results
• Do not show bots in /admins
• Fixed sqlalchemy.exc.NoSuchModuleError
• Edited /start response a little
• Improved help section
• Disabled black workflow and use pre-commits instead
• Comments in config
• Join logger now shows the bot added when you add it, before it showed the user joined which made no sense
• Skip logging on/off events for chatbot
• Fixes for lockdown command
• Added some more bugs to fix later

『 🚮 Removed/Dropped Stuff: 』
• Removed Docker support
• Removed Heroku support or any references to Heroku
• Removed RSS and maths modules

『 ⚠️Warnings: 』
• @dragsama's social life needs more head pats
• @dank_as_fuck needs better gifs

『 ✨Other Important stuff: 』
• Increased coffee intake to avoid nonsensical reverts
• Trying to work on proper sleep schedules

Pull request #366

How we deal with spammers - Cinematic Trailer

By @OnePunchSupport

💬 @Intellivoid has shut down their chatbot api permanently.

What does this means for Saitama?
Simply put, Saitama's chatbot/AI will now no longer function, we might even remove the module in next update since its useless now.

Note:
Please do not come to our support chat asking why.
We do not own the api.
This notice affects any bot/userbot that was using coffeehouse chatbot api.