I think emoji names should not appear in the url. What do you think?
Personally, I don’t think emojis should be in titles to begin with as I find them “noisy” in topic lists. But that’s me.
Exactly. They are making my discourse topic list noisy too. However they make the url even worse.
I guess it’s a matter of whether or not they impart useful information. eg.
Does the “thinking” make it more clear that the discussion is about pondering the use of emoji names in URLs, or does it make it less clear? And that’s only one emoji name of many.
Perhaps bracket it in some way to identify it as an emoji name? eg. (maybe not the best choice of enclosures, but as a rough idea)
I don’t mind them in the titles (or maybe should be an ACP option - as different forums will have different needs) but definitely shouldn’t be in the URL and should not count towards min title/character length imo…
I don’t know what changes could be made without risking routing problems. Nor do I know how much work to core code would be needed.
Links work fine as long as the topic id is at the end.
and URLs without the topic id will work as long as the slug is correct
but there would be a problem if the slug wasn’t correct and there was no topic id
It’s an easy enough change we have all our “slug” logic centralized to one spot and it can be smart enough to strip
:emoji:, though it needs to be smart enough not to strip
@codinghorror’s call if he wants this or not, I am on the fence here.
I think it’s fine the way it is… and honestly when a topic title is
I rock and roll
which transliterates to the slug
that’s basically correct…
Even this example does not make full sense.
Sure it does, I would like to enter in evidence, if it pleases the court, this following video recording
It says “I love rock and roll” not heart. Ofcourse it makes sense but this is one of the few emojis that results a meaningful slug.
On the other hand, we are only considering English here. What about other languages?
for example If I create a topic like
انا روك اند رول
It would generate the following slug
In Arabic though you would probably enable encoded slugs, no?
I have never found a good user experience with encoded slugs. So I mostly don’t enable them. Having raised this issue,I would like to say that we are still missing customizing slug feature.
Wouldn’t this be a case for a plugin that uses localized emoji short_names?
Unicode provides TTS descriptions for plugins, for example (Spanish names):
cara de vaca
búfalo de agua
cara de cerdo
nariz de cerdo
As far as I can see, the only potentially serious concern might be having in a title that might cause a flag for an email client.
Granted, there are many emoji names and an infinite number of possible topic titles. But although the emoji names could make it more difficult to understand the title I can’t think of any combinations where it would render them indecipherable.
Yeah localization is a major argument in favor of not doing what we’re currently doing.
I would say at least for non English we should stop doing this, can be built into the slug class
AFAIK slugs are for SEO purposes since the topic id is always used at the end.
So you need to ask, what is correct for SEO purposes. If the emoji is part of the content then it is relevant. Otherwise it is not and it hurts SEO.
Would it be that emojis at the beginning and very end of the title are usually not part of the content, while emojis inside the title sometimes may be?
Why doesn’t show up? A regression?