告诉HN：我正在构建一个基于标签/文件的通用个人信息管理器。
由于我在管理整个数字信息宇宙时遇到了很多麻烦，我决定解决这个问题，不仅为我自己，也可能为其他人提供帮助。以下是我对我产品的一些想法：
- 管理个人（也可能是商业）信息/内容的整个范围：文档、媒体、消息（电子邮件、即时消息等）、联系人、书签、日历等。
- 基于标签，这样在放置和查找内容时问题会更容易解决。可以想象一组平面文件夹，存储在一个或多个设备中，文件附带标签。然而，这里会对现有的基于标签的系统进行一些改进。由于人们发现浏览文件比搜索更自然，因此将动态生成虚拟文件夹以提供引导式导航。此外，整个文件夹也可以视为一个原子对象进行标记和管理，这对于存储库和项目非常有用。同时，将使用启发式方法（可能还有人工智能）在文件导入工具时自动标记文件，大大减少首次添加标签的繁琐。
- 基于文件，这样所有信息最终都以单独的文件形式物理存储。这使得在物理层面上更容易管理信息：移动、备份、导出/导入、搜索、导航等，而不受我们现在所拥有的那些不透明信息孤岛的限制。因此，除了文档外，每封电子邮件/即时消息、联系人、计划任务/事件、书签等最终都会作为文件存储，解锁与文件相关的所有操作。
- 提供一个基于本地代理的本地网页用户界面，这样实际的文件内容通常不需要在网络上移动，保持本地化，并且该工具也易于跨平台使用，无论平台如何，用户界面保持一致。
- 还提供一个云网页用户界面，通过本地代理与内容设备进行通信，这样存储在多个设备上的内容可以在一个中心位置进行管理，即使没有直接访问这些设备的权限，也可以提供团队/组织功能。然而，文件内容仍然保持本地，除非被共享。
- 提供将数据作为文件从各种应用和服务的数据孤岛中导出，并备份为文件到云存储服务的工具。
我的愿景是，无论我使用什么设备、应用或服务，我都能掌控自己的数据，确保数据始终可用且不会丢失，并且我可以轻松地浏览和搜索所有数据，找到我想要的内容，无论它多么分散和庞大。
我欢迎您的想法。什么能让这个产品对您有效？您更倾向于使用云用户界面还是本地用户界面？我需要注意哪些技术或市场上的陷阱？
以下是我在个人信息管理方面对当前技术的一些问题，这促使我致力于寻找解决方案：
- 我们的数据过于依赖于设备和供应商的孤岛。无法轻松地在Apple/Google/WhatsApp等账户之间移动我的信息。也无法轻松合并和去重。每当我必须更换手机时，我几乎总是会以某种方式丢失数据。
- 在许多服务上很难拥有自己的数据：Discord、Slack等。无法轻松导出、搜索。
- 很难全面了解和管理所有数据资产，并以一致的方式查询它们。
- 文件作为信息存储和管理的单元非常符合人体工程学；我们不应允许供应商为了自身利益而埋没这一概念。
查看原文
Since I had so much trouble managing my entire digital information universe [1], I decided to scratch my itch and solve it for myself and maybe others as well. Here are my ideas about my product:<p>- Manages the entire range of personal (and maybe business) information/content: Documents, Media, Messages (email, instant, etc.), Contacts, Bookmarks, Calendar, etc.<p>- Tag based, so that the question of where to put and find content is quite a bit easier to answer. Think of a set of flat folders, on one or more devices, within which the files are stored with tags attached. However, there will be some improvements on the usual implementation of tag-based systems out in the wild. Since people find navigating/browsing files more natural than searching, virtual folders will be dynamically generated to provide guided navigation. Also, entire folders can also be treated as atomic and tagged/managed as one object, useful for repositories and projects. And, heuristics (and maybe AI) will be used to automatically tag files when they are imported into the tool, greatly reducing the tedium of adding tags the first time.<p>- Is file based, so that all information is ultimately physically stored as individual files. This allows information to be more easily managed on a physical level: moved around, backed up, exported/imported, searched, navigated, etc. without the restrictions imposed by the opaque islands of information we have now. So in addition to docs, each email/instant message, contact, scheduled task/event, bookmark, etc. would ultimately be stored as a file, unlocking all the things you can do with files.<p>- Has a local web-based UI launched from a local agent, so actual file content does not usually need to move across the network and stays local, and the tool is also easily multi-platform, with consistent UI irrespective of platform.<p>- Provides a cloud web UI as well, that communicates with content devices through the local agent, so that content stored across multiple devices can be managed in one central location, even without direct access to those devices, team/org features can be provided. However, file content still stays local, except when shared.<p>- Provides tools for exporting data as file from the data islands of various apps and service, and backing up as files to cloud storage services.<p>My vision is a situation where I am in charge of my own data irrespective of whatever device, app, or service I use, can ensure that it is always available and will not be lost, and that I can easily navigate and search through it all to find whatever I want, no matter how scattered and massive it is.<p>I welcome your thoughts. What would make this work for you? Would you mostly prefer a cloud UI or a local UI? Are there any technical or market gotchas I should be aware of?<p>[1] Here are some of my issues with personal information management affordances of current tech, which is driving me to work on a solution:<p>- Our data is too bound to device and vendor islands. Can't easily move my information across Apple/Google/Whatsapp, etc accounts. Can't easily merge and de-duplicate either. I almost always somehow lose data whenever I have to move to a new phone, etc.<p>- Hard to own your data on many services: Discord, Slack, etc. Can't easily export, search<p>- Hard to have a 360 overview and handle on all your data assets and query them in consistent manner<p>- Files as a unit of information storage and management is very ergonomic; we shouldn't allow that concept to be buried by vendors for their own gain.