|
oh okay. great.
Ravi Khoda
|
|
|
|
|
...is very useful, but...could we use a different symbol (or better, a combination of symbols)
SQL Parameters are often prefixed by an atsign, and this question[^] just accidentally emailed six members...
How about !OriginalGriff! or similar? A lot less likely to be used accidentally.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
7 members in fact.
To be fair nobody's going to remember any other convention.
And it's a good addition to the site, changing it's useage will just make it unused and that won't be a good thing.
Maybe a warning to say 'so-and-so' will be notified will be better.
|
|
|
|
|
Blue Waffle wrote: Maybe a warning to say 'so-and-so' will be notified will be better.
Because users read and pay attention to warning messages, right?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
What are we talking about here.
Sometimes somebody somewhere might get an e-mail notification that wasn't meant for them. It's not really a big problem is it?
The original solution was to inconvenience everybody who wants to notify somebody in a post by trying to remember an alien convention.
My solution was to provide a warning. If a user ignores it, who cares?? The worst thing that is going to happen is somebody gets a wrong e-mail notification.
|
|
|
|
|
As I see it, there are two problems:
- The user receives a notification that's nothing to do with them, and could be seen as spam. Users with shorter usernames (eg: P[^]) are likely to get inundated with spurious notifications.
- The notification reveals the email address of the user posting the message, which is unlike any other notification sent from the site.
Even when you know about the feature, you can still get caught out, as OG did in the thread he linked to.
I'd be interested to see how often this feature has been used intentionally.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: I'd be interested to see how often this feature has been used intentionally Although I don't know the answer to that, I used it intentionally and successfully in this thread[^]
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
If the SQL code is wrapped in PRE or CODE tags there won't be a conversion. I've gone ahead and edited the post to wrap in PRE tags.
|
|
|
|
|
According to my reputation history, at the time of writing this post[^] had 1 x 0pts spam/abusive report and 3 x 24pts upvotes. However the actual message doesn't show the upvotes (or indeed appear green) Is this because the earlier 'abuse' report ensured that the future upvotes weren't displayed on the message?
|
|
|
|
|
The post's rating is 3.86, and (AFAIK) you need >= 4.0 to see green.
I am not sure why someone spam/abuse voted that message, though.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
|
|
|
|
|
Brisingr Aerowing wrote: he post's rating is 3.86, and (AFAIK) you need >= 4.0 to see green.
I don't see that. Where are you seeing that it use to be bottom right of the message.
|
|
|
|
|
Check your messages[^] page
thatrajaCode converters | Education Needed
No thanks, I am all stocked up. - Luc Pattyn
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is - Henry Minute
|
|
|
|
|
Thanks. But if you check the actual message[^] itself there is no indication that it has been upvoted, which I think is a bug. Other messages that are upvoted, even once (with noise set to - very high) shows up as green and displays number of upvotes. This message doesn't and it appears the reason why is some other person marked it as abusive.
|
|
|
|
|
Yes, but a message with one up-vote has a rating of 5. Your message has a rating of 4.11, which is presumably still less than the limit for changing the title to green.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Everytime I see one of his(?) posts I have to fight the urge to abuse vote his account for naming itself after a grossout picture. Maybe someone else was a bit more trigger happy.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I suspect it's more likely that someone objected to him using the word "w*nker" in the Lounge.
Either that, or it's a 'Merkin without a sense of humour.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
It's certainly in the list somewhere. Try changing the "Sort by" option to "Modified (New - Old)", and it's the first result. Or change the "Match" to "Title", and it's still on the first page.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Guys, I'm afraid but you seem to have multiple glitches in your hamster matrix [Yeah, I had to come up with the horrible article vanishing bug again I rest that one and trust you]
If an article has the status closed it can still be accessed over the mobile version of CP.
The scariest moment is always just before the Start - Stephen King Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
Which article?
(Just met with Matthew about bug #1 and it's a combo of edge case logic and wording that caused the issue. The code is doing exactly as we asked it. It's just not doing what you expect, nor is it warning you. This is being fixed right now)
|
|
|
|
|
This one[^] was still accessible after I closed it because one of the Zip files contained a Virus (The virus Zip is gone now, ask Sean for details - I informed him). Remember: The bug will obvisously not appear now, because I repuplished it after the Zip removal. The Zip wasn't directl linked in the article, we gave the author the benefit of the doubt.
I have just reproduced it with this Tip/Trick of mine[^]
Chris Maunder wrote: combo of edge case logic and wording that caused the issue. The code is doing exactly as we asked it. It's just not doing what you expect, nor is it warning you.
Oh the joy. I was at points where I had to say almost the same words. Happy fixing
The scariest moment is always just before the Start - Stephen King Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek
|
|
|
|
|
XML Parsing Error: unexpected parser state Location: jar:file:///C:/Program%20Files%20(x86)/Mozilla%20Firefox/omni.ja!/chrome/toolkit/content/global/netError.xhtml Line Number 311, Column 58: &netInterrupt.longDesc; ---------------------------------------------------------^
|
|
|
|
|
|
Is this an official reply?
|
|
|
|
|
As I'm not a member of the CodeProject staff, no it's not. However, the error message you posted clearly points to a problem with your local Firefox profile.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|