And here is a Saitama ASCII Art

Restarted the bot and added /8ball as a new fun command along with some minor bug fixes.
cachetools isn't working well on windows (or maybe we dunno how to get it to work) so we will either shift Saitama to wsl or shift Saitama to Redis, if anyone knows how to fix or want to help please head over to @OnePunchDev

For those who run support groups or assistance groups with redundant questions, a little bit of playing around with filters can go a long way.
Here is one such example.

So a day or two ago someone contacted saying they want to sponsor Saitama, ngl felt nice that someone actually wants to fund the development.
Turned out to be a tieup to a sales method, when I said we can do this on our own the next reply I got was "bhain cho" ~ translates to "Sister fucker"

Just adds to the list of examples of why we have a zero tolerance policy around our groups, among with the many other spammers that attack the supporting staff out of hate once they get banned/gbanned or reported.

🎉 New bots 🥳

Lots of users want Saitama just for the chatbot, some even ask if we can disable all admin functions and use chatbot.
We got plenty users asking if we can make a chatbot only version and possibly a waifu one.
To this I say, Applaud, out supreme power.

We are now running 3 chatbots, open to all.
• @IkarosRobot
• @NymphRobot
• @RinRobot

Note: They do not use coffeehouse API.

Feel free to add them to your groups.
And soon enough we will be coming up with an index of all our bots, groups, channels @Kaizoku
Please do join as all future new releases or bots would be posted there.

Fun update about the bots posted above.

I think cleverbot rekted our account for no reason, looking into this but it seems like will be shifting the 3 bots to coffeehouse.

Life is shit and then you die.

Our git repo is more of a small website now.

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"