Jump to content

[suggestion] Who invented bb-code? get rid of this piece of crap!


Guest W13

Recommended Posts

Posted

BB-Code is the biggest anti-innovation ever. All I've seen are problems and more problems with bb-code.

WHY CANT WE JUST HAVE A WHITE-LIST OF HTML CODE? No need to convert, just check it before storing in DB. Simple.

My suggestion: for IPB 3, get rid of BB-Code please.

I'm getting problems like these all the time.

Posted

Download Week. :lol:

BBCode is easier than HTML - isn't as scary to those who don't know what they're doing. Just fix the bugs with parsing the BBCode, and it would be fine imho. :mellow:

Posted

As far as I can tell, thats a bug with that specific website, nothing to do with IP.Board or it would have been fixed, haven't seen a bug reported on it anyway

Posted

Download Week. :lol:



BBCode is easier than HTML - isn't as scary to those who don't know what they're doing. Just fix the bugs with parsing the BBCode, and it would be fine imho. :mellow:



Okay, maybe I wasn't thinking hard enough when I made this topic out of frustration....

example



<html>



<_<

Posted

Actually, I've had some problems with the URL tag in the past, it would be replaced with HTML in the post view, not actually a link. Hasn't happened since 2.3.1 though, so I don't know.

Posted

Random divs are a known bug and have been submitted just about every version of IPB. Even if you have never ever enabled HTML in posts, nor import RSS feeds and preserve the HTML it still happens.

Posted

Unfortunately, creating a GOOD parser for BBCode is a right Pain to do - espescially dependant on parsing it back from HTML Code to BBCode. it's a design Flaw really, but a nice tokenising parser, converting to HTML on display and getting rid of the WYSIWYG editor would solve everything :D

Posted

That's just a problem with the IPB parser. bbCode is perfectly fine if you have a proper parser with a bit of cleverness in the implementation of the transformation from bbCode to HTML and back.

In any case, bbCode is a nice way of hiding complicated HTML that people really shouldn't have to deal with. Take quoting for example - no one would want to manually type out the HTML for that thing if the alternative is to use bbCode quote tags.

It's also a nice way of completing avoiding some nasty XSS vectors. Granted, those could also be taken care of by extensive checking of input, but why bother when you can just avoid it altogether?

In short, asking for the removal of something that is at the very least a de facto standard of message boards is probably a bit much, especially given the advantages and disadvantages of the current system as opposed to the system you're proposing. If you wanted to, you could always just enable HTML for everyone and do the whitelisting yourself (using something like HTMLPurifier for example). That shouldn't be the only choice available to everyone though.

Posted

BBCode is the most widely accepted format for most web forums, etc.



I doubt this will change. Even sites like imageshack.us have BBCode options for hotlinking. I see it as too common to remove.


Good point. I even find it awkward when sites like imageshack *don't* have BBCode options.
Posted

I don't agree with the OP about removing BB Code, but do wish its flaws could be figured out and corrected.

Because of the issue with the Quote tag and the Code tag and the Formating tags I no longer do nicely formated pages in my downloads manager. Its basically a read me file type of description for files and I avoid URL's if at all possible because I've been having issues with the < a herf tags being shown in edits also.

Posted

BBCode is the most widely accepted format for most web forums, etc.



I doubt this will change. Even sites like imageshack.us have BBCode options for hotlinking. I see it as too common to remove.



Regardless, with better implementation of rte's, bbcode is (thankfully) obsolete.

Anyway, I completely agree with the op. The best success of bbcode was to simplify overly complicated html tags (like the anchor), for the less web savvy (but is it really that much simpler?). One could also argue that it helped prevent malformed pages because any resulting "bad" code sent by the user couldn't actually break a page it was viewed in, but proper validation would have solved that issue (read: bbcode was developed by lazy programmers not wanting to properly sanitize their input and somehow along the lines became the crappy "common standard" that it is today) :P
Posted

Yeah, because people like the broken outdated rtf engine that IPB uses. If i had to pick between removing the rte engine and the ipb bb code engine, the rte engine would be gone.

And for the curious people, bbcode was initially in some old perl based forum software and was called UBB. The meaning of the U was been lost in my memory.

And yeah, the IPB bb code engine is not the best out there. Luckily I wrote my own that does not have the xss issues. Reminder Invision, I am open for sugestions about licensing.

Posted

Yeah, because people like the broken outdated rtf engine that IPB uses. If i had to pick between removing the rte engine and the ipb bb code engine, the rte engine would be gone.



I never said that IPB's RTE was the best. I just said that RTE superceeds bbcode compeltely based on the entire reason that bbcode was erected in the first place. :)

And for the curious people, bbcode was initially in some old perl based forum software and was called UBB. The meaning of the U was been lost in my memory.


Ultimate? :P
Posted

1) In the interest of protecting server resources changes were made to bbcode parsing in the latest versions of IPB, for the better and for the worse. All parsing is done on save now, which is quite a bit more resource friendly, at the expense of some unparsing issues (any anchor unparsing issues are localized, however, fyi).

2) Our bbcode formatting engine is going to change entirely with IPB3. Entirely rewritten from the ground up to use a tokenizing approach Mez mentioned. We're up in the air on parsing on save vs display, and is something we intend to benchmark. The parser will have the option for each (right from the bbcode configuration in the ACP) but what we do by default...can't really say yet.

We'll be writing up a blog post about the new bbcode engine in a couple of weeks.

henke - I've reviewed your engine to an extent and I like the general approach. The concept put forth is the approach we intend to take (i.e. move away from complicated and error prone regular expressions, properly separate back out the pre_db and pre_display parse, and so on). I don't know about licensing your exact engine, however if you wish to work with us in testing and reviewing the new engine once it's rewritten I'd be happy to get with you at that point. :) I'd really value your feedback at that point (it's a bit premature to ask for your feedback right now since it hasn't been rewritten yet).

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...