License

[fakerybakery]

Hi,
Thanks for releasing this library! Would you mind adding a license, ie MIT or ISC?
Thank you!

[BoogieMonster1O1]

Any update on this?

[cryptoAlgorithm]

Sorry for the delay in responses, been very busy with other projects and the next version of Swiftcord lately. I'm considering an MIT license, but don't take my words as a guarantee just yet. I'll have to see if it's the most suitable license for us, as well as being compatible with that of the new Swiftcord.

[fakerybakery]

Thanks!

[WeetHet]

Sorry for the delay in responses, been very busy with other projects and the next version of Swiftcord lately. I'm considering an MIT license, but don't take my words as a guarantee just yet. I'll have to see if it's the most suitable license for us, as well as being compatible with that of the new Swiftcord.

Please, don't. MIT is terrible because it allows corporate takeover. Please consider dual licensing GPL and a commercial license so for-profit corporate projects using this would be obliged to pay you money. This is better for everyone, as enthusiasts would still be able to use this in there projects and your work won't go underpaid

[fakerybakery]

I’d actually like to support MIT since it allows integration into apps, while still requiring attribution. For the Swiftcord app itself GPL makes sense but for libraries MIT doesn’t require linked software to also be GPL licensed

[WeetHet]

I’d actually like to support MIT since it allows integration into apps, while still requiring attribution. For the Swiftcord app itself GPL makes sense but for libraries MIT doesn’t require linked software to also be GPL licensed

What's the problem with dual licensing with a commercial license? It still allows writing software with whatever the license you'd like while ensuring that the author gets paid

[ImTheSquid]

Most libraries for Swift are MIT licensed, and putting this under GPL would just lead to no one using it. Corporations won't pay for this, they'll just use a different library that is MIT licensed or use Discord's thorough API documentation and make their own. I have forked this library and added features to it, and I'd like to be able to use it in apps. However, if it is GPL'd I'll just write my own library that does what I want and make it MIT, and I don't want to do that when DiscordKit is already great and does what I need. I do agree that Swiftcord should be GPL'd as it is a larger, complete product and is worth protecting more strongly.