Description
While emoji can be successfully saved to postgreSQL, they cannot be successfully or safely passed through Djangos slugify() code - while emoji can be used as part of a URL see this obnoxious example...it is still frowned upon, and Djangos code doesn't tolerate it.
If a tag is entered that contains only emoji, Django assigns either blank space, or an underscore plus a number to represent the "slug" of the string of characters:
Emoji inside a string is simply dropped:
Similar problems arise with ASCII image characters:
Because of this, we need to put validation code around tags, and fail tag strings that include emoji or other ASCII / Unicode "image" characters.
@lpatmo - we definitely need to do this for the backend, and probably should also do this around form/entry validation on the front end.