BetaMechazawa

> This pays for at most a week of work

What kind of lunatic would pay that kind of money for a dev for a single week

timeout after 10 seconds "fingerprint can't be read, please enter password"

This obsession with making every single website a hugbox these days is moronic. The word retard/retarded is seldom associated with actual retardation instead it's just a synonym for moron.

Even if you dissagree with that you should still be able to see that even if we did s/retard/moron/ or replaced it with git, idiot etc it would still violate the TOS.

Most of the time cameras are present.

What would you classify as "by hand" and "automated tools"? Because commands like pip install -r {file} could be seen as both in my eyes.

This looks pretty cool. Although I do not understand why I would have to sign up on the website. The demo makes it look like it's a minimal-config command line tool. Instead the website makes it look like it's a service and there is no clear indication who stores my creditcard info etc. on the front page. This is explained in the FAQ though. A quick notice about stripe processing payments on the front page would be nice.

I guess I'm missing the point. Why not use "Welcome %s to %s" % (who, place)

Username/password to log in? Or is this a real service that put up this site just for today and requires an actual account?

The fact that a company needs their own gTLD is silly. Sites like google have a perfectly good domain. Why use iphone.apple if apple can already do iphone.apple.com or apple.com/iphone? At the end of the day the consumer will not start guessing what domain he/she has to use to get what they want. The average consumer uses a search engine and types in "apple iphone". They don't care about iphone.apple they just want to go to the product page.

Is it me or does everyone and their mother have a gTLD these days? I would not take any company that uses a gTLD serious at all.

Thanks a ton! I've always been annoyed by the fact that Web API documentations never had a "try-this-request" feature. I'll get right to expanding the documentation when I get home like I said in the other comments. The request in progress indicator should be pretty easy to add. Totally forgot about it. I disabled the websockets example because It's currently undergoing a complete rewrite.

The API documentation is talking to the live version of the application. The pre-filled variables can be used for quick testing but this also means that when you make the default user (UUID) listen to the default service it will tell you that it's already doing that. Changing the UUID should be sufficient to give it a non-error response for that API call.

I'll add some documentation about what endpoints do and what kind of "flow" an application needs to interact with the API when I get home from work. I'll also finish my quick start guide while I'm at it then.

I've written a draft for a quick start guide using python/javascript (code with comments). I've been withholding publishing it because it's not fully done yet and message queues and the android app (only thing to do is the Matrial UI) are my #1 priority at the moment. One of the main ideas behind the service is that there is no authentication. You just generate a persistent UUID and use that.