how to avoid api spam when sending "mass dms"
Occasionally (like twice a year maybe) my friend organises a kudoboard for the content creator he mods for and he always painstaking DMS like 50 people with the link to it because he obviously can't post it in the server announcements where the content creator would see it immediately.
So I wrote a command for him that accepts a list of user mentions and a message and then sends that message to all specified users.
Since the topic came up in #general I wanna ask, are there any features I should implement like a short wait time after every DM?
7 Replies
- What's your exact discord.js
npm list discord.js and node node -v version?
- Not a discord.js issue? Check out #other-js-ts.
- Consider reading #how-to-get-help to improve your question!
- Explain what exactly your issue is.
- Post the full error stack trace, not just the top part!
- Show your code!
- Issue solved? Press the button!
- ✅ Marked as resolved by OPno
you shouldnt mass dm
I just called it that
There is no difference of dming 50 people by hand Vs with a bot
And rather that he wasted time sending it a bunch of people by hand I'd rather have him type a command with the mentionables and the message once, even if that command sends one DM every second, it'd still save him time
doesnt matter
mass dm is against to tos
it doesn't matter why you did it
Tldr it doesn't matter if the result is the same and ure sending the same API calls anyway, you just have to do it by hand just because?
both against the tos already?
like there are of course many more people on the server, but the goal isn't to notify everyone, since, as it goes on twitch many people just follow or join a server but aren't actually regulars. (and then it would totally just spam them)
since it's for something like organising birthday surprises with the regulars in a way the streamer doesn't notice, consent shouldn't be a problem.
Though I'll ask him if he can add an opt in role or something like that.
delay also isn't a concern, it's just about reducing the workload for tedious organisational tasks like this, I just wanna avoid annoying the api.
Thank you!