fanboyslim

I'm playing my career mode and my player made it into the Grizzlies (still coming from the bench.) I was surprised to see that in this mode the AI is consistently giving Temple and Anderson the start over Brooks. Then I thought that might not be so unrealistic. After all, Anderson is this year's big FA move, and Brooks hasn't proved he can be a full time SG yet.

Let's hope that the beginning of training camp makes people check the boards. I suspect some not so frequent posters may not have noticed they're back up yet.

I've heard that argument and I don't agree with it either. However I think the more rational argument for losing the pick this year is that we're very likely to get worse in the next 2 years as our core ages / falls out of the roster with no comparable replacements. Unless JJJ has a Donovan Mitchell like rookie season (and nothing would make me happier) it is probably better to try and lose the pick while we have at least some competitive chances and keep it for the full rebuild when we will truly suck. I prefer to lose the pick this year and make one last run for the playoffs, but if the wheels come off before December and we go into full tank mode I won't be complaining too much. In the end we're arguing about a choice of eating crap for lunch or for dinner. It's going to happen, and it's not going to be fun either way, so we may as well get it over with as soon as possible.

I just started playing and let's just say someone I will not name got injured in the second game (out 4-6 weeks) and now I have a 3-14 record. Also, someone forgot to add the "can pass the ball" option to MarShon Brooks. By the way, the new baby blue uniforms look hideous.

I definitely will. Part of that feedback will be to ask why they're having a survey about Grizzlies.com in a grizzliesonline.com site.

This outage was different from the ones of years past. It wasn't just the server going down for a few days. This time the whole DNS domain (grizzliesonline.com) was docked, which is a network management issue as opposed to a server/boards issue. In fact the initial error page was just a standard hosting company page telling the users "contact your admin because he or she forgot to renew the domain or missed too many payments." There are many reasons this could happen but they could all be fixed in a matter of hours by the hosting company as long as someone noticed at the server admin's end. Interestingly, if you go here and check the historical data for the domain it looks like it was owned by a company called SoftLayer Technologies (owned by IBM) from 2012 until last month, when the domain was picked up by several companies in succession (maybe domain squatters who tried to take the domain once it expired, but I can only speculate) until last week when it was again picked up by Amazon and what looks like the current and final domain owner (probably a retailer who uses Amazon infrastructure.) I suspect this is the actual reason for the long outage: the Grizzlies were not in control of the domain for about a month. By the way, for a hosting service setting up a generic landing page ("We're under maintenance") when a server goes down is trivial. I mean, it should be set up ahead of time so that when the end server is not reachable all incoming traffic is automatically redirected to the landing page (instead of the error page,) but I've done this on the fly and a simple page can be set up in a matter of minutes. All of this put together is why it looks like the boards' infrastructure is maintained by a part time intern rather than a professional IT organization. To be honest, I think the Grizzlies' online focus is clearly on the big social media platforms like Facebook and Twitter, which reach many more fans than the forums could ever do, and that's why the forums are just an afterthought. And it's a pity, because as much as we like to complain about the forums' content it's far, far better than most sports forums out there, let alone the cesspool that is Facebook/Twitter.

I obviously don't know the technical details of what happened, but I am an IT support manager in a large corporation and from what I could gather looking at the errors that popped up during the outage, this had all the hallmarks of a major screwup (or very poor planning amounting to the same) by whoever is managing the server where the forums are located. It looks to me like the server was relocated to a new hosting service, and rather than doing the necessary work ahead of time to minimize service impact someone just flipped the switch on the server and suspended the hosting service, and then went away to work on it for a month. All of this without prior warning or an explanation after the fact. I know the forums and their users haven't exactly been a priority for the Grizzlies' organization for a long time, but come on. Isn't there anyone in the whole organization that can spend ten minutes writing a post explaining what happened? But even if we don't matter much to the organization, what I can't understand is how the Grizzlies can tolerate a month long outage in a public facing service. I mean, these aren't some random fan's hosted forums. They're the Memphis Grizzlies forums, and they're directly accessible (or, as it were, not accessible) from the franchise's official website in NBA.com. As an organization with a budget of hundreds of millions of dollars and an owner whose company's motto is "connecting everyone, everywhere," I'd be more concerned about the unprofessional public image this outage gave than about the rumblings of us poor users. Anyway, sorry, rant over. At least training camp is around the corner.

*shakes fist* Will they stop at nothing ?

Video has surfaced pointing to the Chinese

Isn't that a freight container?

I stand corrected.

You do realize that Steph Curry led the NBA with 4.2 three pointers made per game last season, right?

In the other leg. In fact he has now a couple more joints in it.

If only the Grizzlies had an expert in statistical analysis and data reconfiguration.

Of course. Breatharians can synthesize ligaments and bone out of thin air if needed.