We have discussed it, and it seems like an obvious indicator to bring back... the old system wasn't very robust though, and was based on the use of a @microsoft.com email address in your profile, so we'll probably create something that relies upon access
to our internal network to validate. Some employees have expressed a dislike of an indicator though, thinking that everyone should be treated the same and that an indicator suggests some sort of special status.... any thoughts about that?
We have discussed it, and it seems like an obvious indicator to bring back... the old system wasn't very robust though, and was based on the use of a @microsoft.com email address in your profile, so we'll probably create something that relies upon access to our internal network to validate. Some employees have expressed a dislike of an indicator though, thinking that everyone should be treated the same and that an indicator suggests some sort of special status.... any thoughts about that?
Yep, we do a certain amount of filtering during input (whatever the edit control does plus little else), then we do the major filtering during output... that way we leave your source alone... if we have a bug or we if are being overzealous with our filtering, it isn't a permanent issue.SlackmasterK said:Duncanma said:*snip*
Right. When I put <div>'s in a post, and apply a style, and it disappears... if I edit that post, the styles are still there. Must be a filter between the select query and the browser. It seems to store the style along with the rest of the content.
re: "bug in formatting" -- like the imfamous W00terz thread?
Since this is from July 19th, I'm betting this was the case... but was fixed when we fixed the other similar issue. They were, as you suggest, probably the same bug.CannotResolveSymbol said:I can reproduce this issue by following this link, then clicking the button to show the previous page: http://channel9.msdn.com/forums/Feedback/416345-Paging-Bug-w-Go-to-last-page-test-case/?CommentID=416372
Looks like this could be related to the "Posts not showing up right away" issue. The symptoms are more or less the same.
let me know if you still see the issue.
So... your original Lloyd_Humph account was userid/password sign in? or Live ID?
and you want it tied to the same Live ID as this account? or to a different one?
I'll take care of this for you, once I figure out the right action we are looking for.
I'm sorry there was a miscommunication about it.
So Duncanma what is it that Silverlight 2.0 will have to offer that cannot be done in Ajax? I know it looks better, but I'm more concerned with the features you've removed, why they have been removed, and whether Silverlight 2.0 offers a solution.
As I get older, I'm becoming very cynical about any new technologies that supposedly solve problems, as they almost always fall short at some point. Ajax seemed so promising but the stateless nature of it is problematical. You have what is essentially a ‘hack’, and then all this high level code to imitate state that is very very tricky to implement, and the related bugs are hard to reproduce thus eliminate.
For me the biggest disappointment is the loading circle. It seems the traditional HTTPGET/RESPONSE flicker has been substituted for this. In the real word you guys are in Seattle and I'm in England, so it will always take a little while to pull the data from your servers to my PC. The connection I have is also a major factor. That considered it does appear to me that Ajax as a technology was very limited to begin with, and the more data you have to send, the more inefficient and problem filled it becomes. It is only every best used in places like the following in news websites like The New York Times beneath
As far as the use of AJAX and your connection... the idea is to send less data than a full page refresh, which (in theory) should help you out, not hurt you. The initial page load contains the data for that first page, so that doesn't really involve any AJAX at all... but then when you page, instead of sending down 80-120k for the page, we send down a much smaller amount just for the new entries.
I doubt we should really continue on this pathBas said:Duncanma said:*snip*
I still think the spam button, with the idea of x votes == hidden ... with votes being weighted based on the user's history on the site ... is a good model. The other option is moderators ... which has many benefits above any automatic system ... or (and I think this is where we are headed now) a combination where users flag content as spam, and moderators are shown a quick list of flagged posts to make it easier for them to notice any inappropriate content and decide if action is needed.
Jeff mentioned to me today that it gets slow for him from time to time (the word being used was 'pokey', but I can't remember if that was his word or mine). We are aware that there are stability issues, and when the site goes down it slows down for a bit afterwards.jamie said:jeff.... you find this site consistantky as fast as the old site? ..or even consistant?
C9v3 used to crash the app domain as often as every few minutes... and would get slower and slower over a few hours... until we finally scheduled the app pool to recycle every hour or so. I'm not saying that was better or worse, it crashed much more often but recovered faster... bit of a toss up there ... I'm just pointing out that we aren't coming from an idyllic situation to a horrible one... in fact, I'd say that stability has improved overall. People were complaining on a regular basis with C9v3 that they would lose their posts after clicking add, amongst other errors, as just one example.
I already failed your challenge by the way, right after reading it I found an error on the /shows/<show name>/ page and deployed an updated DLL to fix it. My apologies