-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluent Emoji: Twemoji drop-in replacement #611
Comments
The twemoji were free for any commercial purposes. Is this the same with fluent-emojis? |
I‘m glad to meet someone who shares the same ideas as me. 😊I also have a project on a similar topic, and I’m really proud of it. Here’s the link if you’d like to check it out: https://github.com/DellZHackintosh/msemoji. |
Yes: |
The Twemoji graphics are licensed under CC-BY 4.0, while the Fluent Emoji repo provides them under the MIT license. These are both permissive licenses; the kind of attribution they require varies slightly (I am not a copyright lawyer) but this is probably not likely to matter for most users. |
While Fluent Emoji is also nice, if you want to use the same design, you could use the forked Twemoji. X Corp. abandoned this opensource development (the official Twitter account for OSS was also deleted https://twitter.com/TwitterOSS) but the latest Twemoji is still actively maintained and updated by former Twitter designers and Discord/WordPress designers on the fork repository here: https://github.com/jdecked/twemoji This article explains the recent development of Twemoji:
|
Hi all,
I've packaged Fluent UI Emoji (by Microsoft) for us in browsers, and have included drop-in functionality to replace Twemoji in light of the Twitter layoffs/MaxCDN shut down.
More information about the library is available here: https://github.com/AdvenaHQ/fluent-emoji
No re-work is required. You can directly use
twemoji.parse()
with this library just fine. Note: the emoji themselves look different to twemoji, but apart from that, everything is the same.The text was updated successfully, but these errors were encountered: