|
Sorry: I meant anything outside of our systems we can't test. We can ping / tracert from us to your ISP but that probably won't tell us much. Sounds like there's a block in there somewhere
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Sounds like there's a block in there somewhere
Yes, you're correct. Our WatchGuard firewall appliance was incorrectly blocking the site. Thanks to @jeron1 for assisting with that.
Download attempts for the article's source code are still timing out, though. It starts off like a bull, traffic slows down to fits and starts for a bit, and then everything goes quiet.
Thanks,
Jeff Bowman
Fairbanks, Alaska
|
|
|
|
|
Jeff Bowman wrote: WatchGuard router
Interesting...within the last week CodeProject is blocked at work by the WatchGuard router, they claim that it is being detected as a botnet. I'll have to work on the boss to make the exception. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
 We'll ask our IT guys to dig in and see who they need to slap to get this sorted.
cheers
Chris Maunder
|
|
|
|
|
I'm not sure what happened, I've used this site for years at work, then all of the sudden nothing but connection timeouts... Maybe a WatchGuard update botched things up, the fact that someone else had a similar issue seems too coincidental.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
This was exactly the issue. I'm not sure why I didn't think to check for it, so your suggestion was very timely.
I added an exception for *.codeproject.com and all was well.
Thanks,
Jeff Bowman
Fairbanks, Alaska
|
|
|
|
|
 Good to hear!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Greg Utas wrote: he'll be told that he was mentioned in a post and will come running to see what the fuss is about.
That's discutible   
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Message Removed
modified 19-Mar-21 21:01pm.
|
|
|
|
|
The link is now inside the code blocks (I have a feeling it used to be above), with the result that any copied block includes the "Copy Code" text at the beginning.
int main()
{
printf("Hello, world!\n");
}
|
|
|
|
|
That includes using the "Copy Code" button:
Quote: Copy Codeint main()
{
printf("Hello, world!\n");
}
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
All fixed!
cheers
Chris Maunder
|
|
|
|
|
Lots of QA questions explain a problem, then under "What I have tried:" they just repeat the same description.
Suggestion is: replace "What I have tried:" by something more specific that better matches what we want to see there, e.g.
"What I have tried after the problem occurred:"
"My first attempts to solve the problem:"
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
From my point of view this "What I have tried" is anyway useless. Some place a copy of the question there others simply fill enough useless characters until post is accepted.
Simply remove that useless "What I have tried"
Only a noob's view.
modified 27-Mar-21 21:01pm.
|
|
|
|
|
No, it does help in some cases. It makes some - not many, not enough - think about the question and put some information in. Before it was there, we got a lot more "My code don't work - fix it?" type than we do now.
Problem is the lazy ones won't read anything in case learning is accidentally imparted ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
My policy would be strict:
1. give clear, concise, unambiguous instructions; improve them when possible.
2. for all: ignore who ignores the instructions, not even a lengthy "Bad question..." response
3. for moderators: do not remove but respond with exactly one sentence "bad question, to be ignored" (*), remove any other response that may appear, and freeze the question, thus preventing further edits/comments/answers/solutions. Offenders should not be rewarded! They don't deserve a second of our attention.
(*) make this a link to a lengthy page that explains what good and bad questions are
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
But the main problem is not that people ignore the instructions, they do not bother to read them. And far too many just do not know how to ask a question. One of the most common questions is "It does not work, please fix it". So however hard Chris and the team work to make it easy to post a question, add full details and nice neatly formatted code, people will still do what they think is enough.
|
|
|
|
|
And then we ignore them, as there is no alternative.
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
well, as Chris says, we should try to help everybody, even those who appear to be useless or lazy. At the very least we can tell them why they are not getting the answer they expect.
|
|
|
|
|
I will stimulate initiative, creativity, curiosity, and learning in general; I will not reward lazyness. If that doesn't fit this site, then good luck to you all.
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
I agree with you, Luc.
My philosophy is to help everyone who needs help, but I do ask that those who need help take the time to think, even briefly, what they are asking for.
If you try, but can't frame a question perfectly that's fine: we can work it out and (in a perfect world) rephrase the question for you.
If you come in, yell something incomprehensible, and then ignore requests to clarify your question, then no, we can't help. You've made it clear you're not interested in participating, in helping us help you, so even if we help that help may not actually even be read.
cheers
Chris Maunder
|
|
|
|
|
I sympathize, but that policy would also result in a lot of "CP sucks" talk, similar to what some of us think of SO.
|
|
|
|
|
I don't normally disagree with you, but in this case I think I have to.
Many first time posters are lucky to find the right place to post, much less actually read instructions when they get there. And they are often panicking - they have a deadline for their homework and no idea at all how to proceed: they can't find code which does exactly what the question requires and that'#s all they can think of doing.
So they find us: a friendly looking bunch who'll do the homework for them! So they dump the question and ... it won't let them post it without something in the "What I done" bit. So they dump anything they can find in that.
And they get nothing back except a closed "Not a question".
That doesn't help them, doesn't help the site - instead it gets someone who thinks we are all w*nk*rs and bad mouths CP. Just as happens with SO: because the attitude there is "I'm wonderful, newbies should know better".
As the text says:
Quote: Let's work to help developers, not make them feel stupid.
And while that's damn difficult sometimes - I told one poster today that I wasn't talking to him any more because I'd be rude if I did - some of them do respond well, and need some constructive discourse to get them started.
Closing the question doesn't allow for that.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It's often not used properly, you're right.
But I'm not sure changing the text would be enough - the problem is that some Querists have no idea how to ask a question and refuse to read anything in order to learn. That's generally why they are there: they don't want to learn anything, just get code they can hand in as their own work with no effort on their part.
It does prompt some of 'em to actually think a bit though - which is what it was there for!
Not sure what would get the terminally lazy to actually think a little bit - other than electric shocks and the API for that is difficult to install ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: terminally lazy
A subconscious pun? I caught it right away because of timesharing systems. Two dinosaurs walk into a pub... 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
