Harvey's 'threaded' problem in Support...

[mywaytoo]

Might be nice to roll this solution out to everyone...

[GregChapman]

Needs to be user choice, in my view.

It depends so much on your userbase and volume of traffic as to what you prefer. For example, those used to newsreaders (for reading Usenet/newsgroups with many hundreds of posts a day) will definitely find List and Threaded extremely useful functions.

Take a look at this topic under Threaded view:
http://nabble-support.1.n2.nabble.com/Help-with-Free-Support-and-get-access-to-Premium-Support-tt5652870.html#none
and see how easy it is to pick out particular posters names and whether any particular posts generated an especially long string of responses. Notice how Hugo's name always appears at the end of a string, suggesting he always posts definitive answers. You just can't do that kind of analysis in Classic view.

[mywaytoo]

With the Threaded view selected, surely Classic will be treated in exactly the same, unwanted way by Google?

Somehow that line/row needs to be excluded from Google altogether...

[Harvey]

GregChapman wrote

It depends so much on your userbase

Exactly. Of the 200 members of our forum, I know the most about html and web stuff, and I had to ask Hugo to design a feature that allowed me to DELETE ONLY THIS POST and move attached the ones below up to the one above the deleted.  Translation: I get why it's cool and how a guy like Graham couldn't live without it but for me it's extra work, and I risk deleting posts by accident.

There are probably a hundred ski forums in the US.  To my knowledge only one offers threaded functionality - it's call SkiVT and it is running on Old Nabble.  None of my potential forum members have any experience with the feature.  Further, Ski Forums are all about PICTURES (in season at least).  People want to post and browse pictures quickly.  Classic is the way to go.

If you get 5 emails a week from confused people who can't understand it it becomes a lot of work.  I've resisted putting a description in FAQ because I was pretty sure I wanted to eliminate it from the beginning 18 months ago.  I know that Hugo is a smart guy and he has tried to talk me out of killing it. I think I've given it a fair chance. Nobody is using it and Google views it as my most important keyword.

MyWayToo ... are you saying you'd like to get rid of it too? If so why?  If you do it (and succeed) I'd really like to know. I've made quite a mess of my code.

[mywaytoo]

Harvey44 wrote

MyWayToo ... are you saying you'd like to get rid of it too? If so why?  If you do it (and succeed) I'd really like to know. I've made quite a mess of my code.

Harvey... I'm too scared to try coding anything... perhaps when I have nothing else to do, then I'll experiment...  

I think the options are all valid depending on whatever best fits... My issue is that the text in that line/row/whatever should NOT be available to Google...

Ahhhh... display it as images! without alternate text of course...