問題: Programmatic Access and Control
解決: Metaformat

MetaDrive P&L: -25.7 (≃ -1903 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,

可用資金:
104.35 BUSD
+[轉移]
最新 淨現值@貼現率=0.1: 9.7535 ħ (722.78 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,
(別通知) 請,登錄

語言