概念: Programmatic Access and Control
想法: Metaformat

MetaDrive P&L: -25.7 (≃ -1713 CNY)

MetaDrive is an attempt to design a single interface to all world's resources via a metastandard.
github.com/wefindx/metadrive YAML [编辑] 产品

In fact, any person, who has to work with various systems, needs something like a metadrive to avoid having to learn to work with each of them. Plug-and-play systems need drivers. Metadrive is about creating framework for drivers to make all systems plug-and-play (with all of their data and services). For example, plug-and-play connect your bank, and bank becomes just like a disk on your computer. Every intelligence agency needs something like a metadrive, to be able to automate data collection and actions.

As a person, using metadrive, you will be able to be a "universal peer" that freely interacts with all protocols. In daily life, e.g., write your updates in any editor you like in one place, and have it published in any places (any social media or hardware groups) you like, and have all interactive comments from all of those places without having to manually interact with those interfaces.

As an organization, using metadrive, you will be able to take multiple applications, and automatically collect and merge data about all of them, to create AI insights automatically, without any manual human integration work, and also, execute actions on those systems as a result of AI decisions.

It would make most sense to have streams of revenue from all the future projects, that use the open source of metadrive for their for-profit services, in that way, making this a project with expected returns like that of a patent and technology licensing for the for-profit uses.

Current development of metadrive is at:


维基页面 [编辑] 管理者: Mindey,

可用资金:
97.48 BUSD
+[转移]
最新 净现值@贴现率=0.1: 9.7535 ħ (650.48 CNY)
(别通知) 请,登录

(别通知) 请,登录

(别通知) 请,登录

(别通知) (可选) 请,登录

我认为我们应该将 API 之上的 ORM 视为一种新范式,就像 SQL 之上的 ORM 一样。 :)

我正在为所有系统的客户端库考虑 Wiki。例如,对于 Telegram API:

  • 1.列出可用的包管理器
    1. 找到所有实现 Telegram 客户端库的东西
    1. 记录它们,以便我们了解这些客户端的 I/O 类型。

I think we should think ORM on top of APIs as a new paradigm, just like there was ORM on top of SQL. :)

I'm thinking of Wiki for client libraries of all systems. For example, for Telegram APIs:

    1. List available package managers
    1. Find all that implements client libraries for Telegram
    1. Document them so that we understand I/O types of those clients.
(别通知) 请,登录

视频:[https://wiki.mindey.com/shared/shots/4f9283c29619ede486d994cff-metadrive-user-story.mp4](https://wiki.mindey.com/shared/shots/4f9283c29619ede486d994cff-metadrive-user-story。 mp4)。

(别通知) 请,登录

相关尝试:beepb00p.xyz的[Human Programming Interface](https://beepb00p.xyz/hpi.html)。

Related attempts: Human Programming Interface by beepb00p.xyz.



    : Mindey
    :  -- 
    :  -- 
    

Mindey,
(别通知) 请,登录

语言