Problemos: Programmatic Access and Control.
Sprendimai: Metaformat.

MetaDrive P&L: -25.7 (≃ -268 EUR)

MetaDrive is an attempt to design a single interface to all world's resources via a metastandard. YAML [taisyti] Produktai

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:

Viki puslapis [taisyti] tvarkomas: Mindey,

101.09 BUSD
Naujausias NPV@diskonto norma=0.1: 9.7535 ħ (101.90 EUR)
(nesiųsti pranešimų) Prašome prisijungti.

(nesiųsti pranešimų) Prašome prisijungti.

(nesiųsti pranešimų) Prašome prisijungti.

(nesiųsti pranešimų) (nebūtinas) Prašome prisijungti.

Susiję bandymai: „Žmogaus programavimo sąsaja“ (, pateikė

Related attempts: Human Programming Interface by

    : Mindey
    :  -- 
    :  -- 

(nesiųsti pranešimų) Prašome prisijungti.

Vaizdo įrašas: [>( mp4).

(nesiųsti pranešimų) Prašome prisijungti.

Manau, kad ORM be API turėtume galvoti kaip apie naują paradigmą, kaip ir ORM ant SQL. :)

Aš galvoju apie Wiki visų sistemų klientų bibliotekoms. Pavyzdžiui, „Telegram“ API:

    1. Pateikite galimų paketų tvarkytuvų sąrašą
    1. Raskite visas, kurios įdiegia „Telegram“ klientų bibliotekas
    1. Dokumentuokite juos, kad suprastume tų klientų I/O tipus.

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.
(nesiųsti pranešimų) Prašome prisijungti.