Incubator » CB Activity

This should be nearly entirely powered by JS. Then just have a parser that converts a tag into a gyphy link. For example ((xUA7beks3SyvH5a9mE)) would convert to https://media.giphy.com/media/xUA7beks3SyvH5a9mE/giphy.gif. Users could in theory put whatever they wanted into ((GIF)) but it wouldn't matter as we'd sanitize to alpha numeric. GIFs would be loaded in entirely using ajax on demand, scrolling to the end of the container should load in the next page, this also needs a search bar, and the endpoint used should be the trending endpoint.

https://developers.giphy.com/docs/

Since emotes use :EMOTE: maybe reactions should just use ::REACTION::

Needs a better syntax as we want to be able to support inline replacements but we can't just convert all ::STRING:: to reaction gifs. Possible syntaxes as follows.

custom syntax
(reaction:ID)
(reaction:giphy:ID)
(giphy:ID)
(gif:ID)
:reaction:ID:
:giphy:ID:
:gif:ID:
bbcode syntax
[gif]ID[/gif]
[giphy]ID[/giphy]
[reaction]ID[/reaction]
[reaction type="giphy"]ID[/reaction]
markdown syntax
![reaction](ID)

The below syntax probably gives the most flexibility as it leaves the potential for different reaction gif sources.

(reaction:giphy:ID) or (giphy:ID)

Example as follows.

(reaction:giphy:k9b6CX6oZelhK) or (giphy:k9b6CX6oZelhK)

Doesn't make any sense to be adding reactions inline. They are always displayed as block. So continue with the per word replacement of ::ID:: requiring spaces on both sides of it.

This will be default ENABLED, but since it requires a Giphy API key it won't actually be enabled unless the key was supplied. This will allow for an easier time of enabling it across streams.