gocord VS discordgo

I want to be clear that this is still a hobby project, and with exams and other commitments I will not be working on it nearly as much as I did with Grank. However, I still hope that while the project is nowhere near a stable release at the time of writing this post, someone, somewhere in the world will find gocord and have fun using it. Because in the end, that’s the only thing I want from my programs.

You could try building off of DiscordGO, just like dolfies did with discord.py. Glad to see you back though

I don't think that bot exists yet, but it wouldn't be too hard to make. Use some Reddit API wrapper (snoowrap is very good), pull a post from there, and you're gonna have to post it using this golang library because base discord.js still hasn't implemented posting to forum channels, as they are still kinda new.

Interesting. Always nice to have competition, but let's say I currently use https://github.com/bwmarrin/discordgo, what does your library enable that theirs doesn't?

What? This package has its own documentation, here. And it's open-sourced, so you can ensure that this package doesn't spy on you and compile it yourself.

In this first part of the main function, we have created the fiber HTTP server, and the creation of the /sendFile route. When this route is called, passing the file field, we have the creation of our discord bot using this excellent library called discordgo. We also open the WebSocket to talk to the Discord servers.

The stream is about programming the game, and helping others to make their own Discord applications. So far, we've had a Python user and a JavaScript user tandem-code with us, as well as two Golang newcomers. We're using the discordgo framework: (https://github.com/bwmarrin/discordgo.

Can you please elaborate why I should use this instead of discordgo?

Was that the right hyperlink? I think you meant https://github.com/bwmarrin/discordgo not https://www.washingtonpost.com/world/2022/03/06/venezuela-american-officials-visit/