1,284 karma · joined February 7, 2008
> The workloads commonly executed on Async are those that do not require blocking an active user’s experience with a product and can be performed anywhere from a few seconds to several hours after a user’s action.
I understand where the OP is coming from. You over estimate what people think of you and your choices.
In the end I believe you are correct, most people just don’t care about your choices.
Also old pickup trucks rock. =)
They really do not do a good job letting you know when features go live.
At first blush Pi.ai seems like a “better” conversationalist.
I’m surprised SMS verification is this ineffective at testing for “human-ness”.
You said the cost is about $2 an episode, is that mostly for the summarization or audio generation?
Camping in the Sierras is awesome and as a pilot flying in California is a dream. Mission is gritty but there is great food around. It seems to have stabilized.
The kind of stuff I get to work at at Apple is insanely cool and commuting 280 is great.
Still have a good friend group; albeit a bit smaller since folks have moved away.
> Once upon a time there was porcupine. Every day, she baked a loaf of bread. One day the loaf disappeared. Because of that, she had too much butter. Because of that, things got slippery. Until finally she opened the first ever butter theme park.
It seems like the LLM did exactly what the author wanted
It’s also a huge amount fun and let’s you do things that would be unsafe in IRL.
My perception in sense of safety and workload reduction is about the same for aviation vs automative.
I’m a instrument rated pilot that mostly flys for fun on the weekend.
The big danger is folks disconnect from their duty to actively monitor the systems.
I would never play an iPhone game with either system.
Fewer things to hit in the sky but you can never be complacent.
Imagine playing an iPhone game while PIC and accidentally flying into the clouds? The CFIT stats are terrifying.
> Almost every study on human behavior contradicts this. When you have no load, your monitoring and responsiveness gets poorer, not better. (Now, you can certainly go to the other extreme and get overloaded, with the same effect)
With both a plane and a car you still have some load; you are supposed to be monitoring the performance of the systems.
I perceive myself to be safer when I have autopilot enabled on a Cirrus. My thinking goes from having to manipulate the controls to monitoring the performance of the aircraft.
I could be derelict in my duties at ignore the plane and play a game on my iPhone.
I perceive that experience to be very similar to when I engage Autopilot on my Tesla.
I go from having to manipulate the control to monitoring the performance of the car. With over 110k miles on my Tesla I really do feel with autopilot.
> Elon Musk’s SpaceX simulated a successful emergency landing on Sunday in a dramatic test of a crucial abort system on an unmanned astronaut capsule, a big step its mission to fly NASA astronauts for the first time as soon as this spring.
https://www.reuters.com/article/us-space-exploration-spacex/...
https://www.google.com/maps/timeline?pb
I’m getting the following error:
“Location Services permission is not set to always. Timeline cannot function properly if you don’t allow Google Maps access to your location while in background. [Skip][Turn On]”
Seems like I should be able to see what historical location data they have without enabling background location.
Disclaimer: I work for Apple
https://www.pge.com/tariffs/tm2/pdf/ELEC_SCHEDS_EV.pdf
Does the utility that serves your father have a similar EV plan?
The trend on these Telsa / EV blogs has been to take Tesla's logs as gospel and discount human observation.
There have been other reports of users claiming autopilot being engaged when it was not and reports of not noticing that summon was enabled even though one can't really miss that (that has subsequently been redesigned).
Human factors for these systems is incredibly challenging since such a wide audience of users useses them.
is a quoted directly from the article. It is also the title of the story.
http://electrek.co/2016/07/06/tesla-model-x-rollover-acciden...
It was incredibly challenging for us to monetize the service and our user numbers where an order of magnitude off of where things would have been intesting for some investors.
1. Two-factor
We don't offer two factor but is something we are investigating. This is mitigated somewhat by the fact that a lot of our users use Google login.
2. SSL / TLS
SSL shouldn't be a paid feature. It's been included in our product for free since we launched.
We try and use SSL everywhere. All page from catch.com are only available via SSL. e.g. login, landing page, marketing, blog, etc.
There are a few exceptions like our Knowledge Base which is powered by Assitly / Desk:
3. Encryption
We don't offer note level encryption. We'd love to get some feedback on a straightforward way to do key management.
4. HSTS
We've been using HSTS for at least a year now. It was an easy decision for us since all content from catch.com is only available via SSL.
Security is hard and hopefully these breaches will raise the bar for everybody.
If anybody has any questions feel free to email me at a@catch.com
The issue we've seen is that people build an iOS app and then port it over to Android.
We designed Catch 5.0 apps for Android and iPhone in parallel. This let us keep consistency between the platforms when it made sense, but also let us tweak the design early on so it could take advantage things unique to the platform, e.g. Action Bar on Android.
The team is incredibly proud of this release, and it is nice to see folks taking notice. Both Google and Apple have also featured this release, everybody is beaming here. =)
We have done billions of ops with Mongo and have never lost any data.
Context is the article which made is seem like even 220GB is an ok amount, still can fit in memory.