Detect asset pipeline availability about html-pipeline

[atmos]

Is there any reason this stuff can't be cached in akamai sanely and just shared with everyone?

[jch]

That'd be useful for most projects, but would give the SSL insecure elements error for some projects. GitHub projects should definitely use the same assets though.

[atmos]

The urls can be hardcoded and delegated to akamai without camo integration and knowing about SSL.

I almost wish we didn't have secret keys in camo. We can't trivially evict shit out of akamai, we can just update the key but tons of older cached links will still live on. :\

[jch]

But when this becomes opensource, we'll want to give users the option of how to serve assets. Since emoji is the only case, I think it's ok to leave it hardcoded relative to the gem and not support the asset pipeline until someone asks for it. Vote to close?

👍 for asset pipeline support, because as it is now my heroku app is serving static assets (for the emoji filter), instead of having them automagically cached by cloudfront.

PS the asset pipeline instructions in the gemoji readme are out of date.