Support » Plugin: Compressed Emoji » About your plugin

  • Ramanan

    (@superpoincare)


    Hi Mustafa,

    Looks nice.

    Can I suggest a change in the name? “Compressed emoji” is not the best name because there are some tickets at core where this request has been raised.

    Second, your plugin localizes emoji and that itself is a huge feature. You might want to call it local emoji or something (a plugin with a similar name already exists but not maintained).

    Also I don’t see cache headers being added by your plugin. W3 Total Cache currently has svg max-age set to that of HTML and not of images, so you might want to add that. So if I use your plugin and W3 Total Cache, Google pagespeed will still complain because max-age is low.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Mustafa Uysal

    (@m_uysl)

    Hi @superpoincare,

    Sorry for delay, I didn’t get notification via email.

    Can I suggest a change in the name? “Compressed emoji” is not the best name because there are some tickets at core where this request has been raised.

    I can’t change it.

    Second, your plugin localizes emoji and that itself is a huge feature. You might want to call it local emoji or something (a plugin with a similar name already exists but not maintained).

    Yes, https://wordpress.org/plugins/wp-local-emoji/ already exist but I’m not sure it’s abandoned or not. Plugin’s name is not a big deal actually 🙂

    Also I don’t see cache headers being added by your plugin. W3 Total Cache currently has svg max-age set to that of HTML and not of images, so you might want to add that. So if I use your plugin and W3 Total Cache, Google pagespeed will still complain because max-age is low.

    I think you can use server’s feature to set max-age?

    Cheers,

    Ramanan

    (@superpoincare)

    Hi Mustafa,

    I can set it myself but I was speaking from the point of view of all users, not just me.

    Also, I just observed that WordPress is now serving emoji via http2 and also that it’s gzipped.

    Plugin Author Mustafa Uysal

    (@m_uysl)

    Hi Ramanan,

    Also, I just observed that WordPress is now serving emoji via http2 and also that it’s gzipped.

    Yes, it’s true. s.w.org has been switched to a new CDN 😉

    Ramanan

    (@superpoincare)

    How do you the CDN is changed? Any announcement? I think they just added headers to gzip compress the emoji and have upgraded to http2.

    Plugin Author Mustafa Uysal

    (@m_uysl)

    I don’t know details @pento commented on tavern

    Ramanan

    (@superpoincare)

    Thanks. Saw his comment.

    That’s the reason I mentioned you may have changed your plugin name to localized emoji or something else. I had mentioned to pento on trac whether it’s possible to do that and he raised a ticket based on my request and I knew it was coming (the http2 and gzip part).

    Local emoji has the advantage that emoji are self-hosted, so for someone interested in privacy concerns it may be useful.

    • This reply was modified 12 months ago by  Ramanan.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘About your plugin’ is closed to new replies.