Hacker News Reader

Comment by heinrichhartman | Hacker News Reader

Congrats! This looks like a really nice service. Thanks for making this!

I am not a front-end preson, but I run a static Jekyll blog hosted on GitHub. I don't want to miss the zero maintenance (!) ease of deployment and network-performance of the GitHub CDN, but I have been missing some dynamic features. Most notably:

1. A view counter per page

2. Comments

3. Signup for Newsletter Form

Since the GDPR landed, I have removed my Google Analytics and Disqus plugins. And I am happy with that. No reason to leak PII to third parties, that I can't trust anymore.

Is that a use case you want to be supporting on your platform? Looks like, this should not be hard to build with your SDK.

Best regards, Heinrich

View on HN

Have you looked at https://commento.io/ as a replacement for Disqus?

If I'm understanding correctly, just like u/guu said, each of these features would require sharing data between users of your app. We're currently working on getting data sharing shipped! But for right now, it can only be used for a single user to store their own data.

gotcha! Thx.

If I understand correctly currently the data is per user and not shared.

If you have a todo app, the user can log in and see and modify their todos but there would be no way for them to share their todos.

There is no shared access to a modifiable store which I believe would be necessary for the view counter, comment, and signup use cases.

This is correct for right now, but data sharing is a feature we're currently in the process of wrapping up and getting reviewed by an independent security team. So this will be possible in the near future

Are you thinking of user-to-user sharing (ex: daniel shares his list with justin) or something more global?

To give an example: The indiehackers website uses firebase as its data store. It's a blog/forum, so posts and comments made by individual users can be seen by people who don't have accounts. Is this a use case you plan to support in the future?

If not, the potential use cases are much narrower than firebase. Not necessarily a bad thing but I'm just trying to understand the product.

User-to-user sharing (because data created using Userbase is private)

Edit: technically you could do something hacky like share the database with a user who broadcasts the data somewhere. But I don't think you'd want to use Userbase if you want to store lots of data that anyone would be able to see

Adding on to this, Firebase isn't structured to support end-to-end encryption by default. Our client-server architecture is built and optimized for that intention. I don't think you could build a performant end-to-end encrypted application with Firebase very easily. Userbase fills that role with a super simple SDK

Reply on news.ycombinator.com