The discussion revolves around the ReplyGIF plugin, rewritten by cpradio to work with the latest Discourse version. Key updates include automatic pausing of GIFs, multiple GIF selection, and support for API keys and HTTPS via reverse proxy. The plugin has been split into a new repo, with version tags (v0.5.0 for older Discourse versions, v1.0.0 for newer ones) to ensure compatibility. Users discuss issues like mixed content due to HTTP URLs in JSON responses, resolved by configuring a reverse proxy with sub_filter in Nginx. Falco addresses a notification issue caused by system edits, recommending enabling disable edit notifications. cpradio confirms fixes for other issues, while RGJ shares their Nginx configuration to resolve HTTPS problems. The plugin now supports Font Awesome 5, and cpradio has also updated the Giphy plugin to fix similar issues.
With this rewrite there were a few changes, all gifs are paused automatically and can be clicked to start the animation and you can select multiple animations to insert into your post (so long as they are part of the same category/tags).
I’ve also built in features for future proofing. API Key (in case ReplyGIF starts to monitor their API Keys), and the ReplyGIF URL so you could put it behind a proxy for HTTPS support.
Enjoy!
Edit: This is a new repo. It is no longer a fork as the changes were severe and likely wouldn’t merge well.
Awesome plugin. Works great on my install. Well… Maybe too great.
Would be cool to have out of the box a limiter. So we can set a limit on how many gifs can be used in one post. So users can’t reply to a thread with 5000 gifs. (which i did in testing lol)
You have to uncheck the other .gif that you have selected before posting.
But I agree with you. The better solution is that @cpradio add an option in admin panel to set a limit per post (and topic too).
Okay, so I’m not against such an idea, but realize there will be limitations that are beyond my control. I can limit how many you select in the Modal (fairly certain), but I since I’m not tying into the composer, I couldn’t stop someone from opening the model twice to get 10 images (when the limit is 5).
The larger issue I think is Discourse currently has no way to limit the number of images beyond TL 1. It may be worthwhile to see that as a feature versus making that specific to this plugin. As one could simply reference 5000 gifs outside of my plugin and still cause the same pain.
@sam, @zogstrip, what do you think of such a feature? If it is something we could have, maybe 0 (off by default), it might be something I look at contributing and it would only apply to TL1 and higher (staff would be exempt).
Just to jump in here @cpradio I think to add a feature like this to a community. That there would instantly be some abuse. I would feel terrible for my moderators to have to constantly clean up offending posts or to not use the plugin at all. Which would be shame as it makes the user easily be able to express themselves.
But that can be done without the plugin too. The point is, the abuse vector exists regardless of the plugin. The plugin simply makes it a tad bit easier. I’m more than willing to look at creating a site setting in core to limit the number of images that can be embeded in a given post, but I don’t think it should be this plugin’s responsibility, it should be within core.
Okay recent changes in Discourse have removed string-buffer and the use of rawTemplate, so to support non-updated versions, there is a tag v0.5.0 that will let you keep operating.
Whenever you write a post and insert a gif, you get a notification indicating that “system” user has edited the post. When you look up to the revision history there is a previous revision without the gif. How can this be avoided?
