Yes, because the purpose of putting very minimalist information in a self-contained post is an obvious attempt at "exposing" you of some sort. Lol.
Yeah, I'm sure you had some other goal in mentioning my full name and posting a picture of me. How stupid of me.
It's funny how this post clearly shows that this is the other way around. And clearly satirically mentioning the idiom "wantreprenuer" means I'm taking it seriously. Your assumptions are still laughably inaccurate.
How so? I don't see anything that could possibly lead you to that conclusion.
Have fun setting yourself up for failure. I'll be there to savor that day. Also, what I think lowly of you if you will is all pretty much warranted. Just for clarification.
It's funny because the majority of our arguments usually never have a concrete basis. It's usually over something woefully pointless and stupid that truly has no right or wrong. And when we do have such arguments, I'm pretty sure the case is quite the contrary, Smartt.
What were some of the recent arguments we've had?
The first two that come to mind are "hg vs git" and "struct vs class in C++" (or "Is it possible to write OO code in C?").
Who "won" those? I recall you being woefully stupid on the topic of hg vs git (you claimed that git's popularity somehow made it a better candidate despite that hg has a plugin for interacting with git repos).
As for class vs struct,
http://pastebin.com/9ghMUGAt
In other words, this is your way of crying me a river. It's too bad I've been disappointed in you from the get-go. So suffice to say, there's no shame in my game
@Edit: We've been over this, purse. You can't call someone clearly smarter than you--someone clearly superior--an idiot in any way, shape or form.
@Edit2: See above. It wouldn't have a valid premise. It would be just as meaningless as the rest of what you say is.
Do you even understand our argument?
Edy told me that the fix could not be done in GSI because you cannot trust client data. That is absolutely ridiculous. The whole point of using GSI (in this case) is to
avoid trusting client data.
My solution requires a very small change to the friend request method of GSI.
1. When someone attempts to add a user, a GSI request is made. When this request is made, it should be identical to making a friend request on the actual site (i.e. that user gets a pending request, which didn't happen the last time I checked).
2. When someone "accepts" a request, verify that they have a pending request from said user.
That's all. Fixed. No need for changing every game. This fix would be compatible with
all games.
Edy's fix would only be compatible with updated games and towns 2.0. I tried to tell him that wasn't necessary, but he wasn't able to understand what I was saying. I'm completely justified in telling someone with several times more experience than me that their solution is fucking stupid and that they should consider a new job if they aren't capable of understanding that it's possible to verify the authenticity of submitted data on the other end.
Edit/Correction: The use of GSI here is not to avoid trusting client data. It's actually to avoid having to alter every game to solve a problem. In other words, it's exactly what Edy should have been doing- well, telling someone else to do. Instead, he avoided the tool that exists for the purpose I'm pointing out, and is going for a much more complicated route.
Benefit of my solution: Friend requests in games get fixed. Now, not later.
And a lot less work is required.