XF 2.4 general discussion, feedback, complaints, random off topic posts, etc.

Can we just retire BBCode someday, or make it an option so if people really want it, they can enable it? To me, BBCode feels like we are trying to hold on to the glory of MySpace. Seems like a lot of code that wouldn't need to be maintained anymore as a bonus. :)
XF is never going to win here.

There's going to be a legacy portion of the client base who will cling to their BBCode, despite the fact that modern editors (of everything from Microsoft Word to Facebook) have moved on. This is going to be one of the bigger transformations that XF will need to make with their customers (who will need to make the same transformation with their users).
 
I wouldn't remove it entirely. Have bbcode as an option for those who use it due to having a migrated site from vbulletin.
I know this would suit my mate better. You'd anger him if you took that away.
Trust me on this you do not want to see @BIG LLC angry.
 
XF is never going to win here.

There's going to be a legacy portion of the client base who will cling to their BBCode, despite the fact that modern editors (of everything from Microsoft Word to Facebook) have moved on. This is going to be one of the bigger transformations that XF will need to make with their customers (who will need to make the same transformation with their users).
Make it a user group setting… then those that want to move on (or even allow admins only to use it or something), could. 🤷🏻‍♂️
 
There's going to be a legacy portion of the client base who will cling to their BBCode, despite the fact that modern editors (of everything from Microsoft Word to Facebook) have moved on.
Moved to what?

For those who want to tap into the full potential of HTML and web typography while using XF, Facebook is rudimentary at best.

What does Microsoft Word have to do with HTML?

One of my forums has several dozens of custom BB codes defined because that’s what it takes to format a text in some literary genres. It is not about BB codes per se; there is no “clinging.” It's about using advanced formatting that goes above and beyond what social media will ever need.

As an informed community, we should be aware of just how different our needs may be.
 
But that would still mean a lot of code that would need to be maintained and in fact would require additional code to add the permission.
Well “additional code” for permission is literally a single line to check the permission. But ya, I think it would be great to gut it and do away with BBCode completely. But I know that’s not practical because a lot of users would complain… that’s why the permission could be a “transitional” thing of sorts. 🤷🏻‍♂️
 
Can we just retire BBCode someday, or make it an option so if people really want it, they can enable it? To me, BBCode feels like we are trying to hold on to the glory of MySpace. Seems like a lot of code that wouldn't need to be maintained anymore as a bonus. :)
Sentiments aside, what would be the technical (performance) advantages of removing BBCode from XF? What would be the equivalent of custom BB codes in the hypothetical version of XF without BBCode?
 
What would be the equivalent of custom BB codes in the hypothetical version of XF without BBCode?
I guess that would be my question, too. I do have one custom button on my toolbar so I would hope that any future replacement would enable me to keep or recreate that.
 
Seems like a lot of code that wouldn't need to be maintained anymore as a bonus.

Careful - you're starting to talk like a 4.0 release.

I've seen it so often with software product development cycles (vBulletin and Kayako being two of many examples)

v1: "hey this is a neat idea"
v2: "wow this really has a lot of promise"
v3: "this is the best product ever"
v4: "wait - you removed all these features because 'nobody was using them' ? well I rely on this feature and now your software is no long suitable for my purposes"

This is one thing that makes me a little nervous about the call for more features - because at some point there's going to be too many and the devs will want to start removing some during a major rewrite for v4. From there, it's largely all down hill, in my experience.
 
the devs will want to start removing some during a major rewrite for v4.
I can't think of any features that were removed between XF 1 and XF 2.

There also won't be any features removed for XF 3.

I can't imagine why XF 4 would be any different.
 
If it's improvement, without bloat, bring it on. The no BBCODE thing sounds interesting. Maybe an option for those that need it, otherwise, its not loaded. I simply want XF to remain light and super fast, and not follow in the bloatware that is VB and IPB.

All bloatware should be add-ons, whether official or third party.
 
Are any other community software devs using TipTap in their products already? I'm curious if XF (meaning all of us) will be walking the bleeding edge or a well trodden path.
invision alpha version that they have made so that users can preview it as a user uses it.
i will not post that link here out of respect.
but you can find it on admin junkies.
 
I can't think of any features that were removed between XF 1 and XF 2.

There also won't be any features removed for XF 3.

I can't imagine why XF 4 would be any different.
we are literally in the middle of a conversation about removing bbcode, which for me im on the side of not doing btw(unless there is a new custom option) ;P
 
I can't think of any features that were removed between XF 1 and XF 2.

There also won't be any features removed for XF 3.

I can't imagine why XF 4 would be any different.

I wasn't suggesting features were removed in previous versions. I was commenting on other products which go through similar development cycles in the context of a suggestion to remove bbcode support.

By the time these other products get to v4 they decide to do a major rewrite because the underlying framework has aged too much - and in the process, they either drop features or delay the re-implementation of features because of the rush to release the new version.

I'm hopeful that won't happen here because XenForo is already a very mature product - the major framework update happened for v2.x and from my opinion, is still perfectly fit for purpose.

I would be far more concerned about v3.0 doing something crazy like introducing a JavaScript framework for client-side rendering of the UI and changing the structure into a single-page application (SPA) - because then it's no longer a PHP application, but a JavaScript application with a PHP backend.
 
we are literally in the middle of a conversation about removing bbcode, which for me im on the side of not doing btw(unless there is a new custom option) ;P

It was a suggestion from one forum member.

No one on the team has indicated that would happen.

🤷‍♂️
 
I'm in favor of dropping GIPHY support now.

Was going to add it to a new forum and it appears that they went all "corporate" on you, like Facebook did for logins, requiring business validation, except like Facebook for inserting an animated GIF into a post.

To clarify, this is what is now required to get into production mode. I'm not going to make a screencap video of inserting a GIF into a post for them. I'm just not. Good on those that will for an animated GIF. However, this looks like a dying genre, even on Facebook.

1726449456725.webp
 
Last edited:
Back
Top Bottom