Implement Tenor as a replacement for / alternative to GIPHY

GIPHY may start charging for the use of their API so going forwards we will consider Tenor as either an outright replacement for GIPHY or an optional alternative to it.
I prefer to have the possibility to choose between GIPHY or Tenor.
For those that can't afford (or just dont like) API pricing, they have the ability to switch to Tenor.

I like GIPHY, so I don't want it to disappear or need to ask a developer to create another custom plugin for something that used to be a core feature, and suddenly got taken out. So please, let us choose which one we want to use.
 
Valid point. I think that makes a lot of sense.

We don't read these threads to see you agreeing with people, Christopher...

well take you on the sandlot GIF
 
Firefox has it as a small giphy app that gets connected to my browser so really it won't bother me greatly whatever happens.
 
Thing is, there are 60-odd pages of still-open suggestions, some of which have more support than this one which - to some - seem like rearranging deckchairs on a certain ocean vessel.

I think it might do wonders to go through and cull the suggestions board for the things that are definitely not on the roadmap in the next, say, 2 years, and things that are clearly in the “not interested” camp. Not only for sanity but for the optics of being seen to pay attention to suggestions which is part of the problem here, however you slice it.
 
And not the literal hundreds in the board, some still dating back 14 years. Marking a few off every couple of years doesn’t change the 80GB elephant in the corner. (It’s not an 800lb gorilla, we’re talking digital and PHP!)
 
The way to see if we are paying attention to suggestions is to look at the suggestions we mark implemented at every release cycle.
Most people base bug fixes and suggestion implementation off of the number of pages... Ignoring that more bugs and more suggestions are added constantly, so there is an ever-growing list to implement or fix.

I say you spend the time and make a pretty chart and graph page where they can see how many are fixed... Further making them wait for implementations and bug fixes, because they're still going to whine regardless of whether or not they have data.

sassy ha ha GIF by Robert E Blackmon
 
Thing is, there are 60-odd pages of still-open suggestions, some of which have more support than this one which - to some - seem like rearranging deckchairs on a certain ocean vessel.
Exactly my point.
I probably could have done it in the time I spent arguing about it for no reason 🤦‍♂️
They're so proud of their ability to do something so quickly, yet can't get to something in 10 years. They'll jump all over an alternative and push out an XF PL for the continued support of GIPHY or Tenor or the nth alternative to keep the GIFs but ignore the 60-pages for another 10 years.

Just do one thing from the suggestions that've been there for 10 years with the support this has, which arguably has more only because @Chris D posted it (I'd wager again if another member posted it as a pre-emptive suggestion, nobody would care this much and it'd have 15 up votes), and I'll pipe down, since you're so fast at coding and all.

Or, implement this as a feature at least, not a half-measure "bug" fix (I would say that a "notice" is more of a feature than a bug fix - as in make it a flag for developers already).
https://xenforo.com/community/threads/guests-cant-attach-files.225309/

Just to be clear, I did upvote this as a suggestion. However, suppose this is implemented in 2.4 over the older suggestions that have more or the same support. In that case, I'm not going to be too happy when I know now that they could do it "in the time spent arguing" (meaning if they had to, it could be pushed out as a patch for everyone, even to non-updated license holders, overnight). Shows you how much they care about open suggestions or doing them right to begin with...
The way to see if we are paying attention to suggestions is to look at the suggestions we mark implemented at every release cycle.
I don't know if this is on purpose to make it appear like you've done more than you have, but I would suggest new prefixes to show implemented in what version ("Implemented (2.3)" for instance) as it makes it much easier to follow progress. Otherwise, the only way to do it is to look at HYS threads for that version, which makes it look like 6 or so features are added. It'd be nice to know how many features were added on each version with 1 prefix

64 pages of "Implemented" looks good until you break it down by version...
https://xenforo.com/community/forums/closed-suggestions.15/?prefix_id=2

And then you compare 2.3 HYS to the 63* pages of open suggestions.
https://xenforo.com/community/forums/xenforo-suggestions.18/
 
Last edited:
Exactly my point.

They're so proud of their ability to do something so quickly, yet can't get to something in 10 years. They'll jump all over an alternative and push out an XF PL for the continued support of GIPHY or Tenor or the nth alternative to keep the GIFs but ignore the 60-pages for another 10 years.

Just do one thing from the suggestions that've been there for 10 years with the support this has, which arguably has more only because @Chris D posted it (I'd wager again if another member posted it as a pre-emptive suggestion, nobody would care this much and it'd have 15 up votes), and I'll pipe down, since you're so fast at coding and all.

Or, implement this as a feature at least, not a half-measure "bug" fix (I would say that a "notice" is more of a feature than a bug fix - as in make it a flag for developers already).
https://xenforo.com/community/threads/guests-cant-attach-files.225309/

Just to be clear, I did upvote this as a suggestion. However, suppose this is implemented in 2.4 over the older suggestions that have more or the same support. In that case, I'm not going to be too happy when I know now that they could do it "in the time spent arguing" (meaning if they had to, it could be pushed out as a patch for everyone, even to non-updated license holders, overnight). Shows you how much they care about open suggestions or doing them right to begin with...

I don't know if this is on purpose to make it appear like you've done more than you have, but I would suggest new prefixes to show implemented in what version ("Implemented (2.3)" for instance) as it makes it much easier to follow progress. Otherwise, the only way to do it is to look at HYS threads for that version, which makes it look like 6 or so features are added. It'd be nice to know how many features were added on each version with 1 prefix

64 pages of "Implemented" looks good until you break it down by version...
https://xenforo.com/community/forums/closed-suggestions.15/?prefix_id=2

And then you compare 2.3 HYS to the 63* pages of open suggestions.
https://xenforo.com/community/forums/xenforo-suggestions.18/
200.gif


Can I buy you out of your licenses so you can go away?
 
200.gif


Can I buy you out of your licenses so you can go away?
You probably have enough to, but I do have full suite and brand free on some (like $795 for 1 I believe).

But, no. I like XF and purchase more licenses when they pop up. That said, I have the right to gripe like everyone else.

It would be ridiculous of a company to not want negative feedback so they can gauge improvements.
 
Last edited:
Most people base bug fixes and suggestion implementation off of the number of pages...
There are 64 pages of implemented, 63 pages of outstanding suggestions, over the same 14 year period, and 456 pages of suggestions total (=392 pages of not implemented)

That says to me, out of those outstanding suggestions I could expect to see 8 pages of them implemented based on available data. Wouldn’t it make sense to clear out the other 50-odd that aren’t, to focus peoples’ attention and also signal to the add-on authors what is and is not on the table?
 
add-on authors what is and is not on the table?
And to the general public so I don't need to rush to custom development if they're focusing on "faster release cycles" to knock some of them down at least within 90 days (or even 180 days) that they're "not planned" (at least in the next second level release, which could always be reevaluated every cycle)...
 
There are 64 pages of implemented, 63 pages of outstanding suggestions, over the same 14 year period, and 456 pages of suggestions total (=392 pages of not implemented)

That says to me, out of those outstanding suggestions I could expect to see 8 pages of them implemented based on available data. Wouldn’t it make sense to clear out the other 50-odd that aren’t, to focus peoples’ attention and also signal to the add-on authors what is and is not on the table?

To be fair, a lot of those suggestions could be random nonsense like adding a family tree or something.
 
Back
Top Bottom