Implement Tenor as a replacement for / alternative to GIPHY

If there is no alternative, I wouldn’t mind getting rid of the gifs. They’re fun, but not necessary to a community.
Better watch your tone about GIFs round these neck of the woods, else you might get roasted for 2 pages straight, from other members to even staff. 🤣

I learned from experience that you shall not talk down on GIPHY, unless it's now socially acceptable because they want to charge over $9000.

 
It started when you proposed we drop GIPHY support entirely, and people who enjoy having GIF support disagreed. It's not really about GIPHY specifically. People wouldn't want us to drop GIPHY support without some suitable replacement. Tenor may be that replacement in this case, or it may exist alongside GIPHY if people wish to use it.
 
Better watch your tone about GIFs round these neck of the woods, else you might get roasted for 2 pages straight, from other members to even staff. 🤣

I learned from experience that you shall not talk down on GIPHY, unless it's now socially acceptable because they want to charge over $9000.

Gotta have elephant skin my friend. 😂
 
If there is no alternative, I wouldn’t mind getting rid of the gifs. They’re fun, but not necessary to a community.
I Dont Want To No Way GIF by Netflix Is a Joke
 
Gotta have elephant skin my friend. 😂
Doesn't get to me. I say what I want to say.

Now it's about GIPHY charging, then Tenor falling suit.

Might as well remove it now as taking away code is easier to add support for an alternative that I would wager will follow suit.

Then what? Remove GIPHY and Tenor support at the same time or just rip the bandaid off now?
 
It started when you proposed we drop GIPHY support entirely, and people who enjoy having GIF support disagreed. It's not really about GIPHY specifically. People wouldn't want us to drop GIPHY support without some suitable replacement. Tenor may be that replacement in this case, or it may exist alongside GIPHY if people wish to use it.
Bet you a free license that Tenor will start charging before we have our first RC for XF 3.0 — I win, you drop me a free license, I lose, I buy one and ask to Terminate it.

This is business. GIPHY charges, then Tenor will see profit if they can undercut them by thousands and only charge $900.

Screenshot_20241109_023121_Chrome.webp

Not like these guys won't see the money being printed for GIPHY and want in on that too.
 
Last edited:
Then we'll find another replacement. It's not that deep. If you don't want to use GIPHY, Tenor, or offer GIFs on your site, that's entirely your prerogative. We'll continue to offer GIF support for as long as it is possible to do so for those who wish to offer that on their site.
 
Then we'll find another replacement. It's not that deep. If you don't want to use GIPHY, Tenor, or offer GIFs on your site, that's entirely your prerogative. We'll continue to offer GIF support for as long as it is possible to do so for those who wish to offer that on their site.
So development is going to constantly chase the cheese for alternatives until the only one left is packaging gigabytes of GIFs in the installation package?

I could see the benefits of time spent elsewhere, starting with the most popular suggestions that've been there for years, perhaps.

But, you do you.

I use GIPHY on my forum and I'll probably switch to Tenor when the change is made. But ultimately, just like every free image host that started out free with hotlinking and became a click-to-enlarge thumbnail for full view wrapped in 10 ads, alternatives will follow suit or try to monetize GIFs some other way, like an embed that could show an ad every 5 plays of the GIF or something to that extent.
 
It's worth noting that Tenor isn't just some profit losing small business. In 2018 they were purchased by Google. Is it ludicrous to think they would want to monetise it in some way in the future? No, I'm not going to bet a forum license on it. But ultimately they purchased it so that they could deliver GIF searching capabilities to their existing user base via Android and GBoard. And they already monetize it, probably in a way that far exceeds any revenue they'd generate by charging for API access. Not least they engage in sponsorship deals so that GIF owners can pay to feature their GIFs more prominently, and collaboration with brands on marketing campaigns. If you ever log in to Tenor or GIPHY and see ... I don't know ... floods of Deadpool vs Wolverine GIFs ... it's because Marvel / Disney have paid a pretty penny to surface their GIFs. Being owned by Google, I have no doubt that their infrastructure is powered by their own Google Cloud services, meaning that for them, delivering the API is probably cheap as chips anyway.

