Welp, time to rewrite entire Discord bot due to new Terms of Service.. Life is good, right?

What is your bot doing?

What has changed and why do you have to rewrite your bot?

Welcome to devRant!

I'm having to rewrite mine to support shading pretty soon. Looking forward to that...

Probably not. They revised the terms a few days ago. I develop FredBoat and I don't see how it breaks the terms, even as it logs messages required for operation without consent. You also no longer need to encrypt user data, just use reasonable security.

Also, rewriting your bot to support sharding sounds overkill.

*tactical dot*
.
I'm writing a Discord bot too.

Hey, fellow discord users! Are you all in devRant discord?

@redstonetehnik I'm not, but I would like to 😀
And I would also like to hear how is your bot breaking the new terms of service...

My bot saves chat and such without consent currently, and saves it in pure text format instead of any form or encrypted text.
I plan on rather using PGP keys and messages for encryption now, and I'll have to make it automatically require you to either consent with saving or get kicked.

@Frederikam since when is no encryption "reasonable security"?

@Frederikam I'm using the Discord.py library. The library is being rewritten right now, and the rewrite has auto-sharding in it. I'd rather just rewrite it to support the new D.py lib rather than put sharding in what I have now.

@chilledfrogs and everyone else: https://discord.gg/puMNVsU

@endor I would consider it to be reasonably secure if you can only reach the plaintext logfiles over SSH or sFTP. It's not like you're storing passwords, person data or credit card info.