MetaDrive P&L: -25.7 (≃ -227 USD)
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:
- ⬜️の会議を開催する -コスティア -サミュエル --beepb00p -ミンディ
- ⬜️重要なのは、Webリソース用のRestAPI / GraphQLAPIを生成するメタドライブを作成することです(それらをマウントすると、他のパッケージで一般化できます) -既存のライブラリとクローラーの使用をサポートする必要があります。
- ⬜️ Organize meeting of
- Kostya
- Samuel
- beepb00p
- Mindey
- ⬜️ The key is to create metadrive that generates RestAPI/GraphQLAPI for web resources (mounting them can generalized by other packages then)
- it should support using the existing libraries and crawlers.
Just for the demo, actually went in more work than that, but let's say it's a number.
関連する試み:beepb00p.xyzによる[Human Programming Interface](https://beepb00p.xyz/hpi.html)。
Related attempts: Human Programming Interface by beepb00p.xyz.
ビデオ:[https://wiki.mindey.com/shared/shots/4f9283c29619ede486d994cff-metadrive-user-story.mp4](https://wiki.mindey.com/shared/shots/4f9283c29619ede486d994cff-metadrive-user-story。 mp4)。
Video: https://wiki.mindey.com/shared/shots/4f9283c29619ede486d994cff-metadrive-user-story.mp4.
SQLの上にORMがあったように、APIの上にあるORMを新しいパラダイムとして考える必要があると思います。 :)
私はすべてのシステムのクライアントライブラリ用のWikiを考えています。たとえば、TelegramAPIの場合:
-1。利用可能なパッケージマネージャーを一覧表示します --2。Telegramのクライアントライブラリを実装するものをすべて検索します -3。それらのクライアントの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: