We can't bring back the old emojis. Why the attachment to them? For my personal taste, both versions suck?

The old yellow emojis sort of remind me of my first FT luggage tags given during in-flight encounters with fellow FTers doing mileage runs. The old emojis also seem more removed from the emoji style I would expect to see used by a bunch of twelve year old kids. While I preferred the ASCII ones that remained in ASCII style, their successors were less “visual vomit” than the current color and design scheme for emojis. Maybe they will grow on me, but the color scheme alone has me not liking the current ones.

Given the general color scheme of the FT website, the new emojis, especially the ones with blue backgrounds, are much harder to distinguish what the actual visual graphic is supposed to be.

If you take a look at some threads, all one now sees is a field of blue in and amongst FT's blue graphical elements.

David

Are we getting any closer to stopping the annoying auto back-scroll on the mobile website version?

:confused: seriously? They're just image files. I saved the old ones if IB actually deleted them all, would be happy to supply them to you. There is zero technical reason why they can't be brought back.

Probably most of us are somewhere on the spectrum and hate change :o :p but vaguely seriously, the old ones had a certain aesthetic that were arguably crude but semi-intentionally so, whereas the new ones just look goofy as I mentioned upthread.

I could flip the question back and ask why someone at IB thought this was something that was so important to change, vs. any of the other technical issues and wish list/feature requests FTers have asked for. Why are the new ones obviously better?

:D was one of the post popular here when it was yellow, but green = puke

I was thinking the same thing! For me personally, green is associated with the vomiting emoji. But maybe being green with happiness is a new thing :D 🤢 🤮

Not sure how new this is because I don't often scroll down this far, but in mobile skin at the bottom of this page
https://www.flyertalk.com/forum/usercp.php​​​​​​

Seems some debugging output may have been left in accidentally :)

https://cimg0.ibsrv.net/gimg/www.fly...b5a7458b72.png

Can you provide an example screenshot?

That’s just silly. Of course you can.

My biggest issue is, as explained above, that the “new” emojis are so … different … in many ways from the ones they’ve replaced that they essentially no longer necessarily represent the nuance of feeling that the poster intended when posting the “old” emojis. It’s not as extreme as changing every “smiley” to a “frownie” would be, but it’s enough of a difference to “make a difference” to at least those of us who have complained. Based on what I’ve seen, a poll of members who prefer the “new” emoticons over the “classic” version would get about the same results as Coca-Cola’s experiment of 1985.

Thank you, reported. Also, any particular reason you personally saved the old emojis?

When the new ones rolled out, it seemed like there was a transitional period where I sometimes got the new ones and sometimes the old ones, and since I hated the new ones I figured I'd hang on to the old ones just in case.

And TBH in my spare time I'm working on userscript that fixes broken embeds, and "use old emojis" seemed like it would be a useful checkbox too (if I'm feeling ambitious, there may be dark mode too...)

This (and I admit that my eyesight isn't the best). If I am looking in low light I have to either put on reading glasses or look very closely or hover over for the word to appear. It is not the end of the world but why make things harder? If it ain't broke......

https://cimg5.ibsrv.net/gimg/www.fly...4ace3d1f3a.png https://cimg4.ibsrv.net/gimg/www.fly...3ff941c17d.png

You tell me which one looks better.

-J.

There is at least one “email protected” error still showing in my posts. I haven’t cared to see if that is the only such instance in my posts, but this indicates that at least one of these non-email @ shorthand phrases didn’t get fixed and maybe the problem will pop up again in the future.