Sounds like an abusive relationship. Just dump him (Discord).
Re:On resuming discord.py development
by charcircuit on Saturday March 05, 2022 @10:07PM
(#30574660)
>break very soon by Discord shutting people out?
Discord is not shutting people out. They just aren't going to keep legacy versions of the API around forever. Especially when newer versions provide security benefits. Discord as a platform is constantly evolving so it makes sense that its API is too.
“Security” benefits. Based on the original problem, that’s really only true if you are Discord.
A bot that cannot read messages is a lame duck.
Re:On resuming discord.py development
by Madmallard on Saturday March 05, 2022 @08:52PM
(#30574208)
>but Discord is still going to shit the bed very soon
?
Re:On resuming discord.py development
by sergiotapia on Saturday March 05, 2022 @08:56PM
(#30574236)
All of the reasons he quit for originally haven't changed.
Re:On resuming discord.py development
by QuikAccount on Saturday March 05, 2022 @09:39PM
(#30574499)
If you believe this means that Discord is going to die as a platform, you are probably in for a rough surprise.
Re:On resuming discord.py development
by Dylan16807 on Saturday March 05, 2022 @09:55PM
(#30574591)
That's a weird interpretation of "shit the bed" you have.
It's just going to be a giant problem.
>I attempted to discuss the impact of the decommission with Discord, and while they acknowledged my concerns, they gave me no guarantees that the decommission date would be postponed. discord.py remains the 2nd most popular library in the ecosystem. If the decommission goes ahead as planned, it will be a far more catastrophic blow to the ecosystem than the original privileged message intent requirement. In order to minimise damage of this change, I felt like the library needed to be updated.
Why does he feel the library needs to be updated if it will again break very soon by Discord shutting people out?
I don't get it.