jackellenberger / emojme-hubot-plugin Goto Github PK

idk seems like they're not

• reply to thread, not channel
• add more permissive regex
• adjustable size
• [/] see if sharp has some sharpening features
• cleanup files post-posting when they are no longer needed

• Commands

  • hubot how old is the cache?
  • hubot refresh with my super secret token that I won't share in public channels <token>
  • hubot add emoji <name> <url>
    • this might be interesting
  • hubot alias <original> to <alias>
  • hubot who made <emoji>

• Features

  • shared auth? :uhh: seems like a bad idea
  • reply with cache age here's what I have, but i haven't been updated in <age>
  • retry commands I don't know that emoji, but try refreshing my cache if you know it exists
  • tell users to delete their user token if posted in a public channel

• Design

  • keep build outputs in brain

• External requirements

  • emojme
    • save build results elsewhere?
    • set limits on download cache size? (maybe this should be handled by the bot)

https://github.com/jackellenberger/emojme-hubot-plugin/blob/master/src/emojme-script.coffee#L69 here is borken. We need to not capture the "with metadata" part.

jackellenberger/emojme#64

emojme add this to slack as :emoji: with an attachment should work

emojme add <url> to slack as :emoji: should work

emojme add this to slack as :emoji: as a threaded reply to an image should work

Slack still doesn't let you react with aliases, it just presents the "root" emoji, so emojme alias is less useful than it could be.

• add emojme clone :existing-emoji: as|to :new-emoji: to create a new emoji with the same source.

Maybe it's a bad idea, but what if you could run any emojme function from hubot through the cli? could work 🤷‍♂

we're caching tokens now (:yay: (but also :ohno:)) but you still need to find a new one like every morning because they expire after 24 hours. Tokens can live longer than 24 hours (and there's a new expire-this-token endpoint(!) so i feel less bad about storing them) so we should re up the TTL of the token on each usage. If someone refreshes the cache every morning, they should be able to use the same cached token until it expires.