jheising

10 ms·

1.
by jheising 1mo ago
So there are some free sources I found for departure and arrival destinations, but they were wrong more than they were right, so unfortunately the only way to get reliable information is from a paid source. I may offer this at some point as
2.
by jheising 1mo ago
Very interesting! Most likely bad or incorrect altitude or position data from an aircraft transponder.
3.
by jheising 1mo ago
I LOVE the idea of applying Dolbear's Law, that would be such a cool touch.
4.
by jheising 1mo ago
It's meant to be relatively random. The idea is to show you some well known cities and landmarks so that you can get an idea where you are, but then some random curiosities just for the sake of exploring and seeing new things. If you c
5.
by jheising 1mo ago
Thanks for the report, we'll look into it!
6.
by jheising 1mo ago
Great idea!
7.
by jheising 1mo ago
Somewhat. It currently simulates wind speed and direction for the movement of clouds. It also supports the ability to simulate cloud cover percentage (in the advanced options)— the reason it's not on by default is because we want users
8.
by jheising 1mo ago
I will look into this, thanks! In the meantime I'm going to implement a fallback to 2D tiles which has much higher quota limits. Try to stop the bleeding first.
9.
by jheising 1mo ago
Since I'm here, the why: When I was a kid — back when travelling still felt new and exciting — I would see a plane crossing the early evening sky and try to put myself in it. Not to go anywhere in particular. I just wanted to know what
10.
by jheising 1mo ago
Hi all! I'm the creator of Stowaway.live and I really appreciate you posting it here. All this attention has maxed out my Google 3D Tiles quota, so the ground textures in ride-along mode are being throttled. Everything else works — sky
11.
by jheising 11y ago
The Maker Channel Action doesn't support authenticated requests, at least anything beyond something you could send in the URL or body of the message. We do this to prevent people from using it to spoof requests to public authenticated
12.
by jheising 12y ago
Not exactly sure what you mean by long-polling in this context. Do you mean a client making calls to the API at regular timed intervals to check the status? Or do you mean the server making calls to an endpoint URI when an event occurs?
13.
by jheising 12y ago
Hey azdle, thanks for the question and being honest. Do you mind me asking who you work for? Just curious more than anything. To answer your questions about the alert code, yes it runs in a sandbox, but we also parse it and take it through
14.
by jheising 12y ago
Yeah it's something that is browser dependent. I wouldn't call it a bug, but it is an annoyance. It's a decision we had to make in order to keep Freeboards secure for customers who don't want their data to be seen. But i
15.
by jheising 12y ago
Our core focus is read-only at the moment, but yes, command and control has been very much on our mind for a while and I think is going to be a next logical step. Technically you could implement C&C with a plugin right now, but we want
16.
by jheising 12y ago
Yeah it's 100% client side.
17.
by jheising 12y ago
Check the repository again. I just updated the Readme.md to add some more docs on loading and creating plugins. Let me know if this helps. Thanks!
18.
by jheising 12y ago
donatj, I would expect that both of those would work, but I can check into adding this as a feature. A lot of times this is actually an issue with CORS. The API would need to add a CORS header for freeboard.io. Or if the API supports JSONP,
19.
by jheising 13y ago
Will do mate.
20.
by jheising 13y ago
Hah! Never thought about it, but you are so right. HTTP is actually an M2M protocol at heart and is by far the most prevalent on the planet...
21.
by jheising 13y ago
Right now there is nothing to protect because the API is inherently open (on purpose to make it easy). But next week we will be introducing a security token mechanism to be able to "lock" machines. In this case HTTPS will be impor
22.
by jheising 13y ago
Thanks for the feedback! To be clear, the node.js library is just a client-side library, so it should only be technically running on a single machine in most cases. Also, we only use socket.io for real-time pubsub, but you could just as eas
23.
by jheising 13y ago
So let's not a call it a security issue then. Let's call it an "it's too easy to delete" issue. And if that's the case, then that's what we're going for— easy. Remember, if you were truly protecting s
24.
by jheising 13y ago
Yes and if I were a hacker, I could do the same thing with curl. Either way the only person who's likely to do it is someone who is technically savvy.
25.
by jheising 13y ago
Seriously? Look at the HTTP protocol and tell me you really believe that. Their way: DELETE /something HTTP/1.1 My way: GET /delete/something HTTP/1.1 Do you really think one is more secure than the other?
26.
by jheising 13y ago
Yes this is by design to make it easy. Being able to lock things to make them private is an upcoming feature. No promises, but probably will be available this coming week.
27.
by jheising 13y ago
Yeah that's pretty much it. We're not claiming anything earth shattering or new here— just something that is dead simple, and works.
28.
by jheising 13y ago
Correct. Damned be the HTTP specs and REST because they are such a pain in the ass :) I built HAPI precisely because the current standards only work in a world where everyone knows how and enjoys using curl. I think you should be able to pa
29.
by jheising 13y ago
Agreed, in the code-readability sense it's a little on the strange side, but I wouldn't call it completely nonsense either. My thinking behind the design was that developers are a lot easier to deal with than end-users/laypeo
30.
by jheising 13y ago
It might seem like it, but it's actually not that different from a lot of REST APIs I know of. Most REST APIs return a status (in our case "this":"succeeded"), and some sort of wrapper for the actual data (in our ca

More ›