Hacker News new | comments | show | ask | jobs | submit | jamest's comments login

[posting on behalf of my colleague @ Google]

Hi everyone, Google Product Manager for Maps APIs here. We are not revoking Routebuilder’s access to the Maps API. Unfortunately, we mistakenly sent a letter to Routebuilder saying that they were in violation of the Google Maps API terms of service. This was an error. Once the developer contacted us about this issue, we replied apologizing for the misunderstanding and confirming that we would not be revoking his access to the Maps API. (He contacted us on Friday, we replied on Monday, the blog post was published on the weekend.)

We’re really glad he let us know so we could fix the issue and we encourage any developers that have issues in future to reach out to us so we can help. Developers who want to contact the Google Maps APIs team: Stack Overflow and our issue tracker forum (https://code.google.com/p/gmaps-api-issues/) are both monitored by the Google Maps team weekly.

-----


Hahaha. We have been through this with AdSense. Without the negative PR Google would have never replied. This is also a good lesson for the aspiring Play Store Android developers.

-----


Firebase does have offline support for iOS/Android[1]. Web support is coming.

[1] https://www.firebase.com/blog/2015-05-29-announcing-mobile-o...

-----


[Firebase Cofounder] The reason <your_app>.firebaseapp.com sites are free and custom domains are $5/mo with Firebase Hosting is HTTPS-only. Our cost-of-goods-sold includes auto-provisioning the SSL cert for the domain.

Part of our philosophy is providing services that work well, and hopefully better, together. Our realtime database only accepts SSL connections and doing the same with Hosting means when you build on Firebase your whole app is encrypted by default.

We're excited to use Divshot's tech make Firebase Hosting even better going forward.

-----


Firebase has a similar style guide:

https://www.firebase.com/docs/styleguide.html

-----


[Firebase founder] There is a Firebase C# SDK on the way. We've had some other things, that we've been working on for the last year, that are shipping in the next few weeks which have taken priority. After that, we'll be shifting focus to new SDKs (they're a little complicated and take a bit of time to build)

-----


I'm really glad to hear this. I have been loving Firebase for the app I'm making but one of the components has to run in C# and talking to Firebase from the C# app was much more painful than the other Firebase portions of the application.

-----


This would be awesome. Right now I'm experimenting using raw HTTP requests and Newtonsoft.Json as the JSON [de]serializer. I presume that you will make your C# SDK a portable class library so we can use it in iOS and Android apps as well via Xamarin?

-----


"C# SDK" doesn't say much. SilverLight can use C#, WinRT can use C#, .NET can use C#, but that doesn't mean your "C# library" will run everywhere. C# is just the syntax.

-----


You can get a 'prettier' version by removing .json entirely:

https://hacker-news.firebaseio.com/v0/user/tptacek

-----


[Firebase founder here] This is pretty exciting for us, we're glad kogir, dang, kevin and sctb chose to expose HN's data through Firebase. We're seen quite a few startups (and big companies like Nest) do this, since building, maintaining, and documenting a public API often isn't a easy task.

-----


How does this API work with Firebase?

Is HN data already in Firebase (as its primary data store) or is content from HN's DB getting 'mirrored/cloned' on-demand to Firebase for the API?

-----


Mozilla, the corporate backer of Persona, decided to end new feature development on it because of low adoption. Because of this, and very low usage numbers on our end, we decided to remove support.

-----


Kudos to Auth0 for creating this site. The education, awareness and graphical debugger are great. Thank you!

We (Firebase) use JWTs to integrate with an existing app's userbase[1].

[1] https://www.firebase.com/docs/web/guide/simple-login/custom....

-----


Thanks! Glad you had a good experience!

-----

More

Applications are open for YC Summer 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: