Internet Browser


All ports, all protocols Internet browser. Open ports and support protocols to direct browsing of databases, and other internet resources, make web browsers support accessing them directly and nicely.

YAML Idėja

What people currently think of a browser, is a "Web browser," that works on http:// and https:// and primarily 80/443, that are on top of TCP-IP. The idea of "Internet browser" is that any record in any system could have a "url" to any other record in any other system may be useful in many situations, including the creation of semantic web.

Given a good popular data browser, many would probably care to open their databases for public access with default database ports, like 5432, or 27017, for data consumption, and so, we could start using hyperlinks like:


The database programming languages like (PL/SQL, PSL, etc.) would come back to relevance, allowing the flexibility to define the added business logic and functionality, which these days usually is provided by building an API on to of databases.

Today, while most of the web pages on ports 80/443 are open to public, traditionally, most records in databases are behind an authentication, and thus, people are not inclined to make such links (they are inclined to scrape the web rather than properly use databases).

Given an existence and wide knowledge of a good data browser (with ease of use and powerful analytics capabilities on local computers), it is likely to expect that people would care to make proper public access to them, and create a web of data.

Imagine, browsing postgresql://, rdf://, or ethereum:// or rest:// endpoints, or graphql:// endpoints, or gopher://, or ftp:// endpoints, or anything else just as easily as we browse http://, with nice out-of-the-box UI, right inside the browsers.

Since protocols are tightly coupled with software, one path to achieve this is through WebAssembly making traditional software become runnable in browser. Another, is through building clients to support browsing resources all of those protocols, as a "browser" plugin.

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

Noriu bendrosios paskirties duomenų redaktoriaus.

I want a general purpose data editor.

[chronologinė], taip pat ir aš. Tarp bendriausių vartotojo sąsajų, kurias mačiau iki šiol, yra [dynalist] (, skirta nestruktūruotiems duomenims, ir [aiški] (, skirta struktūrizuotiems duomenims (lentelių lentelė). , į reliacinę duomenų bazę panašūs duomenys. Tačiau, manau, nė vienas iš jų nėra pakankamai geras sudėtingesnėms hipergrafijoms.

Tai gali būti kažkas panašaus į chromo maitinimo režimo pratęsimą :)

[chronological], me as well. Among the most generic UIs that I've seen so far, are that of dynalist for unstructured data, and airtable for structured (tabular), relational-database-like data. However, neither of them are good enough for complex hypergraphs, I suppose.

It may be something like a power-mode extension for chromium :)

Btw. Darant prielaidą, kad kiekvieną protokolą apibrėžia pati programa, o protokolai yra tiesiog tam tikrų įprastų programų modeliai (think, aMule ir ʻed2k: // , Telegram ir tg: // `ir kt.), Ir atsižvelgiant į bendrą naršyklės, veikiančios „WebAssembly“, tendenciją, kuri leis paleisti bet kokias programas žiniatinklio naršyklėje, šios programos natūraliai gali būti palaikomos naršyklės languose.

Tai gerai, bet tai reiškia, kad naršyklė apskritai tampa sunkesnė, ir aš nesu tikras, ar to norime. Kitas būdas yra kurti klientus, kad šie naršyklės ištekliai palaikytų visus tuos protokolus kaip „naršyklės“ papildinys.

Btw., assuming that each protocol is defined by the application itself, and protocols are simply the patterns of certain common applications (think, aMule and ed2k://, Telegram and tg://, etc.), and considering the general trend of browser running WebAssembly, that will allow to run any applications on web browser, those applications could naturally become supported in browser windows.

This is ok, but that means making browser more heavy as a client in general, and I'm not sure if this is what we want. Another, is through building clients to support browsing resources all of those protocols, as a "browser" plugin.