Hacker News new | ask | show | jobs
by stock_toaster 3044 days ago
> using emoji as "media" was forbidden, but "content" was okay. Whatever that means

From what I read other places, it meant that if it was non-variable and shipped with the app (UI, app data, etc) then it was "media" and not ok. If it was user supplied (like a text message), externally loaded (web page), etc... then it was "content" and ok.

1 comments

So if a users presses a button that says "Do X":

Then the app sends a request to a server to do X and based on the response looks up the text that shipped with the app saying "X completed successfully" which it displays using the system font, that is fine.

Then the app sends a request to a server to do X and the server sends back the text "X completed successfully <smiley-face-character>" and the app displays it using the system font, that is fine.

Then the app sends a request to a server to do X and based on the response looks up the text that shipped with the app saying "X completed successfully <smiley-face-character>" which it displays using the system font, that is against the rules.

That seems incredibly arbitrary and nonsensical if that is an accurate description of the rule.

The minor use that occurred to me is Slack's "You're all up to date :tada:" when you pull up at the bottom of a channel to load new messages.

Another link was posted suggesting that Apple's reversed this stance. If not for that, would Apple have been making Slack get rid of the party popper because the user didn't type it? It sounds like yes.