So Tenor is probably a safe bet, for now. As for what would replace that if the worst came to the worst... no... we wouldn't package "gigabytes of GIFs" in the installation package...? Why would we do that. If we ran out of road and there were no viable alternatives then the ability to use GIFs would depend on whether you had a relevant API key that allows you to do that, perhaps one that people would have to pay for if they wanted to. And if they didn't want to pay 🤷‍♂️ So what? It's there for people who need it.

I don't really understand what the big deal is or why it warrants such a persistent back and forth on it. In fact, that's the last I'm going to say on it.
 
So Tenor is probably a safe bet, for now.
No, I'm not going to bet a forum license on it.
Gives a clearer picture on where we're at with XF 3 at least.

And if they didn't want to pay 🤷‍♂️ So what? It's there for people who need it.
Continued support regardless of how few will be able to actually use it when it comes time to pay up over big boards with the budget that can not only pay up, but also develop their own add on for continued support without XF supporting it. Not really the best use of time, again, but you're the boss.
 
Gives a clearer picture on where we're at with XF 3 at least.


Continued support regardless of how few will be able to actually use it when it comes time to pay up over big boards with the budget that can not only pay up, but also develop their own add on for continued support without XF supporting it. Not really the best use of time, again, but you're the boss.
gifs can be attached. Get over it.
 
Removing functionality and pushing it over to the add-on devs (which is likely what would happen) is quite the opposite of what most people seem to want on here based on various threads. I don't use the REST API or web hooks but that doesn't mean I don't support them being there as supported functionality.

Personally I like GIFs but not enough to pay that kind of money. As long as there is a free API option, my site will have a GIF button. However, I am on two non-Xenforo sites that don't have a GIF button and I can still embed a GIF using their image embed button and the share link, which I believe would not be using the API. So I could always do that on a Xenforo site without API access.

As for GIPHY vs. Tenor, I will take whatever works and isn't going to break my bank.
 
gifs can be attached. Get over it.
Brilliant. How didn't I think of that? 🤦‍♂️

We're talking about development on constantly changing APIs and issues that arise with that for GIF support, and you say that we can just attach them?

I didn't say abolish attachments.

I said stop chasing alternatives if it's ultimately going to come down to attachments and focus on decade old suggestions that have greater utility instead of supporting 2 APIs that could change at any time (ignoring the cost issue for this example), as we see with PayPal, things often break and require patches, which could be the same in this case too.

Devote time to patch APIs or get to popular suggestions instead?

Which One Thumbs Up GIF by Originals
 
Then let's have a 2.4 HYS with at least one of them already to show you're capable of doing both.

We'll likely only see 8 additions in 2.4 counting the editor, if that, far from the 100 suggestions, some dating back to 2010s.

My expectations on both aren't high when you fail to do even one.

Two months in since the announcement and no HYS, but we'd definitely get Tenor support overnight if GIPHY suddenly started blocking the API and charging. Make it make sense.
 
Devote time to patch APIs or get to popular suggestions instead?
I suspect that adding GIF API support would be suggested and voted up fairly quickly were it not already a feature. And patching the GIF API is supporting a popular feature from what I am seeing.
 
Then let's have a 2.4 HYS with at least one of them already to show you're capable of doing both.

We'll likely only see 8 additions in 2.4 counting the editor, if that, far from the 100 suggestions, some dating back to 2010s.

My expectations on both aren't high when you fail to do even one.

Two months in since the announcement and no HYS, but we'd definitely get Tenor support overnight if GIPHY suddenly started blocking the API and charging. Make it make sense.

Every update cycle we implement hugely popular suggestions, some dating back years, so our track record is there for all to see and I’m satisfied with our progress.

Have we said when we’re implementing Tenor? Have I said it will be in 2.4? Have I said it will be in 3.0? I’ve logged it as a suggestion solely for the purpose of having it in our backlog for suggestions, and to engage customers who may have valid points to add. It could still be here in a few years as you eloquently point out because, after all, we absolutely never implement anything of note ever do we?

The only thing in this thread that makes no sense is your incessant ramblings on a point that has little to no impact on anything at all. So unless you have anything constructive to add I’d suggest it’s wise to stop at this point.
 
I suspect that adding GIF API support would be suggested and voted up fairly quickly were it not already a feature. And patching the GIF API is supporting a popular feature from what I am seeing.
I suspect changing/adding Tenor is also minimal work on XenForo's end--it's not a major update or reconfiguration. Not like it's going to take a team of three developers several months to accomplish, in other words.
 
Back
Top Bottom