jakeywankenobi

Sounds good, thanks. Cool blog btw, I poked around for a while. Nice work!

Nice. Any interesting use cases for the genome one?

Are there any other interesting articles on good use cases for this kind of centralized data ownership. The syndication concept and the discussion about data rights aside, why else might I want to have all the data I ever create or interact with in aggregate like this? The author has referenced a few really interesting projects they worked on, curious if there are more good ones.

> My point is, people's minds aren't caught up to the scale of data, and I don't think there is a technology solution for it.

I totally agree with the general thrust of this argument. I'd like to hear more about use cases for this kind of personally-owned, aggregated data store. Once this article started talking about searching over, say, notes and highlights from articles and blog posts, I started to see specific use cases that seem totally compelling. However, it's not clear to me how this part of the data ownership conversation matches up with the seemingly more principles-driven data ownership conversation.

Theoretically there's nothing stopping you from building some of these more specific implementations (which the author has done--btw those projects looks really cool).

Hey HN, wanted to share the 3rd iteration of Aircrud. Now you can drag & drop to build pages using a set of flexible components—like charts, tables, forms, and more—and then copy and paste your API details to bring them to life. It's a fast, simple way to build wiki-like tools your teams can use to flip feature flags, manage orders, analyze data—basically anything your APIs can do, you can build a tool for it with Aircrud. Let me know what you think!

Yeah. I mean, at what point does this level of neglect become criminal?

Yeah totally, I think that's an interesting thing to know. I guess my underlying question was: how might this be turned into a product?

Oh, thanks for the tip. I was just trying to have a little fun, but you're right that it's not very descriptive. I'll change it.

Interesting. Have you thought about any practical applications for something like this?

I'm always curious about how things like this would do if an effort was made to market it to the general populace. The makers are all amped about the underlying tech (and rightfully so), but it's a hard thing to really care about outside that niche space. What if you hid all the underlying tech, layered on a good UX, and spoke to the value proposition?