Implement Tenor as a replacement for / alternative to GIPHY

To be fair, a lot of those suggestions could be random nonsense like adding a family tree or something.
Then they shouldn't get as many upvotes.

They should consider marking a suggestion as "not planned" and automatically move it to a "not planned" sub-forum if it can't get X upvotes in 180 days. Then, people can still find whether it was previously suggested, see why or why not it makes sense, and make another suggestion for it if it requires new attention to be given, or a bump by someone other than the author of a "not planned" thread to something like 10% more upvotes than it had before being moved to automatically move it back to the regular suggestions forum. Implementing automated features like that here shouldn't be too difficult if we're talking about implementing Tenor in a matter of minutes...

It's very unorganized starting with the issue of "implemented" as previously brought up, and through my interpretation of what you wrote, cluttered.
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.
 
Then they shouldn't get as many upvotes.

They should consider marking a suggestion as "not planned" and automatically move it to a "not planned" sub-forum if it can't get X upvotes in 180 days. Then, people can still find whether it was previously suggested, see why or why not it makes sense, and make another suggestion for it if it requires new attention to be given, or a bump by someone other than the author of a "not planned" thread to something like 10% more upvotes than it had before being moved to automatically move it back to the regular suggestions forum. Implementing automated features like that here shouldn't be too difficult if we're talking about implementing Tenor in a matter of minutes...

It's very unorganized starting with the issue of "implemented" as previously brought up, and through my interpretation of what you wrote, cluttered.

Popular isn't always good (as some recent pole results might or might not show - LOL).

Most popular isn't always the best.
 
Then they shouldn't get as many upvotes.
But sadly some quite niche suggestions get lots of votes. Even this one I would hazard a guess as being used on less fewer less than the majority of forums. We have Giphy on the three forums and nobody uses it. But not trying to say those a representative, just making a guess.
 
Last edited:
I've noticed that SEO suggestions seem to not get many votes. Maybe people don't understand why it may be good.

I'm curious to discuss and hear more about this - perhaps in a separate topic related to that.

As far as I can tell, XenForo does quite well out of the box regarding (technical) SEO.
So, what am I missing?
(again, I would suggest taking this to a separate topic)

On topic:
Giphy & GIFs in general bring a lot of joy and I'm happy to see XenForo considering an alternative now that eye-gouging prices are announced for Giphy. :)
 
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?

No developer will ever out pace suggestions (or bug fixes); it is literally impossible, as every time there is an update that introduces something new, there are guaranteed to be at least 5-10 more suggestions added almost immediately (and that is being conservative based off of what I have noticed here specifically).

Every update to XF that was not primarily focused on bug fixes has included suggestions; whether those are popular or not does not matter, as it shows that XF is including suggestions. Also, just because things are suggested does not mean that they are going to be implemented. And just because they are popular does not mean that they have to be implemented. With the latest release they have introduced one of the oldest suggestions which was OAuth/REST API support, as well as other suggestions.

frm's issue is not that they are not implementing suggestions, or not implementing them fast enough. It is that they are working on something he has historically had a tantrum over, and thus feels he is right to complain once again. It is a never-ending story where he will continue to argue in circles until people just move on and ignore him because if he doesn't win the argument he will just simply not shut up.

The reality is that XF is already moving forward to do faster development cycles (we know of 2.4 and 3.0), and thus will likely increase the implementation of suggestions. Complaining about something that is already planned is simply ridiculous, especially when they are trying to get ahead of an issue that will come from licensing changes. Just because someone does not use a feature, or it is a niche feature does not mean that they should not fix it if they can.

This is just yet another example of people needing to complain about something regarding XF's development, regardless of whether it has improved from the last time they complained. The real irony is that 2.4 was hinted to already include some suggestions so rather than ***** and moan about things, wait to see what that brings and then raise your pitchfork when you will find something else to be upset about.
 
No developer will ever out pace suggestions (or bug fixes); it is literally impossible, as every time there is an update that introduces something new, there are guaranteed to be at least 5-10 more suggestions added almost immediately (and that is being conservative based off of what I have noticed here specifically).
And no-one's suggesting that.

You'll notice that I'm not taking the same hard line here; but it's very clear that there are holes in the approach - 2.4 wasn't even a thing until recently because it was going to be 2.3 then 3.0 - and even 2.3 incorporates bits pulled back from 3.0, then suddenly 2.4 is on the horizon.

It's clear there's a communication issue: there's been calls (repeatedly over the years) for a guideline to the roadmap, what's likely to be included in a future version, what's almost certainly not going to be included in a future version. I wasn't at any point suggesting that the XF devs suddenly start adopting suggestions that don't fit the product, or even turning down more of them, simply being better at communicating what the overarching plan is.

Consider how many people were holding off on upgrades (and may even still be) until 2.3 came out, and how many are holding back for 2.4 - better communication of what's coming up and a vague ballpark (let's go with 'which year it is') and sticking to it wouldn't hurt. Making claims and then failing to hit them (see 2.3 release date drama) doesn't bode well for 2.4, though 2.4 is an ideal opportunity to demonstrate the lessons that 2.3 so aptly taught (namely: don't have 3 years between release cycles of significant feature versions, communicate better)

In the meantime, there is a curious limbo that the 64 pages of suggestions occupy. It wouldn't even hurt to breeze through and check if they've been implemented in the meantime - wouldn't surprise me if this had happened.

Remember: we're not really arguing so much about what the XF devs are doing (see Chris's comment on judging them by what they've done) but what they appear to be doing, which, from a faintly outside perspective could be 'not a lot' given 3 years between releases and the appearance of a neglected and unmaintained board full of suggestions. Appearances matter - even if they lie about the reality underneath them, and I'm just advocating for bringing the appearance closer to reality.

See, all the time a suggestion languishes in the main suggestions board, it leaves the door fully open to that being core. Leaving it for 10 years in there tells a particular story that isn't ideal.
 
Photobucket GIF
 
I mentioned this in another thread, but it would also be good, if possible, to allow Xenforo to accept GIF Keyboards (such as the GIFs you can search using gboard on android phones) as an input as well.
 
I mentioned this in another thread, but it would also be good, if possible, to allow Xenforo to accept GIF Keyboards (such as the GIFs you can search using gboard on android phones) as an input as well.
This.

It would make it easier for those of us on a mac for example to add more keyboards.
 
I mentioned this in another thread, but it would also be good, if possible, to allow Xenforo to accept GIF Keyboards (such as the GIFs you can search using gboard on android phones) as an input as well.

This would be my preference as well. Have you set up a suggestion thread for it yet? If not, let me know if/when you do and it'll get my vote.
 
1731197802221.gif

This was posted with Gboard on iOS.

We don't do anything to prevent it. It's just going to depend how exactly the keyboard provides the image. In this case it copies the image data to the clipboard and pasting it triggers an attachment upload.

Not sure how it works on Android or why it would be any different but ultimately not sure there's anything for us to do here.
 
Maybe those of you on android phones look at only posting from your computers for now until something is done for android users
 
Back
Top Bottom