OMG if this isn’t the truth! I see so many weird little passive aggressive baiting type stuff in all kinds of threads that stem from a certain group and their rigid intolerant ideology. Thankfully one has been banned. I am still hoping for ignore to return. It just makes it easier to roll on past in an interesting conversation.
2 Likes
Is the Ignore feature still not working? I’m guessing not, since since someone on my list showed up on one of my threads!
No ignore isn’t working yet,sure Mod 1 will inform us when that function is fixed.
After reading the Help questions on the board of the software developer (vBulletin Version 5.2.5) the Ignore function is an embedded feature.
It appears the feature was either altered or disable in the software’s use on this board so do not ever expect Ignore to work
It is there, according to the Moderator, just not working and they are working on it.
There is no reason to think they are lying about it?
I assume it was nicked off when they were working on other and are having a hard time getting it back online.
Good to keep reminding them how important it is for some, so they hurry up with it.
Yo, @clanter!
I posted this last time you brought up how you think we’re the only board with a broken ignore, but perhaps you missed it.
It’s broken across the entire PLATFORM. Not just us!
4 Likes
Oh, thanks for sharing this information Mr. @Simkie . Interesting…
MARK.B | vBULLETIN SUPPORT
Sat 11th Mar '17, 6:44am
No updates on this as yet…it probably needs votes.
The link to the tracker entry is here: VBV-17030
So if we all vote for it, maybe they will get it fixed soon 
1 Like
this is just what pisses me off about software… They say the feature is there …but isn’t. …refund? ugh No as we have your money and what are you going to do about it.
The owners of this board paid for the software and they got screwed. … so they will suffer with reduced activity, suffer loss of advertising income due to the reduced activity and then finally change the software out to XenForo Ltd. or some other.
I despise this concept of a bug being fixed only if enough people have shouted. To me its an important functionality and as a software developer it is vBulletin’s responsibility to fix a known issue. So even with the disagreement of this notion I have gone in and added my vote on the their bug tracker link — hoping — they would give it any sort of importance to it.
@Moderator 1 - Maybe if you guys file an ‘official’ support request (if you haven’t already) they would give it some weight.
A very fine line IMO. If the feature was coded in but not functioning properly, the feature is there. Why a refund? If the feature was not coded in, then perhaps a different story. I’ve never seen software where all documented features worked as documented. I’ve never seen software (short of code of only 2 or 3 lines) that didn’t have at least one bug.
I know of folks that used to call “bugs” undocumented featured :lol:
1 Like
So product performance is not expected? Sort of like buying a car that wouldn’t start then the auto manufacturers saying oh that’s just a bug we are working on …suck it up until we figure it out
The feature is claimed to part of the program, it does not work nor evidently ever had… any other industry there would cries of false advertisement …
Buy an airline ticket, plan that wonder vacation then go to the airport and sadly return home as the flight is canceled because they couldn’t start the engines … oh no refund, its just a bug we are working on
The number of bugs always exceeds the number of lines found in a program.
Next self driving cars
Now that is a scary thought!:eek:
Oh, I love the idea of self driving cars.
I need someone to drive me into town.
I can’t see that good any more.
Self driving cars would be great.
What is scary is that we don’t have the reliable programs yet needed for that, I don’t think.
Your article reinforces that opinion.
Love the idea too, but very scary at the same time… I don’t want to put my life in the hands of programmers who simply say “oops that didn’t happen when we tested it”. Its almost a cliche every time we report a bug to IT staff in our office.
Given that no computer program will, IMO, ever be free of bugs and given that testing will not find all bugs, what type of response were you expecting?
Would you be happier if the “oops” was replaced with “sorry”? Software will ship with bugs… some of which are unknown and yes, some of which are known but deemed of insufficient severity to delay the release. The known bugs may or may not get fixed given resource availability. The bugs which are discovered after release may or may not get fixed depending on severity, ability to reproduce, and resources.
Maybe someday the realities above will no longer be the case, but software development and release has been like this for many, many years.
One reason that I’m just as happy driving my own car 
2 Likes
My note was just on the lighter side…
I understand and appreciate the efforts programmers and IT make all the time, in order to bring us all the cool technology. For the most part, technical glitches are not life endangering like a website not working as expected or a program crashing and losing data as compared to Tesla driving under the truck!!!
On the other hand there are several accidents happen each day due to some mechanical failure too.
Someone once tried to explain me the whole development and testing process, with regression, alpha, beta testing and some other terms that my simple brain can’t even remember and yet, it can’t be bug free for exactly the same reasons you have explained. I think what I’m trying to say is that with our ever increasing dependency on technology and the amount of technical glitches we encounter with almost everything, everyday, it sometimes scares me a lot.
And yes, I like to drive my own car too :winkgrin:
In general, if the bug is severe (and known), the software won’t ship until the severe bug(s) are fixed.
If the bugs, or undocumented features as I’ve often fondly referred to them, aren’t severe, the software may ship anyway. If software releases didn’t ship until all the known bugs were fixed, the software would probably never ship
What is on the “scary” side are the severe bugs that are unknown until the right set of circumstances occur to drive the code through a path that hasn’t previously been executed in quite that way. That’s potentially when the driverless car has the crash :eek:
