enbarca

10 ms·

1. 1.▲
   by enbarca 2mo ago

   I ran into the same issue when building ProForta.com. My solution was to build a companion app that pulls data (including Garmin) via Health Connect. Right now, it seems that every hardware platform from Oura to Garmin is trying to build th
2. 2.▲
   by enbarca 2mo ago

   I purchased my Spark back in March before the RAM price increase. My use case is local self-sovereign AI in Healthcare ( https://hcvc.net ), so I haven't done any gaming. Its been a great driver for Hermes Agent, serving loca
3. 3.▲
   by enbarca 2mo ago

   Very cool PoC for self-sovereign AI! Federated learning across private data resident on user's phone makes sense, but still begs the question of how the user gets access and controls access to their genomic data in a private way. From
4. 4.▲
   by enbarca 2mo ago

   I'm building ProForta.com, a prototype app for a self-sovereign AI architecture where you gain control over your health data wherever it resides, the AIs go to your data to gather insights, and raw data custody remains where it was cre
5. 5.▲
   by enbarca 2mo ago

   On-device isn't only cheaper/faster - for health data it's the whole point! The self-sovereign community desperately needs an affordable AI appliance and Apple is still the most likely candidate to deliver on the privacy prom
6. 6.▲
   by enbarca 2mo ago

   I'm looking at adopting a mesh network architecture for self-sovereign inference across longitudinal health records.
7. 7.▲
   by enbarca 2mo ago

   I got myself a NVIDIA DGX Spark to build on unified-memory hardware at home. Now running a health-AI node for all my longitudinal health data - insights are generated on the box so that raw data never leaks.
8. 8.▲
   by enbarca 2mo ago

   the failure wasn’t the science - it was the custody model (your DNA sequence became someone else’s asset). This problem is not limited to 23andMe and the fix is a programatic custody model for health data where the data never leaves your co