🤖 Like Darth Vader, only prettier!
[➕] Added /admincache/admincache
• Saitama caches the admin status of a user, means when you do promote/demote it isnt reflected instantly (this saves queries), so when you want this to update on demand you can use /admincache to force a cache thrash. (this also auto thrashes in 10 minutes)
[➕] Added rate limiting to notes, filters
• Yay, yet another fuck you to those who were non stop spamming filter replies and causing flood waits.
[➕] Fixed a frontend issue in welcome security
• A tmute/muted user could just leave group > join > click on"I'm a human" verification and then get unmuted, bot now stores soft and strong mutes statuses in db. So once you pass verification once in a group it wont show it again.
[➕] Introducing random filters(Yes, copied this update text from Rose)
• You can have our baldie pick a reply to a word at random! Simply separate the two contents by %%%, on a newline.
Example:
• When bot restarts/starts it would send a message saying its up to Support chat.
👁🗨 Some more notable stuff
• Shout & weebify merged into fun.py
• chatlist is now groups_list
• Improved admin list
• Shifted markdown to html in some files
• Requirements.txt have static telethon version
• Fixed blacklist sticker tmutes (they were perma muting)
• Fixed "brb" case sensitive issue in afk
• Renamed "Welcome/Goodbyes" in help list to "Greetings"
• Fixed reporting and greeting in /settings
• Lil bit of bug fixes here and there
• Made some edits to the readme cause people are a dick
• Added more bugs to fix later
Pull request #296
[➕] Added /admincache/admincache
• Saitama caches the admin status of a user, means when you do promote/demote it isnt reflected instantly (this saves queries), so when you want this to update on demand you can use /admincache to force a cache thrash. (this also auto thrashes in 10 minutes)
[➕] Added rate limiting to notes, filters
• Yay, yet another fuck you to those who were non stop spamming filter replies and causing flood waits.
[➕] Fixed a frontend issue in welcome security
• A tmute/muted user could just leave group > join > click on"I'm a human" verification and then get unmuted, bot now stores soft and strong mutes statuses in db. So once you pass verification once in a group it wont show it again.
[➕] Introducing random filters(Yes, copied this update text from Rose)
• You can have our baldie pick a reply to a word at random! Simply separate the two contents by %%%, on a newline.
Example:
/filter 'awoo'[➕] Wake up message
Dont awoo 100$ Penalty!
%%%
Dont awoo 10$ Penalty!
%%%
Awoo all you want.
• When bot restarts/starts it would send a message saying its up to Support chat.
👁🗨 Some more notable stuff
• Shout & weebify merged into fun.py
• chatlist is now groups_list
• Improved admin list
• Shifted markdown to html in some files
• Requirements.txt have static telethon version
• Fixed blacklist sticker tmutes (they were perma muting)
• Fixed "brb" case sensitive issue in afk
• Renamed "Welcome/Goodbyes" in help list to "Greetings"
• Fixed reporting and greeting in /settings
• Lil bit of bug fixes here and there
• Made some edits to the readme cause people are a dick
• Added more bugs to fix later
Pull request #296
OOPSIE WOOPSIE!! UwU We make a fucky wucky!! A wittle fucko boingo!Anyway, added some more stuff
The code monkeys at our headquarters are working VEWY HAWD to fix this!
• Save a note with multiple replies
separate by %%% to get random responses.
• Fixed some bugs with filters random replies
• Added help examples for notes and filters
• Fixed a bug with purge
• Fix keyerr while migrating chat filters
Reported bug with filters not getting added, will look into this.
So..in short..
So..in short..
OOPSIE WOOPSIE!! UwU We make a fucky wucky!! A wittle fucko boingo!
The code monkeys at our headquarters are working VEWY HAWD to fix this!Saitama is very slow, Looking into this.
Edit:
It's fast again
Edit:
It's fast again
♿️ Yet Another update
• Fixed keyerr on windows
• Fixed console errors with kick, reply message not found
• Check bot status before checking perms
• Don't hit spamwatch if spamwatch is down
• Don't enable chatbot in pm
• Don't send chatbot error messages to owner
• Update help for leave, stats in disasters
• Fixed notes get connection issue
• Fixed translate module
We are observing the error logs today and might fix some more stuff soon.
• Fixed keyerr on windows
• Fixed console errors with kick, reply message not found
• Check bot status before checking perms
• Don't hit spamwatch if spamwatch is down
• Don't enable chatbot in pm
• Don't send chatbot error messages to owner
• Update help for leave, stats in disasters
• Fixed notes get connection issue
• Fixed translate module
We are observing the error logs today and might fix some more stuff soon.
💭 With the new filters and notes with random replies, you can now add your own way of fun to the group.
For example I have added
For example I have added
/8ball to support group as a filter. Check it out hereWhat are gbans❔ (Now called antispam on Saitama)
Stands for "Global Ban", comprises of a list of users that are so bad that keeping them out of groups is better for an average group stability.
Worst of users end up with gban tags and it is shown on the user profile in the
Saitama has designated users to push gbans on users that come under the following gban rules.
Basically means Saitama will ban that user anywhere he can ban/has permissions to ban provided the antispam mode is on.
Every group that uses Saitama is auto subscribed to Spamwatch, Sibyl which keeps most spammers away from their group before major harm can be done, we also provide a toggle to turn this off/on at will using
Do you guys gban anyone❔ for any reason❔
Yes and No, we can and will gban anyone who doesn't falls under the gban rules and no we wont ban them for any random reason.
Users that spam, run close sourced forks of Marie, bulk pm promote, attempt to scam users in a normal group, mass adding/kidnapping from other groups to their own or similar stuff like these end up being globally banned from the community that saitama tends to protect.
We operate this under a set of rules and the logs are always posted public on @OnePunchLogs for anyone to see and validate.
As of late we have shifted gbans through @SibylSystem (A division made for judging spam and taking actions accordingly) which not only validates a ban but logs the proof.
Do you guys revert bans❔
Yes we do, if you fix your ways your ban can be lifted depending on the case. If your ban was made in error then it will be lifted.
Hey, You guys banned me and now I look bad❔
Fault of your own action majority of the times, you acted and we reacted. Try following group rules next time and try not to be too hasty that you end up like a spammer.
Where do I appeal my ban or my friend's ban❔
Come to @OnePunchSupport or @PublicSafetyBureau if you are gbanned, if you are spamwatched then you can take your report to @SpamwatchSupport
Spamwatch/OPM Support banned me, WTF❔
Means you either abuse the support group itself or have a ban that cannot be revoked. Game over!
Why do you guys give a shit what I spam in my group❔ or when I mass add hundreds of people❔
We tend to only involve ourselves where our bot/connected bot/staff etc is involved, you come and accost them and we respond accordingly.
Telegram has many cool features like user-bots, bots, impressive arsenal of options - while these are ...well..OwO they also are abused by people who have intentions of their own, we cut them out from our groups and the groups out bot has taken the responsibility of defending.
Now...the most popular question that we get retorted with often.....
Telegram allows me to add bulk members, the platform allows mass adding, user-botting and everything you guys give bans for, so what gives❔
Absolutely valid point, telegram does allow all of this, however, it also allowed us to create a way of handling shit like this, you aren't the only ones doing what they want to and it isn't limited to you alone. When you get to use a tech to abuse for your own greed, we get to use it for the sake of the community being abused.
Stands for "Global Ban", comprises of a list of users that are so bad that keeping them out of groups is better for an average group stability.
Worst of users end up with gban tags and it is shown on the user profile in the
/info command. Saitama has designated users to push gbans on users that come under the following gban rules.
Basically means Saitama will ban that user anywhere he can ban/has permissions to ban provided the antispam mode is on.
Every group that uses Saitama is auto subscribed to Spamwatch, Sibyl which keeps most spammers away from their group before major harm can be done, we also provide a toggle to turn this off/on at will using
/antispam off/on Do you guys gban anyone❔ for any reason❔
Yes and No, we can and will gban anyone who doesn't falls under the gban rules and no we wont ban them for any random reason.
Users that spam, run close sourced forks of Marie, bulk pm promote, attempt to scam users in a normal group, mass adding/kidnapping from other groups to their own or similar stuff like these end up being globally banned from the community that saitama tends to protect.
We operate this under a set of rules and the logs are always posted public on @OnePunchLogs for anyone to see and validate.
As of late we have shifted gbans through @SibylSystem (A division made for judging spam and taking actions accordingly) which not only validates a ban but logs the proof.
Do you guys revert bans❔
Yes we do, if you fix your ways your ban can be lifted depending on the case. If your ban was made in error then it will be lifted.
Hey, You guys banned me and now I look bad❔
Fault of your own action majority of the times, you acted and we reacted. Try following group rules next time and try not to be too hasty that you end up like a spammer.
Where do I appeal my ban or my friend's ban❔
Come to @OnePunchSupport or @PublicSafetyBureau if you are gbanned, if you are spamwatched then you can take your report to @SpamwatchSupport
Spamwatch/OPM Support banned me, WTF❔
Means you either abuse the support group itself or have a ban that cannot be revoked. Game over!
Why do you guys give a shit what I spam in my group❔ or when I mass add hundreds of people❔
We tend to only involve ourselves where our bot/connected bot/staff etc is involved, you come and accost them and we respond accordingly.
Telegram has many cool features like user-bots, bots, impressive arsenal of options - while these are ...well..OwO they also are abused by people who have intentions of their own, we cut them out from our groups and the groups out bot has taken the responsibility of defending.
Now...the most popular question that we get retorted with often.....
Telegram allows me to add bulk members, the platform allows mass adding, user-botting and everything you guys give bans for, so what gives❔
Absolutely valid point, telegram does allow all of this, however, it also allowed us to create a way of handling shit like this, you aren't the only ones doing what they want to and it isn't limited to you alone. When you get to use a tech to abuse for your own greed, we get to use it for the sake of the community being abused.
Restarted the bot and added
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
/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
image_2020-12-18_20-33-01.png
340.7 KB
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.
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.
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.
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.
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.
image_2020-12-25_23-30-09.png
41.7 KB
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 ⚰️
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 ⚰️
|│ 🛂 Lang codes table │|
│• af - Afrikaans │
│• am - Amharic │
│• ar - Arabic │
│• az - Azerbaijani │
│• be - Belarusian │
│• bg - Bulgarian │
│• bn - Bengali │
│• bs - Bosnian │
│• ca - Catalan │
│• ceb - Chechen │
│• co - Corsican │
│• cs - Czech │
│• cy - Welsh │
│• da - Danish │
│• de - German │
│• el - Greek │
│• en - English │
│• eo - Esperanto │
│• es - Spanish │
│• et - Estonian │
│• eu - Basque │
│• fa - Persian │
│• fi - Finnish │
│• fr - French │
│• fy - WesternFrisian│
│• ga - Irish │
│• gd - Gaelic │
│• gl - Galician │
│• gu - Gujarati │
│• ha - Hausa │
│• haw - ??? │
│• hi - Hindi │
│• hmn - ??? │
│• hr - Croatian │
│• ht - Haitian │
│• hu - Hungarian │
│• hy - Armenian │
│• id - Indonesian │
│• ig - Igbo │
│• is - Icelandic │
│• it - Italian │
│• iw - Hebrew │
│• ja - Japanese │
│• jw - ??? │
│• ka - Georgian │
│• kk - Kazakh │
│• km - Central Khmer │
│• kn - Kannada │
│• ko - Korean │
│• ku - Kurdish │
│• ky - Kirghiz │
│• la - Latin │
│• lb - Luxembourgish │
│• lo - Lao │
│• lt - Lithuanian │
│• lv - Latvian │
│• mg - Malagasy │
│• mi - Maori │
│• mk - Macedonian │
│• ml - Malayalam │
│• mn - Mongolian │
│• mr - Marathi │
│• ms - Malay │
│• mt - Maltese │
│• my - Burmese │
│• ne - Nepali │
│• nl - Dutch │
│• no - Norwegian │
│• ny - Chichewa │
│• pa - Punjabi │
│• pl - Polish │
│• ps - Pashto │
│• pt - Portuguese │
│• ro - Romanian │
│• ru - Russian │
│• sd - Sindhi │
│• si - Sinhala │
│• sk - Slovak │
│• sl - Slovenian │
│• sm - Samoan │
│• sn - Shona │
│• so - Somali │
│• sq - Albanian │
│• sr - Serbian │
│• st - Southern Sotho│
│• su - Sundanese │
│• sv - Swedish │
│• sw - Swahili │
│• ta - Tamil │
│• te - Telugu │
│• tg - Tajik │
│• th - Thai │
│• tl - Tagalog │
│• tr - Turkish │
│• uk - Ukrainian │
│• ur - Urdu │
│• uz - Uzbek │
│• vi - Vietnamese │
│• xh - Xhosa │
│• yi - Yiddish │
│• yo - Yoruba │
│• zh - Chinese │
│• zh_CN - Chinese │
│• zh_TW - Chinese │
│• zu - Zulu │
• Source👍1🔥1
🎉 @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]
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]
www.gnu.org
Why the Affero GPL
The GNU Affero General Public License is a modified version of the ordinary GNU GPL version 3. It has one added requirement: if you run a modified program on a server and let other users communicate with it there, your server must also allow them to download…
Stats as on 05-01-2021:
•
•
•
•
•
•
•
•
•
•
•
•
We hit a million users, thanks for all the spam 🥳
•
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
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
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
• 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