[Meme] Stay at home everyone
https://redd.it/fo5h8h

by @programmer_humor

Finally got the new server up and running.
having a newer CPU with more cores, double the RAM, and most importaintly finally SSD. Two of them actually.

Migrated @JoinCaptchaBot to the brand new server.

This means it should now run fast and be quick to respond again.

Note, I dropped unprocessed events so it won't bother with people already left hours ago.

All the other bots will be upgraded as well, roughly over this week, whenever I have free time in the evening.
Sorry for any inconvenience caused by this.

#JoinCaptchaBot #migration

Ever felt the desire to build nice menus for your bot but it was just too big of a struggle to write all that state management logic yourself?

Here's a sneak peek on something I'm currently working on.

In the end defining a menu is pretty easy.

Quickly moved @anonymize_bot, @HeyAdminBot, @PermalinkBot, @ponbot (+ 🔞@p0nbot) and @RpAliasBot to the new server, as those didn't need any database migrations, as they simply don't have any database.

#migration
#anonymize_bot #HeyAdminBot #PermalinkBot #ponbot #p0nbot #RpAliasBot

In case you're using @RpAliasBot you have to re-register any of your clients, so they use the new server.

That is because for data protection sake I don't store anything about your registered bots,
not even the fact that I'm running them.
Only telegram knows that, and my server in the short milliseconds it's processing telegram's incoming updates.
Therefore I sadly can't automatically migrate them for you, I appologize for the inconvinience.

If you care for technical details: The prefix you set, which is the only data it needs to know, is stored all in the URL. Therefore my server will know it only when telegram calls it, but doesn't need to keep it around for itself. The benifit for you is privacy, and for me that I don't have to store anything which keeps the costs low.
#RpAliasBot

Permanent link to the file code/rp_alias/main.py.

https://4458.rocks

Because z0r.de/4458 with Flashplayer gone ain't no fun.

Fixed @HeyAdminBot getting stuck on some special message types and becoming unresponsive.
#resolved #HeyAdminBot

Took down @RulesRulesBot to move it to the new server as well.
Somehow I did miss that one.
#ongoing #RulesRulesBot

Restoring the database backup of that bot for some reason brought down the whole database, so some other bots might be affected.
#ongoing

Everything is back up and running again. With that @RulesRulesBot now finally is on the fast new server.

#resolved #RulesRulesBot

Maintenance: Moving @BanWarnBot to the new server.

Okey going through the same procedure for @BanWarnBot now, hopefully without the database breaking this time.

Turning the bot off for moving the database, so any /warns send in the meantime shouldn't get lost. As soon as it's on the new server it should pick up those, and carry out the needed actions.

I'll take @BanWarnBot down in 10 minutes. Other bots should not be affected.

#maintenance #downtime #BanWarnBot

@BanWarnBot is now successfully back up and running the newest version:
Here's a list of what's new:

New /kick and /ban commands:
Just like the /warn one, but immediately removes the user from the chat, either once or permanently.
You can specify a reason for why you kicked/banned someone after the command.
Those kicks count into the normal warn count, because they are kinda like special warns.

Those 3 commands, /warn, /kick and /ban now also allow the first thing after the command to be the id of a user, in the format of #1234, or a user mention. This can come in handy if you don't have a message to reply to.

Overhaul of the warning lists:
Now the list of /listwarnings and /listallwarnings will link you to the message warn message, if you press the date stamp.
Also support for distinguishing automatic kicks/bans and manual kicks/bans has been added.

#update #BanWarnBot #resolved

Here is an example how that /listwarnings log could look like in action. Note, the limits were changed to 5 wanings before kicking and 10 warnings before banning in that group. #BanWarnBot

Fixed a bug where @RulesRules would hang on processing a special type of message.
Should now be responsive again.

#update #resolved

Quick heads-up, @BanWarnBot currently says 'User unbanned.' instead of 'User kicked.'
So far it looks like it's just the wrong text displayed though. I'll switch it out with the next regular update.

Should there be a problem, don't hesitate to contact me.
I might not respond the same day, but I'll read your messages eventually.