Test PostsHere you can test your posting skills & see how your signature looks.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
I suppose others may be confused about my point of the post.
I sent Broni a PM about that long-standing forum bug because Broni was posting ComboFix copy/paste instructions in QUOTE tags for malware victims and I was concerned those spaces might mess up the registry merges that ComboFix was doing. I posted that "test" message to illustrate to Broni what I was talking about.
I suppose it would have been better to just put the examples in the PM instead as that would have illustrated my point just as well. I'm sorry about any confusion I may have caused with the public "test post".
Anyway...
I realize vBulletin may have a good reason for automatically putting a space in a long string of characters, causing an end-of-line break (i.e., to prevent viewers having to horizontally scroll a vBulletin page in certain situations).
However, it seems vBulletin should give the administrator a "per forum" option to specify the maximum length of a character string before the software inserts a space. Then the malware removal forum could be tailored to allow much longer continuous strings than 77 or 78 characters...perhaps also based on a poster's privilege level or reputation. For example, moderators and "Team Members" could post long strings but normal users could not (to prevent abuse, for example).
Do you know whether anyone has offered such a suggestion to the vBulletin developers or not?
However, maybe the vBulletin developers would see it as a low-priority fix since there are workarounds (such as enclosing the text in CODE tags instead).
Oh well, thanks for reading my rant anyway. No need to respond.
No need to respond.
