The criticisms presented there seem to essentially be criticisms that could be thrown at any charity. None of them registered as problem with the foundation itself. In some of the cases, the only solution to resolve the complaint is to lower or eliminate the amount donated.

Sorry, but those people complaining are going to complain whatever happens.

That's the thing. People look at Google Wave as the interface. The real interface is all the things they are using every day (Gmail, /. comments, Facebook, Twitter, etc) integrating into Wave.

Email is the same way. Systems integrated email, and now email is useful.

Sorry. I didn't get into too much detail because I've done it so often. Wave is a pretty big idea, so it's reasonable that it might be difficult to grasp what it can be.

I'll try. Keep in mind I'm not known for brevity.

My elevator pitch would be: Wave is a real-time content sharing system. That's the best I can come up with right now, though I think it fairly describes it.

Now, it doesn't sound impressive, but it really is, and better expressed with real world examples. This is easy.

Let's look at this threaded conversation here. If I hadn't come back here looking for any responses, I wouldn't have known you'd respond. I have to come back to /., find my post, and than dig through all the replies.

This entire commenting system can be duplicated inside a Wave. That doesn't mean comments here have to change. Rather, they are linked into Wave. How? The same way email is used currently. However, instead of using an email address, you'd use a wave address.

In fact, anywhere email is used, wave can be used as well.

Now, you're probably wondering if this is the case, why not just use email? The thing is, email only works in one direction. You email me. I email you. Wave works off the premise that communication is bidirectional. So, if /. comments were in Wave, I'd be able to use my Mozilla Thunderfox (My imagined Mozilla Wave client) to see the comments, as well as reply to /. from the client.

Of course, here is where it get's interesting. As I said, I tend to ramble quite a bit, so I'd want to bring in a friend that can better explain this to you. Maybe a bit more concise. Worded nicely, and a lot shorter. He'd do a better job, so I'd share him with the conversation in Thunderfox. He'd be able to see what the conversation is about, and add his own two cents. He'd reply to your comment. He'd also reply to mine, making some mention about how I can't shut up.

He'd also drop in the video of Google showing off Wave, just in case you missed it.

All of this would appear on /. in real time if they wanted.

Being the smart dapper guy I am, I'd steal my friends concise comment, and put it up on my blog (iDontKnowWhenToShutUp.BlogSpot.com). The blog post would let people comment. All 1 of my readers would, probably something like "Honey, don't forget the milk." Everyone subscribed to that Wave (You, my friend, me) would probably be able to see that.

This is all done in real time, on a standard base. Real time communication. Maybe a better way to think of it is IRC meets Email.

This handles a lot of the cases where developers have to create their own APIs to access the inforamtion in a system. If I want to develop an application that posts updates to various social networks, I have to learn a different API for each place. Integrating Wave into these system kinda negates that need for the content sharing side.

I'm not a Wave expert. I'm not going to pretend to know everything. But Wave's goals are big. If they are realized, it will be bigger than email. The problem is, it's so big, so ambitious, it can get rather confusing.

Hopefully I've gotten you thinking. My examples aren't perfect, but I'm sure if you sit back and think for a bit, you could see all the possibilities.

It's actually not difficult to see what it can be used with. Basically, anything you type can be a wave. Any content you create can be a wave. The problem is people see Google Wave as the product. Google Wave is just the interface. Gmail would be useless if Email wasn't as widely used as it is. The Wave protocol exists for a reason.

These comments here could all be waves. Facebook could be based on waves. Forums as well. You would still use the same interfaces as you do now, but you'd have the added benefit of a standard API to access that information, the way email works today.

Google Wave is Thunderbird. Wave is Email.

Having worked in this environment before, you'd actually do better. You'd give the person their money back, and comp them something. However, people doing this all the time would be asked to leave.

People assume the Casino's are just crooks. That's not really fair. Problems can happen. If someone wins legit, fine, they get the money, and that's it. However, if something goes wrong, things are adjusted. On both sides. Yes, if a machine breaks down and ate someones money, we get the person's money back, comp them something, etc. They are then free to take that money and try again.

Just because you lose and the machine was broken doesn't mean you would have won.

So Steve got trolled. That doesn't inspire confidence. His response also shows that he felt that he had to respond, so I don't think these are minor complaints, but ones he has to fire back at. I also feel like he's getting this from other sources as well. I have to say, for him to respond so, I have to wonder how much pressure he's under. After all, what's next for Apple?

It's actually not that bad, and it doesn't take long to get into the understanding. SC2 goes a long way toward assisting with all the micro and macro elements of the old SC. Matchmaking is also pretty good. I'm horrible, and play in the Copper ladder, and I when about half my games. They are challenging and fun, and I'm slowly seeing improvement in my game. I don't feel like I'm getting rolled all the time. I can usually look back on games and say "Yup, I should have worked on building an army and not just more drones." or "I failed to properly keep tabs on my opponent and he kept tabs on me, and that let him trounce me."

At the same time, I've also learned how to keep fighting and still remember to build units back at the base.

The thing is, SC2 is gonna be around a while. So I know the number of hours I get from the game will be worth it from a dollar's spent pov. It's like TF2 in that regard. That game was well worth the price (even moreso because it was in the Orange box).

As was posted in previous comments, I also don't think the document is really anything to cry home about. The truth is, reviewing the document left me a bit more comfortable. They clearly spelled out what they did and didn't track, and I actually found out that they track less than I thought they did.

Dice are already marked. They have pips or numbers on them. Opposite sides add up to the number of sides on a dice plus 1. So if the number 1 was on the bottom, number 6 would be on top.

Granted, this works for some dice, like d6, d8, d12 and d20. d10 are odd/even, and equal out to one less then the total number of sides. So 2 and 7 are opposites.

d4s are usually easy enough, but depend on the type you get. The one I have has the number on the top, and the number doesn't appear on the bottom.

Basically, the point is, most die follow a set of rules for number placement. If you can read the bottom of the dice, you can easily tell what number is opposite of it.