Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have been trying to come off of google and cloud by building — quite slowly — my own nas server which has 2 nodes in two geographic regions where I am building certain services like cloud storage and backup, webhosting etc. But I think there are a few key things that need to be community driven to really get rid of this duoply.

0. A privacy first approach would be something like this:

`You+App --Read/Write-> f_private(your_data) <--Write only- 3p` and App cannot communicate your data to 3p or google/apple.

Think of Yelp/Google Maps but with no _read_ permissions on location, functions can be run in a private middleware e.g. what's near an anonymous location or ads based on anonymous data. You can wipe your data from one button click and start again for EVERYTHING, no data is ever stored on a 3p server. Bonus: No more stupid horrible permission fiascos for app development that are just plain creepy.

1. An opensource data effort that can support (0) with critical infra e.g. precise positioning, anonymous or privacy preserving functions that don't reveal their data or processes to 3p.

Here is my favourite open source effort: Precise Location Positioning. A high recall, opensource, 3D building and sattelite-shadow Data-Infra effort[3]. This world class dataset on shadows and sattelites are a must. Most geo-location positioning tied to Radio signals is just a bandaid and fraught with privacy issues — thought there are heroic privacy first efforts in this direction[1][2] which though amazing will be playing catch-up with google already deploying [3].

[1]https://beacondb.net/

[2] https://github.com/wiglenet/m8b

[3] https://insidegnss.com/end-game-for-urban-gnss-googles-use-o...





I don't understand your syntax:

    `You+App --Read/Write-> f_private(your_data) <--Write only- 3p`
Does this mean a server where third parties can send code to run on your data, but cannot respond to them?

They mean 3rd parties have wo permission instead of rwo to your data store



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: