emojidex

Help us update and animate our emoji and get some stickers & goodies! Check here for details: emojidex.com/campaign

After a small mixup the emojidex Chrome extension is back up on the Chrome Web Store. Thanks to the quick response from the team at @googlechrome . You can find it here at: chrome.google.com/webstore/detai…

@ivucica @Emojipedia The context being all emojidex software clients connect to the emojidex service, which hosts user contributed content and copyright information on image assets. If you replace the image assets through a modification of the client it destroys copyright protection. Still OSS.

@ivucica @Emojipedia The source DOES NOT conflict with the OSI, The assets ARE NOT "OSS" which is why our license makes that distinction and why assets and sources are distributed separately. You either fundamentally misunderstand those definitions or you're trolling us. Our sources are OSS.

@ivucica @Emojipedia You obviously felt you did or you wouldn't have. Feel free to point out specifically what you believe does not fit within the OSI guidelines and we'll forward it to our lawyer. Just don't confuse assets with source - in this case that's an important separation.

@ivucica @Emojipedia You have a misconception on dual licensing. There is a condition which must be met to choose the secondary license. For MySQL it's to pay a fee, for us it's simply don't use non-emojidex assets OR use it in OSS software. + our license was written by a lawyer who deals with OSS

@ivucica @Emojipedia As for viral nature, we chose LGPL as secondary for a reason.

@ivucica @Emojipedia Otherwise, if anyone ever has a specific question or concern about our licenses PLEASE don't hesitate to contact us for clarification. We want as many people using emojidex as possible, and we feel/want our license reflects that.

@ivucica @Emojipedia I'll try and prepare an article describing the licensing situation and what we did/how we specifically formulated our license to be as OSS friendly and compatible as we possibly could while still providing adequate and reasonable protection. I'll put a link here when I finish it.

@ivucica @Emojipedia As for citation, we got the idea from other projects in the first place. Furthermore, every GPL+ dual-licensed piece of software is technically putting conditions on the GPL applied. This is not at all uncommon or unheard of - you just need to clarify what takes precedence.

@ivucica @Emojipedia License on the actual emoji and the sources is different. Regardless; our emoji asset license is extremely permissive, but crafted specifically to protect content/creators/contributors. We had to do it this way, and we took a lot of care and time to craft the license well.

@ivucica @Emojipedia You can't just add the F there - it changes the entire argument. We're not trying to fit FSF or OSI definitions of FOSS, but that does not change the fact we are OSS. Also, take note: licensing on assets is not OSS which is specifically why assets are not bundled with source!

@ivucica @Emojipedia 1. There's plenty of other GPL software that has similar restrictions. 2. Our license on emoji is far more permissive than EmojiOne, and they are still considered "OSS". Our source is open and you are free to use it as OSS. We are OSS even if it doesn't fit your definition.

@ivucica @Emojipedia It IS an OSS license, it's just not an OSI license. We just had to take special care to preserve copyright of contributed material. The sources are LGPLv3 equivalent, actual emoji are under very permissive terms but with protection for contributors on their material.

@ivucica @Emojipedia > Sources: Under the condition that sources are only used with emojidex emoji, usage is granted to the Licensee to use all sources for Official emojidex Tools as if they were licensed under the conditions of the GNU Lesser General Public License, Version 3 or later.

@mashable Our base "hamburger" doesn't have cheese, but we have variants with cheese AND bacon... And we're now adding double burgers

@Informoji @Emojipedia TBH we're debating on one change which would add over 600 ZWJ sequences. Display would still make sense, but would add complexity to regex.

@Random_Guy_32 @Emojipedia Yes, and more to come.

@Informoji @Emojipedia No but you could cross-refrence emoji.json in the UTF folder of the vector or raster repositories against a standard list + expect more soon

@plaandrew22 @davenicolette @Emojipedia @tomwarren We'll just have to add ZWJ double burger variants in our next update then - put some pressure on "the establishment".