It's a Known Issue.

"Waiter, what the heck is going on here? This food you brought me is all raw! "

"Rawness is a known issue."

"Known issue? What does that mean?!"

"Rawness is a known problem. Cooking has been placed at a high priority in the kitchen activity queue."


--------------------------------------------------------------------------------------------------


"Hey, buddy, why are you down in this unusually hot and torturous part of Hell?'

"God told me in a vision that his love extended to even to the worst of sinners."

"That doesn't sound so bad. What'd you do to make him so mad you got put here?"

"I told him my sinning was a known issue."


---------------------------------------------------

yes?

These, Huns, are what are known as jokes, apparently not very funny ones in your view.

They are based on my post concerning my displeasure at the problem of ghosted objects and Robin Linden's response to it.




The phrase "Known Issues " has been selected by Linden Lab as a euphemism for what used to be called the bug queue. Perhaps someone realized that calling SL's problems "bugs" implied the presence of errors which resulted from mistakes and which could be fixed while "issues" sounds more like something in the weather that isn't the result of human action and about which nothing can be done at the present state of technological development.

Perhaps you have heard people make a comment suggesting that they will perform some action or another when they "get a round toit". When shown in print this might be accompanied by a coin-like object with the letters "TUIT" on it's face. There being no such thing as a "Tuit" and thus no such thing as a round one the implication is that the activity will never be done, much the same as saying that the problem of ghosted objects has been given a high priorty in the bug queue conveys to me more that they problem will never be solved becaused absolutely zero effort is being made to solve it.

I am reminded of Jerry Pournelle's column "Chaos Manor" that appeared back in the days of Byte magazine. He would use a phrase to describe when some bug fix or program update was supposed to come out. The phrase was "Real Soon Now", always capitalized, and meant that you shouldn't hold your breath or make any plans that depended on that Real Soon Now time ever arriving.

I'm sorry that my jokes were so weak that you couldn't tell that the desired response would have been someone to post an additional joke based on some catch phrase emitted by the Lindens, although I think the fault may not be totally in the jokes themselves. I suspect your failure to find any amusement at all in my post might just possibly be the result of not having smoked enough pot in the last few hours. It's just a guess. You could give it a try and see if helps a little.

My lousy sense of humor is a known issue. I have given the acquisition of a better sense of humor a high priority in my action queue, and I am certain I will become excruciatingly hilarious Real Soon Now, as soon as I get a round Tuit.

I don't know just when my sense of humor will get funny enough for people to at least tell I am making a joke, if not actually be amused by it, but I will lay odds that this, and any other events one might think of, like say, the evolution of a new order of life, or the next cycle in the big bang, will occur long before the objects ghosted upon deletion problem is solved.

Did you tell the Lindens to check the gas line?

Maybe Huns meant for you to finish that sentence?

I think Huns was asking "yes" in response to the very end of your post, where you said the above... not neccessarily commenting on the humor of your post. But your incredibly long response to his question was amusing.

do ya think the buggyness and generally broken condition of the objects in sl known as "users" is a known issue? most of the ones i run into barely work at all and even when they do they just lurch around spewing random characters.

As a software architect that works on large-scale projects, I expect that means that they don't have the manpower to deal with it at the moment without dropping their other projects. For example, in order to eliminate the ghosting, it might require overhauling the entire client-server communication protocol or something. I'm just speculating, because I certainly haven't seen their code base.

If it were the developers' job to answer the support queue, you probably would have been told something at this level of detail. But if it were the developers' job to answer the support queue, I expect you would see new code sometime in 2026.

Insightful Zuzi, LOL. May I quote you?

"Exaulted" Bob Bravo

In any given day, I have to read a ton of words, and there were too many in your post, so I only read what I've quoted here. Ghosting has been a problem in SL for a lot longer than you've been here, and I can tell you it is a lot less of a problem than it was in 5/2003 when I first noticed it. LL has put a lot of work into this product, and I am satisfied that if they don't fix a bug like this in a short timeframe, it's because a very long and involved redesign would be necessary to fix it. I also know that they are well aware of the ghosting problem, and that they are working on a 2nd-gen graphics engine presently. That might just fix it but I don't know for sure.

Keep in mind that LL is a very small company, and they don't have 30 programmers to throw at single problems at the drop of a hat.

of course. the only reason i post on the forums is to get quoted and finally steal some sig spotlight from that glory hog Torley.

Strangeweather, it is good to finally get an estimate for when the ghosting problem might be solved. 2026 is much earlier than I hoped. What do I need to do to get the programmers transerred into the questions answering department so that this problem can finally be solved?

That was another joke, in case that isn't clear.

Seriously I question priorities that involve fixes to the permission system, for example, when some people are effectively unable to create the objects to assign permissions to owing to having a typical ghosting rate of 30 to 50 percent. Sometimes when I try to build things I get a one hundred percent ghost rate. There is no way in the world I am gonna manually move the things out of the way or enter numbers into the edit field to position the ghosts into a harmless position. They seem to me to be working on their problems in a very odd order.

Perhaps someone at a key location in the organization has fallen victim to the Peter Principle.

When is that 1.6 supposed to happen?

Ghosting is currently a low priority because it is a problem without an easy solution, and because it is a problem which does not severely affect most users. That your experience differs so drastically from the norm suggests that the problem does not lie with LL, but with you. Though ghosting is a problem, a rate apparoaching 100% is either hyperbolic, or symptomatic of significant connection problems on your end.

Sadly this high ghosting rate occurs when there is zero packet loss and pings of 100 100. Nothing else I do on the internet has any trouble, but SL is the only thing I use that's more demanding than internet browsers.

Wouldn't it seem that severe connection problems would have a more general effect than just a massive ghosting problem?

Would there be errors that one could find in the log files? It does seem to me that problems as severe as I have would produce some kind of messages indicating lost or mangled or delay packets or something.

I hear about ghosting from other people, but no one gives any info about whether it is happening 1 time out of a thousand or 30 times out of a hundred.

I have no real alternative for internet service; you can rest assured I would try it if I did.
I use RoadRunner and my only alternatives are Time Warner AOL or Time Warner Earthlink, both of which would come through the same cable that the Time Warner RoadRunner does. I am lead to believe by stuff on the internet that my signal path would be the same if I switched, only the billing would be affected. I don't guess anyone has any info on that?

DSL stops about a mile away from where I live.

I could switch to a high priced higher bandwidth RoadRunner but I have no idea at all whether that might help. RoadRunner is pretty clear about not caring about UDP speed or reliably.

I don't have wireless, and the problem occurs on two different computers, and it doesn't matter if the computers are networked and sharing an internet connection or just one is plugged straight into the cable modem. Same results occur using the cable modem's USB port or Ethernet port.

If I knew anyone in RL I could try moving my computer to their place and see what results.
My workplace may be switching to RoadRunner, which I guess would be business grade RoadRunner, whatever that is. I could bring my computer in after work and try it if that does come to pass.

I feel your pain.

Ghosting sucks. Ghosting is there. Ghosting is being worked on. Ghosting has been mentioned on the forums many times in great detail as to the fixing and the problems with Ghosting. Ghosting should be searched for on the forums for further information.

Since Bob was taking so long on the 'ole cut and paste ........ welcome to my sigline!

The ghoasting bug was actually cured months ago. The effect you're currently seeing is meerly a ghoast of the bug...

Won't there always be 'ghosts in the machine' ??

<-- begins singing the opening theme of Ghost in the Shell
==Chris

yay! *dies happy*