We write the needed functions for wslay which use the homebrew SDK's TLS, and our HTTPS library. Wslay is a WebSockets library that uses callbacks, this is where you give functions for wslay to use to access things like TLS and HTTPS. I used my own, as libcurl isn't available though the homebrew SDK. At first, I used the HTTP library that was part of the homebrew SDK but Discord would reject it a lot. Those being the ones that rely on the internet protocol or sockets, so WebSockets, and HTTPS. We'll need a module for the 2 protocols that work differently on different platforms. My library was made to be modular, so I used this as a test to see if modules can add support for strange platforms. Discord updates their API sometimes to add features that can break your client, so you'll need update the library and client when that happens. You'll need to modify them as they generally don't support custom clients. Unless, you are very familiar with the APIs, I recommend using a Discord library. I've made a Discord library for bots, not clients, so I used what I made. These protocols also use other protocols, such as TLS and TCP. The main protocols being WebSockets, HTTPS, and JSON. Anyway, you'll need to understand the Discord API and it's protocols. I generally only use the client with a bot account. Firstly, I need to say that doing so is against the TOS if you are using a user account. I've been getting messages asking how to make a Discord Client. Skip to 5:33, if you want the relevant info. I don't want to shamelessly plug my newer work, but in case you want to know, I'm currently working on a Discord bot and my own online multiplayer video game now. As for this client, I don't think Discord, the company, will want it or any custom client to continue. There are people using my library to build stuff on the switch as well, and I hope they'll continue to work. I'm not going to stop doing stuff with Discord, I'm still working on the Sleepy Discord library that this client uses. I also want to thank the people that used my client. I also want to thanks everyone that helped with the details of doing networking with tcp and tls on the 3DS to help kickstart this project and those that helped me cram the Discord client into the 3DS's memory on the first version and the one that helped me get font rendering working. It was a pretty good run I guess, but I think it's time to say good bye to Discord on 3DS. Discord wants to be more careful about what people are using the data from Discord's API for now for security reasons, and I don't blame them. Then again you'll likely run out of memory anyways but that's not the issue. Since this client counts as a custom client because it's not official and uses the API and many are using it on a user account instead of a bot account, I'm not sure if someone will get in trouble for using this while on a lot of servers as the client will not be approved by Discord. There's also now an verification process for bots that want to get server member data from the web sockets API when on a lot of servers. I've been also having a hard time keeping the client not use up too much memory and moving stuff to be stored on the SD card. The isn't a big change but v7 is pretty big. I'm calling this change the change and also the v7 change. Discord is going to make big changes to it's API sometime in November, anything that doesn't update to make sure it keeps working with the changes will stop working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |