💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › t7g9vn$ogt$1@dont-email.me… captured on 2024-05-10 at 11:15:52. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-06-11)
-=-=-=-=-=-=-
From: D Finnigan <dog_cow@macgui.com>
Subject: Re: Gemini is no social network
Date: Sat, 4 Jun 2022 13:57:57 -0500
Message-ID: <t7g9vn$ogt$1@dont-email.me>
On 6/3/22 3:35 PM, news@zzo38computer.org.invalid wrote:
You can use different protocols and file formats for different purposes.
One protocol or file format will not help everything. (The same should be
true of character encodings; Unicode is not suitable for everything, nor
can everything always be converted to/from Unicode effectively. TRON also
is not always suitable, but has some advantages and disadvantages over
Unicode for some purposes.)
Possibly, implementations could be made where different protocols and file
formats may be loaded as .so files, and may be written in C. Adding new
character encoding conversions could also be implemented similarly; it may
use a font with that encoding if it exists otherwise convert it and specify
which settings to use if necessary.
For example, an implementation could be made with:
Protocols:
* HTTP and HTTPS
* Gemini
* Gopher
* NNTP
* Local files
* Inline data ("data:" URI scheme)
File formats:
* Plain text
* Gemini
* TRON application databus format
* HTML (limited; e.g. based on Lynx or Links)
* Markdown
* CSV
* SQLite
* VM3 application file (including VM3 markup format)
* Pictures: PNG, JPEG, XBM, XPM, farbfeld
* ZIP archive (including Gempub)
Different implementations may vary in which protocols and file formats, and
which features of them, and may allow a common C interface to add other
formats and change their capabilities. The core system may also then be
modified independently to change the user interface and features which are
separate from the protocols and file formats.
We might also ahve different ideas than the above, too. All of the above is
just my current ideas, and we can have improvement in future, too.
You just re-created Tim B-L's World Wide Web project from 1990. This was
exactly one of his goals: to have just one application, the browser,
which can access many different information sources and databases
through a series of hyperlinks. The browser would access resources
through many protocols, not just HTTP.
LibWWW, which powered Marc Andreesen's Mosaic browser, had built-in
support for HTTP, FTP, Gopher, Wais, NNTP, and other protocols.
Parent:
Start of thread:
Gemini is no social network (by David <david@arch.invalid> on Thu, 18 Nov 2021 22:40:59 +0100)