https://intermediate-and-advanced-software-carpentry.readthe...

https://peps.python.org/pep-0020/

Okay, so now you've removed humans from the voting process two MORE levels, and introduced two MORE possible places where votes can be hijacked.

Never mind that the constitution CLEARLY disallows a direct vote by the populace ( https://en.wikipedia.org/wiki/Twelfth_Amendment_to_the_Unite... ), and the electors can vote for whomever they want and are answerable to nobody since their identities are not known.

All this technology can still be undone by the electors, and until the constitution is fixed, none of it matters.

That said, why create a "tick" when the perception of that tick can vary by individual? When I go into code mode, 10 hours can slip by in an instant, and I'm not hungry or thirsty until I come out of it.

Perhaps it's just an affectation of focus, as time still "ticked" by at it's normal rate.

Einstein said that the effects of time move more slowly the closer you get to C, so it makes sense that C would be the univeral "tick" if this was a simulation. As evidenced by Mars rovers and Voyager, an earth clock on another planet or in space still ticks at the same rate (Voyager and Mars are moving through space at the same rate we are moving around the sun, about 61,000km/hour).

There's no other reason for light to move at a steady speed, and nothing apparent that's stopping it from going faster.

For example, Uber appears to be the end of the taxi business, but it opens up a whole market to developers. You have a beautiful imbalance now, all those taxi drivers and cab companies are heavily incentivized to compete with Uber or lose their companies/jobs.

If there was (and there might be, idk) a platform that allowed all the cab companies to aggregate into an uber-Uber, there's a market for that with known customers. The only obvious issue I see is that in order to make this work, the cab companies would have to give up their fights to block Uber using municipal codes as they are now.

Anywhere you have an imbalance, there's a potential market. The problem is, if you're not on the demand side, your product has the potential of a short lifespan unless it corrects the imbalance.

Google did this with ads, Uber with rides, AirBnB with rooms, tinder with.. well, you know.

Each of these markets had an unseen demand side which each of the companies exploited. Find an unfilled demand and fill it. It doesn't need to be huge, but if it's in the way of someone already moving there, you greatly increase your chances of being acquired.

First step now, is to figure our what each of your strengths is/are, and then create a list of potential ideas that spark each of you, then choose the one that (a) ignites you both, (b) has a realistic revenue model, and (c) can be built without the need for investor capital.

Make sure you choose something that actually has customers you can get to, not something that has revenue potential when you say "If we can just get 1% of the population..."

Lastly, enjoy the journey.

As a result, nVidia will be put to death in favor of Intel's crappy graphics engine.

If you're the sole founder, and you die. It's over. Nobody else is going to take over with the same energy, passion, and insight you had.

This is why you should be publishing an API and having a "3rd party" writing and publishing your app, so there is no revenue behind it for the douchebags at Apple to screw you out of.

Apple won't care if your app is free and uses a public API, but if there's ANY money in it, they want their 30%, especially if it's recurring revenue.

Memcache as an accelerator for web apps is fantasticalicious, but it's not the best solution.

As a loooooong time memcache user, I've found that Redis is much more reliable when it comes to removing items on schedule, and has a bunch of cool new features as well.

HeyZap didn't build the games that power them, the developers did. HeyZap, in releasing information such as installs, etc., to unauthenticated API calls is saying "This is HEYZAP's data".

It's not. It's the developers data too.

Without that developers game, you'd have NO data, and each player is a customer of the developer once they buy the game. They're not just HeyZap's users, they are paid customers of that developer.

Treat your developers businesses with respect and limit information to the developer and let them decide if they want to release it.

http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot

{ "game": { "checkins_count": 876134, "developer_name": "RUNNERGAMES", "activity_url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot/activity, "android_package": "com.game.BubbleShoot", "tips_and_questions_count": 773, "checkins_url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot/activity..., "description": null, "players_count": 52612, "questions_url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot/activity..., "web_url": "http://www.heyzap.com/game/Kqh-bubble-shoot, "players_url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot/players, "url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot, "tips_url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot/activity..., "thumbnail_url": "http://d2ruqtjkg8og7r.cloudfront.net/mobile_game_icon_com.ga..., "name": "Bubble Shoot", "id": "Kqh-bubble-shoot", "android_price": "Free" } }

AND if I go HERE, I can see ALL the checkins with their locations, again without authentication: http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot/activity

{ "activity": [ { "type": "checkin", "like_count": 0, "message": "", "comment_count": 0, "created_at": 1353111191, "user": { "display_name": "emil", "profile_image_url": "http://www.heyzap.com/legacy/images/users/default_user_photo..., "web_url": "http://www.heyzap.com/profile/emilgousfendi, "url": "http://www.heyzap.com/api/v1/users/emilgousfendi, "username": "emilgousfendi", "id": "emilgousfendi" }, "location": { "truncated_longitude": 106.963, "city": "Bekasi", "truncated_latitude": -6.356, "country": "ID" }, "updated_at": 1353111191, "id": 192146287, "time_ago": "just now", "game": { "android_package": "com.game.BubbleShoot", "web_url": "http://www.heyzap.com/game/Kqh-bubble-shoot, "url": "http://www.heyzap.com/api/v1/games/Kqh-bubble-shoot, "thumbnail_url": "http://d2ruqtjkg8og7r.cloudfront.net/mobile_game_icon_com.ga..., "name": "Bubble Shoot", "android_price": "Free", "id": "Kqh-bubble-shoot" } },

...

I wasn't missing the point. OpenFeint was built on the backs of indie developers, and they sold out and didn't protect the indie developer. Okay, so selling out isn't so bad, but why then make the developers do all the work to get compatibility when THEY were the ones that made you rich?

Except with Twitter and Instagram, I need to authenticate to get the information about WHERE an action occurred, so at least there's a trail.

With your implementation, I can scan all my competitors users with public profiles (at the very least) and see who's buying what.

If this is a transparency play, then say that and make a stink about it. But when Mike gets the crap kicked out of him, also step up and cover his medical bills.

Edit: Okay.. so the location IS truncated, kudos. Why is this an unauthenticated API?

This URL: http://www.heyzap.com/api/v1/users/search?q=mike

Allows me to anonymously see numerous (limited by # of results) users records.

When I choose one from the list and go to this URL: http://www.heyzap.com/api/v1/users/mike_midkiff/activity

I see all of Mike Midkiff's info. All the games he has, WHERE he played (are you f'in kidding me??????), HOW MUCH he paid, and even his unique ID.

hackers, wake up. Bad engineering is bad.

Only the developer whose game Mike bought should be able to request his information, and ONLY relative to that developers game.

Hell. If someone gets mad at him in game, they can use YOUR API to track him down and beat the crap out of him.

Nice.

They can't tell you that their servers will be compromised, and all your users will be open game. They can't promise you that they won't bring in a CEO that just wants to get the company sold, and doesn't care about the developers or their customers.

They can't tell you that when they pivot, all your games will be busted. Not because they're hiding this gem from you.

It's simply because they don't know it.

When you roll your own, you know it's going to survive because YOU are responsible for it.

No BS politics are going to force you down an ridiculous migration path you don't already know about, and since YOU are the CEO, you can sell out and not worry about screwing companies who are dependent on your product or service.

Even IF you choose to use a third party, you owe it to yourself to write your own and mirror that data on to yours so that when, not IF, they go down or out, you can flip a switch and you're back in business within seconds, not days.

The deal with GREE stinks of potential currency manipulation, IMHO, and I wouldn't put my livelihood in their hands for one minute. Again, not because they're bad people - I don't know them from Adam, but because they've already shown that they're willing to allow the customer, we developers, to do ALL the work to satisfy THEIR migration to their API instead of requiring OpenFeint to develop a transparent proxy layer and make it turnkey.

Don't indie developers have enough to do already?

If you think OpenFeint had issues, just try getting your concerns addressed now that (a) GREE is in Japan, (b) time shifted 13 or so hours ahead of the US, and (c) works in YEN and uses at least two levels of currency conversion to compute your revenues.

All those users just lost faith in yet another service, and all these guys are doing is saying "Hey, we failed you as a SAAS vendor, but we made $100 million, so lube up and try GREE because they need to [overcharge you voraciously to] recoup their investment.

You'd think the geniuses in the game industry could put their collective [self acclaimed] intellects together to come up with a platform agnostic approach to these common issues, and open source it for the betterment of the customer.

Oh, yeah... the... customer. Oops.

>>>>>>>>>>> UPDATE <<<<<<<<<<

OOH.. and it gets better... From GREE's agreement, paraphrased:

ARTICLE 5: Virtual Currency; Revenue Sharing

We've created our own currencies, not unlike BitCoin, called J-Coins and G-Coins. We reserve the right to change the ratios to capture more revenue, but right now you should just trust us that we're being honest.

Customers will pay US, not you. We'll tell you how much they spent of that money with you, and then pay you what we think is fair, in our sole discretion.

Oh yeah, to further confuse the customer, you can't call YOUR currency anything like ours, and we get to decide what you call it, and if you don't change it, we don't have to pay you.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Where the f* do I SIGN UP!!!