Structured Internet Client
Like browser, but structured, based on high level protocols?
For all intents and purposes, browser can be thought of as "Unstructured Internet Client", because it can render arbitrary UI interact with arbitrary backends. However, the Internet data is getting increasingly structured. This can be seen in the shift of paradigm from creating custom HTML pages to creating public APIs as the main entry point to what application has to offer.
The idea of structured internet client, is thus a client, that defines protocols for ranges of similar apps.
An example of a structured multi-protocol client, is Trillian, a multi-protocol messenger. However, it is not only chat that has the need for very similar UI. For example, E-mail had same UI, regardless if POP or IMAP protocol was used. Also, there are many other things that are similar, like: shopping, video viewing, forums, etc., that today have hundreds of unique apps, that rely on their APIs, but coherent open-source UIs could be developed to allow the display and interact with such common content.
If a general purpose client for Internet's structured data is created, then everyone's day-to-day work may be simplified.
On reinventing Internet Browser. Multiple projects mentioned. Need to figure out their core ideas, and link.
Explanation: Super-apps are fundamentally integration points of various services provided on the internet over APIs (structured data) from various companies in a unified experience (app).
While browser does the same for unstructured data (browser is an integration point for the web for human access), the structured internet client could be said to be a super-app, because it provides a human access to the web of APIs)
Telegram's client application is open source, and structured. WeChat client application is closed source, and structured.
While Google is going with Chromium and WebAssembly towards the direction of making the browser itself into such a client for both structured (by providing the option of running traditional apps inside browser) AND unstructued data, browser extensions actually compromise security... I think, there is a place for a highly secure open source structured Internet client, like what Telegram client could become.
I agree, and working on such an idea for more than 5 years now. And could explain my ideas. Let us connect.
//そして今5年以上そのようなアイデアに取り組んでいます
本当に？ええ、接続しましょう。 mindey.com/meetでいつでもあなたのために働きますか？
// and working on such an idea for more than 5 years now
Really? Yeah, let's connect. Any times on mindey.com/meet work for you?
XMPPに何が起こったのかを避けたいと思います。XMPPは、プロトコルに古いものを追加して単純に実装することを不可能にする委員会です。簡単ではないからです。
プロトコルをシンプルにすることが目標です。 Cでテキストベースのプロトコルを構築するのに役立つepollserverがあります。
https://github.com/samsquire/epoll-server
We want to avoid what has happened to XMPP - which is a committee which adds any old stuff into the protocol making it impossible to implement simply. Because it's not simple.
Making protocols simple is the goal. I have an epollserver which is useful for building text based protocols in C:
https://github.com/samsquire/epoll-server
非同期IOは、IO要求を並行して行うことができるため、構造化されたインターネットクライアントを非常にスッキリと感じさせる可能性があります。
私が見つけた最も簡単な例は、ライブラリを使用しており、ここにあります
https://github.com/robn/yoctochat/blob/main/yc_uring.c
Asynchronous IO could make a structured internet client feel very snappy because you can make IO requests in parallel.
Simplest example I have found that uses lib uring and is here
https://github.com/robn/yoctochat/blob/main/yc_uring.c