CryptoAlgo

@OlshaMB Great to hear from you! Looks like this issue has already been brought up before: #119, so I'll be closing this to continue discussions there. @12944qwerty has been giving...

This appears to be yet another issue related to SwiftyGif not being so swifty after all. I might have to implement a more performant implementation using CoreGraphics directly.

@ErrorErrorError That's interesting, it like a good alternative to replace both `CachedAsyncImage` and `SwiftyGif` 🤔. And it even has first-class SwiftUI support. I will consider refactoring with Nuke in a...

@ErrorErrorError I dug deeper and it appears that we are back with the same issues as before. Nuke is a performant _image loading_ solution, but out of the box it...

After throwing together some quick code to use Nuke instead of `CachedAsyncImage` to evaluate its suitability, I have come to the conclusion that migration isn't worth it as it actually...

I've noticed this bug while using Swiftcord myself, and after some debugging it turns out that the issue is way more difficult to fix than expected. Turns out, images directly...

Hi there, thanks for opening an issue! Unfortunately (or fortunately), this isn't a bug. Swiftcord defaults to handling a channel as a text channel if it's type is unknown, as...

This issue will serve as a stub for implementation of new channel types. I'm mainly looking at forum and stage channel types for now.

This will be partially resolved by #163. Big thanks to all my contributors!

Thanks for this contribution! It's fine that the read state doesn't get acknowledged as that's a limitation in Swiftcord itself. I'm reviewing the changes, and a few screenshots illustrating the...