|
It really is quite difficult for someone new to find (come across!) the way to navigate message-room entries.
I refer to this:
"Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages."
Yes, it's hidden at the foot of pages like http://www.codeproject.com/Forums/1645/Site-Bugs-Suggestions.aspx[^], but not at all explicitly obvious to one entering the 'forum'.
I managed to forget since my last visit (why should I have to remember? I have enough things to do), and it took me an age to find it again.
At the very least, "navigating entries" could be an item in Help.
You could even put it above the chosen format selector, where it would be obvious.
Then it would save me from rsi & not overload my brain.
|
|
|
|
|
It's just a quick key reminder - you can always do things the old way and click with a mouse...
They only have a certain amount of screen real estate - I for one am happier with the content taking precedence when the page loads and the hints left to the bottom where I can scroll to them if I need them.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
|
Yes, comments are tied to specific versions in order to allow members to post comments while author's fine tune their article during the composition and approval process.
An example is that you post a new article and it's in a Pending state while members approve it. A few members find fault with it, and you make those corrections, and then the article is approved. The comments related to corrections should not be included in the final published version of the article.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
This error can be reliably reproduced by trying to preview a message that only has newlines in it.
|
|
|
|
|
This is in the forums, right, with "live preview" disabled in your settings?
I can replicate. I've tried. Lord knows I've tried. Even the error logs aren't showing anything.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
It's in the live preview, sorry..
|
|
|
|
|
Try as I may I can't reproduce this.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
Ah. Can you try disabling AdBlock Plus and seeing if that helps?
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Ok I disabled AdBlock Plus, Ghostery and even NoScript but it didn't help.
|
|
|
|
|
I've made a change. Any change your end?
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
No, I still get that error (I disabled the add-ons again).
It's also doing it in Chrome.
|
|
|
|
|
|
Updates now get put into the "awaiting approval" queue, the same as new articles. You can check the new process here[^].
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
There's a checkbox, highlighted in yellow, at the top right that says 'Work in progress - do not publish. Uncheck to publish'. I'm assuming you unchecked this and found it didn't help (at least that's what I found when I did it).
Looks like we have a version issue with your updated version. We'll get this sorted out very soon.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
It is still in composing...
Its the man, not the machine - Chuck Yeager
If at first you don't succeed... get a better publicist
If the final destination is death, then we should enjoy every second of the journey.
|
|
|
|
|
Thanks, it is fixed now.
Its the man, not the machine - Chuck Yeager
If at first you don't succeed... get a better publicist
If the final destination is death, then we should enjoy every second of the journey.
|
|
|
|
|
|
|
Spammers seem to employ people from all over the globe to hit certain pages with certain text. I've tried blocking by IP, keyword in their name, email address, Bio, but in the end the best solution, by far, has been the Report button and the Spam and abuse forum that allows you guys to seek and destroy.
Maybe we could award badges for those who kill spam
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thank you for your reply, Chris.
I can imagine how difficult this problem can be. I have done couple works or so to fight spam in a very simple case of a "Contact us" Web form and shared my recommendations in several Q & A answers. A naive approach in processing of such form would allow for an exploit turning the host into a zombie sending spam in no times. I remember your post showing that, for example, CodeProject is protected against JavaScript injection.
The problem of the spam through the formally legitimate post is much more difficult.
Did you ever considering Bayesian filtering? Please see:
http://www.paulgraham.com/spam.html[^],
http://www.paulgraham.com/better.html[^].
(I do not really appreciate each and every opinion of Paul Graham; this is just the first place I faced with the Bayesian filtering. I used such thing for a while for a-mail filtering (not anymore) and know the problems of this approach: false positives.)
Even though the filtering is dangerous due to false positives, it could be used not for final removal, but just for marking the post and the offender for final removal, but only when confirmed by a person. It could be used to form a list of notification for the site support.
In other words, the only way I can see right now it to greatly speed up, simplify and streamline the process of removal of bad posts and accounts. Right now, the process of getting all the references and reporting on them is awkward enough, so new spam posts appear before the bad account it disabled, which is the most critical time. When people just report on posts and/or remove them, accounts remains active for a time which allows bad people to spam more, which makes this time a bottleneck. I understand that you physically unable to act faster in such situation. Filtering is merely one of the directions where this time could be shortened while reducing waste of time. Just some extra automation.
The idea of the badges or other encouraging awards is good.
I can easily picture myself wearing the badge. First which comes on mind is the well-known coat-of-arms of Moscow:
http://en.wikipedia.org/wiki/File:Coat_of_Arms_of_Moscow.svg[^], where a thick-bellied CodeProject mascot could be placed instead of St. George, and Serpent to be hit with the pike could be… I don't know, maybe a "Cristian Shoe" or a "Tiffany bag"…
Cheers,
—SASergey A Kryukov
|
|
|
|
|
I *love* the badge!
However, I love the idea of Bayesian filtering the messages even more. I've never written one before: maybe time to learn. Training would be simple because we'd use the spam/abuse reporting system to show it messages that were to be marked.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|