On resuming discord.py development
gist.github.com
gist.github.com
And zero profit nor viable plan to generate any. That's the problem.
There's no money to be made in being a message bus, certainly not enough to justify such a valuation and sustain hundreds of employees (whether it needs those is a different matter, but that's out of scope).
Discord's current business model is "growth and engagement" - this is what netted them their current funding and valuation. This requires keeping the audience captive and being able to regulate their behavior, including coercing them into doing things against their interests such as seeing ads, navigating through dark patterns, etc.
Having a healthy developer ecosystem goes against this - it means you become a dumb message bus and people will be able to automate their way around any inconvenience you might put to monetize them. Developers are great when you've got a real business providing a real product people pay for, but when your only bet is on the "attention economy", the last thing you want is to have "smartasses" around that can create technical workarounds to your inconvenience-based business model.
What do you mean? You can literally link to an image and Discord will replace that link with an inline image. And with opengraph Discord will embed youtube videos and twitter image and videos right into the chat.
I just hope it's viable when you're taking VC money.
They went from 5 Million revenue in 2016 to 120 Million in 2020. That's very far from zero or a lacking plan. The money is coming, it's just has not grown enough yet.
This gist doesn't really help my view of the scene, it confuses me more and adds to the drama. The changes look great, the future plans look great, but discord.js already had (at least) slash commands and better documentation. Staying with js seems safer, more time efficient, and more drama free to me at the moment even if it's a bit awkward.
Discord is a company that seems to just fly by the seat of their pants. A great example would be "threads", for which they rolled out with no notice to server admins - it just suddenly appeared - and worse, threads were rolled out before thread-related roles were.
Even worse: threads created before the roles were updated to include thread roles could not be deleted by server admins/moderators.
The mind boggles that such a large company, presumably full of very qualified and well paid engineers (and likely piles of "UX" people) could generate such a clusterfuck.
Another great "feature" of discord: blocking someone, unlike every other platform save IRC, does not hide your content from them. It hides them from you.
Discord gets to move fast at some expense to the users, but mostly those users do not care, as long as messaging/voice chat functionality isn’t impacted.
Blocking a user so you no longer see their posts is a long established feature of various web forums, chat systems, and comment sections. I do not know how you would come under the impression that the reverse is true; the only platforms I know of where it is, is the four or five social media giants. People do complain about Discord blocks, but they complain about them because there is still a 'N blocked messages' indicator, not because of what direction the blocks go.
Not sure what point you're making here. The equivalent of a "block" that goes the other way is kicking or banning the user. That works the same on IRC.
Could you expand on what you mean, please? Genuinely interested.
In my experience on the discord.py server, I had recently come back to discord bots after a couple of years and wanted to try slash commands and was told: "slash is trash", discord.py will never support slash commands (lol), the gist on the issue is SO OBVIOUS and easy to find just google it (it wasn't), talking about forks and other bot libraries is against the rules (wtf?), and this was all served with mild verbal abuse. It was also served while at least 2 people were asking if they were allowed to ping Danny to express bizarre levels of affection and they somehow got more positive traction than me trying to understand why this advertised API feature wasn't available in what I thought was a highly popular/respected library. Looking around the other channels had me cringing a bit on conversations and shared media to put it lightly.
Sometimes going to a discord server feels like entering an online shooter voice lobby. If you try to be serious you just get talked past or berated by loud 15 year olds. If they even say something related to what you're trying to talk about, they're mindlessly parroting their idol and not thinking critically on their own. These servers often have a handful of active people forming their own little social club with hundreds or thousands of other members on the side never saying anything, probably not even lurking. This is something I've noticed a lot on Discord but I imagine extends to similar solutions in the same space. My experience on Slack has been less juvenile but also less populated and similarly useless.
Anyway so mix that experience with the "I'm quitting" gist (which is something I can write a few paragraphs on but really don't want to) and yeah I wouldn't want to work with these people if I were a boring corporation, and I don't want to think about them when I'm doing a fun side project for friends.
[0] https://discord-py-slash-command.readthedocs.io/en/latest/
> the gist on the issue is SO OBVIOUS and easy to find just google
I also have a deep resentment against people telling me to just 'read the docs' (especially the LMGTFY links). It gives a really bad first experience like yours, even more so when you've already looked it up before asking. I understand the contributors being constrained, however it's very important not to be blatantly rude to people. Very tired of this attitude in FOSS in general (I never do it when people ask about my projects).
> These servers often have a handful of active people forming their own little social club
That lines up with my experiences in the Discord API server, too. It's very ostracising.
As an aside: the state of the Discord API server is quite something. It's not "offical" per se, but it basically is (even Discord link to it). Almost like they want the benefits of an "official" room while also keeping it at arms length. Perhaps it's due to the experiences you describe above.
Regarding pseudo-official servers, I imagine Discord wants a beat and handle on the community but ultimately the way the business has to move and make decisions is not compatible with how these people behave in public.
I only briefly looked at discord.py and left with the exact same impression. A lot of angsty energy. Felt like everyone was fighting with each other and Discord itself, with a heavy dose of martyrdom.
Fortunately none of the other Discord libraries I looked at had anything remotely similar.
What's the issue with it?
I'm not clear on the details but if you aren't currently using slash commands you may be forced to in the near future so if you have any operating bots responding to custom prompts you should look into whether you need to do some work or not.
Now on what library to use... there have been various discord.py derivative projects to provide slash commands and now discord.py apparently supports them too. Personally I'm avoiding discord.py, I can't trust they'll continue development and I'm not trying to track community drama via discord. I also really dislike node. My solution for now is discord.js as a thin layer between discord and python.
I can't really say I'm surprised, however. It seems like it's mostly always been this way with constant whining or drama from them when things didn't go their way.
> I was hopeful that after half a year that there would be a clear alternative library that most users can transparently migrate to, but it seems that this never ended up materialising.
So I think the author agrees it would be nice if the ecosystem kept moving forward.
pycord is a fork. Why didn't the author of pycord start a new project? I think the author of the article was hoping for a new project that isn't a fork.
Isn't that kind of the whole point of open source?
None. It's open source.
I don't really know if this is a good thing. Going by his own account as quoted above, Danny's leave doesn't seem to have affected much at Discord. You'd think Discord would have reached out to him after he published his initial Gist and tried to work things out (including releasing a public apology). Especially since, as he said, the Discord.py library is one of the most popular libraries for Discord out there. I obviously don't have the numbers, but the amount of developers libraries such as Discord.py have brought to Discord must be in the high thousands. Why are Discord not treating this with the urgency it deserves?
Have I just come to expect too much of companies these days?
The point made by the discord.py creator elsewhere is true: this is more likely to happen with invisible self-bots than bot-bots. But it would be far more catastrophic if it happened with an actual bot, since lots of small, private servers and channels make use of those. It's the difference between leaking things most everyone involved kind of already knew they were broadcasting publicly vs. potentially leaking enormous amounts of data that everyone involved assumed would be private because they didn't consider the scenario of a popular bot secretly spying on them.
This is one of those counterfactual scenarios where everyone would be furious at Discord if this happened and they didn't take steps to prevent it. And frankly, it seems quite possible it already has happened but the bot owner has just been using the data for some nefarious intelligence or profit purpose and has no intentions of burning their trick by leaking anything.
People tend to be quite nonchalant about bots in private channels, in my experience. It tends to be taken for granted that they're not hoovering up all the messages. I'd go so far as to say we need a data catastrophe like the one you described to wake everyone up. A music bot does not need read permissions in your private staff room! I took over administration of a server which did so and quickly clamped down on the permission of bots.
Another problem is User bots - ie. clients that look like a regular user but are still doing bot stuff or simply ingesting all messages they see, which is easy since Discord's client implementation between bots and users are almost exactly the same. They could have used some wasm/javascript virtual machine thing that would make it hard to figure out what the Discord client is doing and would make it harder to sign in to Discord via a user bot, but then we'd probably have another set of HN users complain about Discord hiding stuff from users or something.
Some administrators set their server up to create a temporary holding room for new members and ask them to add a reaction to a message, or do a CAPTCHA, but that still falls apart if someone does all that manually then uses their account as a bot. If you're interested, there are plenty of readymade bots (heh) that do all this verification stuff, and they are quite popular.
You could also prune inactive members, but again the user account could just say something every now and again, plus any real users who find they have been kicked out for not participating might not be particularly pleased (or might just forget about your server altogether).
My point in the above message mainly focused on bot accounts. It's best to operate at the principle of least privilege. You don't need a music bot to see your staff channels, for example. Keeping with that example, some administrators take the time to limit music bots to a specific music channel. For that, I applaud them. There are simple ways to limit the data bots can get, which mostly rely on common sense on account of the server administrator(s).
Garbage in, garbage out. Why won’t popular bots spy on you? I doubt if these bots even have a privacy policy.
There's no way people could invite CoolMusicBot to their private chat and have any expectation of privacy...
>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.
?
It's just going to be a giant problem.
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.
A bot that cannot read messages is a lame duck.
The API of telegram is awful, how is it even possible to provide a worse DX than that? At least discord seems to have proper OAuth2.0 support lol [1]
[1] https://core.telegram.org/widgets/login#receiving-authorizat...
Telegram is definitely not the worst, in fact, it's the best on that list depending on what you want to do.
Slack's real-time API has been deprecated since forever, leaving you only specific slash commands that hit web hooks, which does not allow for rich engagement of content or anything close to being as dynamic as the old IRC bots used to be.
Teams is a joke when it comes to bots. Seriously.