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.
Great to see that Python3 support for frameworks such as Flask and Django are catching on. I personally feel that the big frameworks should push more when it comes to the adaption of Python3. The only reason I ever still use Python2 is because of frameworks such as Twisted[1] not supporting Python3 yet.
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.
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.
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.
I'm currently working on a libre push notification service (Heavy WIP) and since this post is about API's and Documentation I was wondering if mine is any good.
I honestly feel that in this case we can say that beyond a reasonable doubt this is a state-sponsored attack. This is because of both the target and the fact that traffic is manipulated at the "great" firewall to initiate this attack.
Too bad most of it has been censored. This means that even though the manual has been published a lot of it is useless.
I'm not that familiar with the US FOIA (Freedom Of Information Act). But why is so much of the document censored? Is the US government just allowed to censor whatever they please in documents they have to send due to FOIA requests? Doesn't that defeat the purpose?
What kind of lunatic would pay that kind of money for a dev for a single week