Agree, state files can contain sensitive information. We parse the Terraform client side and only send the details to the API that are needed to determine the price, i.e. the instance type, region, etc.
But "When people invest" - This isn't investment behavior. This is speculation and most likely simple addiction to gambling behavior they drive and incent people to do.
The quality and consistency of firmware/functionality/hidden stuff on the various 8266's I have leads me to avoid them. I had a pair that phoned home to some Chinese domain and registered all via HTTP, and a quick Wireshark yielded it phoned home for commands. Not on my network...
You can pick them up cheaper on ebay, as well.
It depends :-)
Some seem to have a fall-back or fail-safe that isn't overwritten. Even with flashing known firmware, the reliability of the little guys was questionable. Random lockups and very touchy to power source.
Disclaimer: I'm just a product/biz guy that codes on the side.
I started using CodeAnywhere earlier this year to manage a small PHP+mysql geospatial email system for an aviation charity I do the tech for...so wanted something cheap (its $120 a year?) and able to teach a non-tech how to go in and make a change (as I don't want them making edits in the github UI).
I was also using my Chromebook a lot while traveling and using shared space, so I needed a decent dev environment without Chrome plugins/jankiness/slowness from a 4gb system.
They have Android and iOS apps that make changes when on the go a touch easier, though code on a Nexus is pretty rough on a plane :-)
So far, pretty good - initially they were making changes to how containers were created and destroyed, causing some changes in the syntax of how a container is defined thus causing mine to be troublesome. However, their support was pretty responsive and got it sorted out.
gomix.com as mentioned here already is pretty new but has been reliable for me so far. It is a fogcreek venture so I imagine it will mature pretty quickly.
I took a stab at this domain (online dev environment) with a service recently, and it's really hard! So congrats on codeanywhere, it's really nice. My qustion is; how does code anywhere handle mobile users? Every syntax highlighting text component I tried utterly failed on mobile slash touch devices.
I'm not terribly keen on providing my actual login to my bank. Ie, adding Betterment asks me for my user/pass Betterment user login (they don't offer 2 factor) - something anyone could then use to login and manage my money there.
I see you're using plaid underneath to connect; so giving some assurance that plaid is handling the data flow and sway will not be storing usernames/passwords would be nice (if that is true).
"Also, how responsible is a civilian pilot for climbing through an instrument approach near a military airfield without radio contact?"
Other than responsible for not seeing a fast moving jet rear-end him, not very responsible. Even if he was under radio control and his head on a swivel, it would have have been near impossible to see the jet coming from behind and left at that speed.
He wasn't "near a military airfield" - he had taken off from a general aviation airport just north of Charleston's International airport (CHS), also shared with military, however FAA ATC and rules prevail in this airspace. There is no "military airfield" difference around CHS.
The F-16 was on a practice approach to CHS, just as anyone could do a practice approach to CHS by requesting to do so from ATC.
One major contributing issue to this was the controller descending the F-16 to such a low altitude so far out (1600' at 34 miles out) [1]. This is well below any slide glope and frankly, as a pilot who flies IFR and no-radio-VFR, I would never expect to see a jet on an approach that low even 15 miles out.
The incident did not occur in the military operation areas (MOA) north of CHS.
My main point is that there are likely multiple factors and a headline titled “Can the ‘Right Stuff’ Become the Wrong Stuff?” with speculation and hand picked comments doesn’t help the investigation or preventing accidents in the future. It does drive traffic and revenue for James Fallows and the Atlantic though.
If you fly GA, I’d recommend you know where nearby airports are (and thirty miles isn’t that far for jets), where instrument approaches are, where MOAs are, where low level routes are, etc. I’d also recommend using flight following. You can say that these things aren’t your responsibility, but I don’t think that’s a good attitude.
Also, I’m not sure how you interpret that the Cesna was rear ended. Reading the NTSB report it sounds like the Cesna was heading southeast (135) and climbing and the F-16 was heading west (265) and turning south (180). Seems closer to head-on or perpendicular with the Cesna climbing into the F-16’s altitude and the F-16 in a belly up turn with no visibility.
Regarding the Tacan, I don’t see any mention that the F-16 was below altitude or off course. So just because you wouldn’t expect a plane there, doesn’t mean that one won’t be there. Again, maybe this is a bad Tacan with nearby civilian airfields and should be axed, but it doesn’t seem any rules were broken.
We don’t know the results of the investigation, yet all the blame is being put on the F-16 driver. It sounds like small failures from all involved resulted in a tragic outcome. There may be lessons learned from this incident that can help prevent another in the future, but placing blame without the facts and pointing fingers in the media isn’t how we figure them out.
State files should be considered secret....