In general, please follow Contributing Feature Requests when filing feature requests. We have no plans to expand on tokens beyond T11217. They are a lighthearted and frivolous application. I'd recommend un-installing it if it is causing user confusion (you wouldn't be the first install to do so).

As I noted in T11217, this isn't exactly a duplicate. Tokens today are created with a class (tokens-coin-2 above) in their <span>. I don't see why title="Piece of Eight" couldn't also be added to that tag.

T12000 isn't really a duplicate. It's more of an enhancement for today's tokens. Of course, it'd be useful for this eventually, too, but that's tangential.

Token added for effect. ;)

This doesn't seem to be going anywhere too fast so I'm just going to nuke it while I'm combing through old things rather than letting it collect dust forever.

I did order an iPhone 7 plus, so I'll have a better understanding if 2x is actually noticeably bad.

This isn't like something I'm looking for immediately, btw. Just like, next time I have to make 50 images.

I'm also not sure if we can use SVG as a data: URL in CSS. It probably should work, but if it doesn't we'll have to rasterize (and, I guess, serve 5+ different sizes to every user).

Alright -- we can have bin/celerity map rasterize SVG into arbitrary sizes if I'm not comfortable serving SVG directly from Celerity.

I'd like to generate 1 image and have them work 1x, 2x, 3x, etc or any size I need. I can't think of any other long term solution.

(That will give us slightly bad scale-downs on 1X screens, but I bet they're not worse than scaling down an SVG would be.)

I think we can just do 2x in all cases for these, if that's reasonable?

fwiw, I want to convert all bitmaps to SVG if possible, so we can skip building 1x and 2x images.

Don't know if D16178 is worth comandeering? But feel free.

This one is a little scattered, so let me know where I can fill in any gaps. Most of the details are in D16178.

I'm going to merge this into T10448, which discusses limitations and improvements to the mail tags system. This is an example of a cross-cutting tag ("No Application/System Settings") that isn't handled gracefully by the current system, but correcting this and other similar issues is a goal of future work.

Something representing a prison, quarantine, or really good fence? I'm also a fan of the spooky ghost.

shruggy_ghost

haha i was just thinking the same thing with the spooky haunted file task.

Some kind of ghost would be good too, but not too snapchat-ey.

next batch is ready, should land tonight:

Nope, it's a hardcoded app right now, see T11217

Is this not a modularizable thing?

First 16 are done and out for review. Next 8 are sent off to the designer, should have them next week. Can explore another set of 8 if needed after that.

We need a platypus. It is objectively the best animal.

Humbly suggesting any/all of the following: gun, bomb, skull and cross bones. I find that I type :skull: :gun: on slack a lot (a common side effect of support ops work.)

These will be images in Phabricator, not emoji.