ttol

Had to give https://reasoner.com a try on ARC-AGI-2.

Reasoner passed on first try.

“Correct!”

(See screenshot that shows one rated “hard” -- https://www.linkedin.com/posts/waynechang_tried-reasoner-on-...)

Finally, the missing block to building geocities v2!

We actually integrate with PagerDuty and a bunch of other services already (users can submit integrations too) :-)

Existing integrations: http://try.crashlytics.com/integrations/

Submit integrations using: https://github.com/crashlytics/crashlytics-services

[CENSORED] [REDACTED] [CENSORED] :P

Agree. That's an area I personally want to address and am addressing. Oh the stories I have around that!

Yes - no brainer. :-)

Crashlytics is free :-)

Thanks ksar! Wait until you see what we've been working on ;-)

Wayne here. I hear your loud and clear. Working on it.. :-)

This is super interesting. Right now we are limited by communication due to latency from speed of light. With quantum entanglement, does that mean no latency over great distances? Or is there a latency involved, even in quantum entanglement?

Hey Joe, Wayne here with Crashlytics. Our mission is to provide the best-in-class mobile crash reporting tool. We actually do not charge :-) Let me know your thoughts once you've tried it. We power many top apps including Twitter, Vine, OpenTable, Yelp, Path, Square, and many others.

Also, thanks for the feedback on the invite flow -- I will look into that with the team today!

Hi pifflesnort,

Wayne here. We're extremely proud of the work that the team here at Crashlytics has put into our crash reporting solution. There are many flaws in PLCR that we've addressed -- our customers, like Twitter, Vine, Square, Yelp, OpenTable, Hipmunk, Delta, Kayak, and others, enjoy the increased visibility as well as the wider net to catch issues that other solutions cannot.

We look forward to improving our solution even further - stay tuned ;-)

Wayne from Crashlytics here. Don't worry, a shut down is not next :-)

Thanks Leonid! Have you used these in production?

Agree. OP should work on better account receivable practices instead of pretending to be a loan shark.

This won't work in practice. There are laws in place to prevent sky-high compounding interest rates, late fees, etc.

I would suggest that you simply take 50%, or some other large portion of the project, up front. Then, as you near a milestone, ask for another piece of it.

Billing at the end in one large chunk and then charging enormous rates just means you're not de-risking on the on set, and you're screwing a customer relationship.

Also, industry norms are NET 30, and some customers may even operate, and push, on NET 90 terms.

We redirected it to our main site while we resized our blog server. Resize completed and the blog server (and post) is now up! :-)

Whoops - yes, you're right. Our blog server is completely separate and apart from any of our other servers. It originally only had 1GB of ram, and we're in the middle of resizing it to 4GB. Thanks for the Google cached link! :)

Update: And the blog server is now back up and on a much faster machine.

I remember when this problem was solved. Saved a ton of time.

I think cutting all the legacy is a good move -- start over from scratch. They have the wherewithal to round developer support (and also leverage their Xbox relationships), so cutting baggage is a good idea.

This is nifty :-)

Congrats Ariel, Aaron, and Brian! Textbook industry needs disruption.

PLCrashReporter is great. We've built many things on top of PLCR. A sliver of the many things we've built on the SDK side:

  - transparent symbolication so that you get the exact line of code
  - compatibility with ARC in iOS 5
  - we handle both fatal and non-fatal exceptions
  - detect low-memory warnings
  - and much more

We also took the time to make our small SDK compatible with others so mobile devs can just drop us in easily.

Beyond that, there's a whole other world to consider outside the SDK. For example, since we want to make sure devs don't need to ship with debug symbols built in (30-50% increase in app size), we have done all the heavy lifting instead of shifting that to the developer (and then to the user).

In terms of just dumping the logs to an S3 bucket, that may work initially, but once you start getting tons of crash reports, the real problem starts -- how to make sense of it all. We also wanted the filename and the line of code that it crashed on, but this wasn't terribly easy to do. We ran into these issues ourselves and decided to build an elegant solution to this problem.

We're excited about this space and have been deeply involved in it. Great stuff to announce soon that should shed more light!

Thanks, I think! ;-)

Thanks! We really wanted to make sure our users get the best of both worlds - we symbolicate crash reports, provide device insights, and much more, without forcing devs to ship with debug symbols (which ends up bloating their app).

I was never paid by Napster, Inc (although probably should have been ;). Those were fun times. My career was just getting started so it was my pleasure to volunteer my time -- 8 to 10 hours a day. I was responsible for the Napster Ground Zero effort, which I started and managed. I was an administrator there -- not just only a chat moderator volunteer on the Napster service (although I did have the chat moderator access level as well). The Napster Ground Zero service was insanely popular and allowed napster users to have a persistent identity online, beyond just the chat service. I received a written recommendation from a Napster cofounder and created some great relationships, which was great at that early time in my career. I appreciate every moment of that experience. On a side note, it was great to connect with them again in person at the Napster 10-year reunion last year (can you believe it's already been over 10 years now?). Shawn Fanning throws amazing parties.

As for AllAdvantage, I was a security consultant there. This was a paid position. I was involved directly with the company (and have maintained contact with some of the people there over the years, including the CEO). The software I created, first of its kind called MyAdvantage, got their attention. I was asked to be a security consultant for them to hunt down other software and to help protect their Viewbar software. I agreed and helped with the onslaught of the waves of similar software to my original. Sadly, their business model was fundamentally flawed, but that's an entirely different story.

Great times back then. Heady days of the last dot-com boom.

Not really. Many articles discuss that they send the data every 12 hours.

For example, here's one: http://www.eweek.com/c/a/Web-Services-Web-20-and-SOA/Apple-T...

Alex Levinson says that it's illegal to determine the location or movement of a person.

Apple's lead counsel Bruce Sewell says this is not the case as the identifier is randomized, and that Apple does collect anonymous location data from iPhones in an effort to improve its own database of cell tower and WiFi hotspot locations.

See: http://arstechnica.com/apple/news/2010/07/apple-responds-to-...

F-Secure's article on this, http://www.f-secure.com/weblog/archives/00002145.html, shows that the location database is uploaded to Apple twice a day

Jason is the man. He will run through walls and jump over canyons. (HN: he is also #14 on the leaders page: http://news.ycombinator.com/leaders)

Last year I met with Jason to discuss the project. When he described it to me, I immediately understood the vision and his goals and plan to get there. When he passed me the iPad with the demo, I was sold. Within 24 hours, I committed to be the first investor. I wrote a quick blurb here: http://waynechang.com/2011/01/13/proud-to-be-a-part-of-onswi... - Crazy that post was only two months ago.