Made me think, is there an opportunity to build a management layer for this? Handle subscribing and cancelling automatically when you want to watch certain things? Would probably be blocked pretty fast but amusing to think about.
Data lakes promised schema-on-read flexibility but became swamps. The industry responded by turning them into databases again, defeating the original purpose. We built Matterbeam differently: immutable storage with inferred intermediate schemas that translate rapidly into any structure you need. When materializations aren't right, replay them. The original vision, actually operationalized.
We gave our first employees restricted stock agreements instead of ISO options, with the exact same legal terms and vesting schedule I got as founder. 2-6% equity grants, six-year vesting, hiring bonuses to cover exercise costs and taxes. Values have to cost something, or they're just words on a website.
This is a little triggering :) Reminds me of all the promise back in 2005 when I built my first startup Grazr.
It was:
- a widget that was a mini RSS reader that let visitors to your site read the RSS feeds you subscribed to on your site
- a way to share your collection of RSS feeds dynamically
- a way to copy / remix those collections
- a way to subscribe to those lists dynamically (if they had a dynamic blogroll or whatever)
- a processing and filtering engine to allow merging collections of feeds together into a single stream
- Javascript on the server (in 2005 :) ) run using embedded script tags in the OPML / XML blogrolls to create even more dynamic blogs
The net effect was you could make your own news feeds / timelines and use code to control how they were filtered / combined / etc... It was crazy powerful (for 2005) and I still miss it _today_ since it had the dynamism of the news feed, some of the social aspect, and total control since there was no algorithm other than your and the people's who's list you subscribed to curation and any code you ran against it.