|
You'd just need to make sure he was wearing a badge that said, "Come to CodeProject, it's a much nicer place!". 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
..not to mention that he'd then be able to be coloured using CSS. Hot Pink Bob? Not even Sean would go for that one.
cheers
Chris Maunder
|
|
|
|
|
Challenge accepted.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
Hi, I am not getting the password reset emails for my old username 'wizardzz'
I checked the spam folder, no dice.
|
|
|
|
|
I'll send you an email about this.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Some bozo is rapidly posting garbage, likely with a bot. See this post[^] by @Nelek. We used to call this a babbling idiot. Ours were often caused by hardware faults, but the term still works quite well here.
We handled this with a leaky bucket counter, which says that n events in s seconds is OK, and anything more is excessive. A bucket has credits (for events) and a timestamp. When an event occurs, the time since the last event adds a pro-rated number of credits to the bucket, up to its maximum of n. The timestamp is then updated to account for any new credits and the count of credits is decremented. If the number of credits drops below zero, the source is considered a babbler and is ignored for a while. If the babbling keeps recurring, the source is ignored for longer or until reenabled by an administrator.
You can use this to limit the number of events that an account can generate. It can even be weighted so that a new post uses more credits than a vote, for example. A limit of 5 events per minute might be reasonable, although this would somewhat hamper those of us who help to purge spammers by flagging the accounts in @phil-o's daily SAOTD post.
|
|
|
|
|
We do have limits. You can see he hit them. It's not as advanced as it could be, but we found that as we tried to make babble traps more sophisticated we ended up catching Real Humans and the babblebots would adapt (scarily fast) and break through.
Just like Apple found that people build phones better than robots, we've found people are better babble blockers than bots.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: people are better babble blockers than bots
But hamsters are the best!
|
|
|
|
|
![Badger | [badger,badger,badger,badger...]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/badger.gif) are pretty good too.
cheers
Chris Maunder
|
|
|
|
|
A panda doing jumping jacks? A rockhopper?
|
|
|
|
|
A badger[^].
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
That's what the text said when I copied and pasted it to try and figure it out, but it didn't look like no badger to me!
|
|
|
|
|
Hi all,
In Professional Profile > Reputation tab, the graphic shows data until today,
But reputation points is not complete
My rep is 185k but graphic ends at 158k.
In participant, it seems rep points of MVP rewards are missing, otherwise, points are missing in any category.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
Have a look to the date. In my case the history end in the popup shows 16-12-2019:
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
For me, history ends at 01/06/2020 (European date format: dd/mm/yy)
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
This is a known issue that is on our list.
Basically, the stored procedure for updating the tables used for the graph occasionally times out for members with a lot of reputation events.
Don't worry, you won't lose any points, just the graph may be missing some data until it is fixed.
And since this is an issue for high rep members, the difference is really not that significant, it still shows that you are amazing.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
Thanks for information.
Hope you have time to fix it soon.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
Between 11:22 and 11:25, this article[^] was bookmarked 42 times. Yes, it was updated today, and yes, it's a good article, but seriously?  I received author points for this, but the article itself (unless its statistics lag) still only shows 13 bookmarks, which is probably what it had before all this happened. You may want to check if the hamsters are boozing it up or someone is testing a pile of bot accounts.
|
|
|
|
|
Each time someone bookmarks or adds an article to their "read later" list you get bookmarks points. If someone removes the bookmark or article from a read later list the count goes down. The count of bookmarks next to an article is for bookmarks, not "read later"'s.
cheers
Chris Maunder
|
|
|
|
|
I get that, but 42 bookmarks in 3 minutes struck me as rather suspicious. I suppose it could have been someone telling all their developers to read it, but I suspect not.
|
|
|
|
|
See the post[^] below. This is not fixed.
Setting a margin for an article's first image works, but its width is always 700 (the same as the article), so setting a margin causes the image to go beyond the right margin.
It displays correctly when previewed before submission, but something goes awry during submission. If you look at the HTML, the first image is called out the same way as the others when previewed. But after submission, it's called out in a completely different way than the subsequent ones, which remain OK.
EDIT: The article[^] is up, and unless Sean corrects the first image, you can see how it displays, even though it was set to width=500 (an experiment that failed) and margin=50. The callout for the first image is
<p><img src="/KB/cpp/5269493/image1-r-700.png" style="margin-left: 50px; margin-right: 50px; cursor: pointer; border: 0; width: 700px; height: auto"... whereas the callout for the second is
<p><img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" style="width: 600px; height: 183px; margin-left: 50px; margin-right: 50px"... with the subsequent ones following the pattern of the second one.
modified 5-Jun-20 8:53am.
|
|
|
|
|
Out of curiosity why are you setting the margin? If you want it centered then "margin: 0 auto" is the way to go.
Our issue is we're trying to have as consistent a look and feel as possible while accepting that authors don't always follow the rules or understand how to keep the HTML clean (eg pasting from Word or WordPress).
Generally we don't want margins and spacing and styles applied to any elements in an article. Focus on the text, place the images, and let the content speak for itself. Simply removing all style attributes helps this. However, we understand that there are times where some formatting such as wrapping text around an image, centering etc can really help, so we need to keep some styles.
In your case you've hit an edge case we haven't dealt with. The quick answer is to remove the hardcoded margins so our image resizer works. In other cases an image may be floated and then have a margin added to make it spaced better, so a margin does make sense. However, that margin should be in our CSS, not hardcoded into the image itself. Even then, floating an image that's wider than (700 - margin - minimum-width-of-side-text-that's-readable) will just look bad. That's a tricky but not impossible task to automatically fix, but so rare that we prefer just to manually fix.
cheers
Chris Maunder
|
|
|
|
|
I was trying to shrink the image (saved as 700 pixels wide) to 600 pixels wide and then centre it. At 700, the fonts in the image are outsized compared to the article. The other images worked great when setting them to width=600 and margin=50 so that they'd be centered. But if you prefer no margin, that's fine with me. I'm not really looking to change the layout, just trying to compress the images while preserving their aspect ratio. There may be a way to do this before uploading the images, but I just get screenshots the way OriginalGriff describes in his article: use Dropbox to get the image, and then crop it with Paint.
|
|
|
|
|
The absolute easiest thing to do is take your screenshot and just upload it. We take your uploads and automatically resize them (and also creative smaller images for responsive layouts like mobile devices) without you needing to do anything. A large image will be shown smaller, with a link that, when clicked, will show the original image full sized.
cheers
Chris Maunder
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
