| Deutsch English Français Italiano |
|
<1737333707.bystand@zzo38computer.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: news@zzo38computer.org.invalid Newsgroups: comp.infosystems,comp.misc Subject: Re: web Date: Mon, 20 Jan 2025 11:23:24 -0800 Organization: A noiseless patient Spider Lines: 35 Message-ID: <1737333707.bystand@zzo38computer.org> References: <67447ce1$0$22$882e4bbb@reader.netnews.com> <vi3ecs$35u53$1@dont-email.me> <6c4ae24b-7bb8-7d84-8f74-1f5fc14c0ec0@example.net> <87ed2yjkl8.fsf@tilde.institute> <55db8483-58f0-c3dc-de0b-7f44881fa180@example.net> <87jzcp4pzy.fsf@enoch.nodomain.nowhere> <viorqr$mnrh$1@dont-email.me> <viotl0$n3vg$1@dont-email.me> <slrnvl0pq8.1ddsk.candycanearter07@candydeb.host.invalid> <vir0m3$17csf$3@dont-email.me> <6754c3a1@news.ausics.net> <vj49do$3r1ov$1@dont-email.me> <vm1hk3$1etjc$1@dont-email.me> <6Qspx-PwipMTzeeG@violet.siamics.net> <678975ab@news.ausics.net> <jWv0GNpJelv3n7gK@violet.siamics.net> <vmj39r$29je9$1@dont-email.me> <87cygivmy3.fsf@tilde.institute> MIME-Version: 1.0 Injection-Date: Mon, 20 Jan 2025 20:17:02 +0100 (CET) Injection-Info: dont-email.me; posting-host="c707aa263e1f472cff1b3dd9d7c33400"; logging-data="3550738"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Ny5ASs28pKOOo3t7xrFYh" User-Agent: bystand/1.3.0pre1 Cancel-Lock: sha1:CLbhG0CxO6ajgXVz/8+/EpWWdlo= Bytes: 3151 yeti <yeti@tilde.institute> wrote: > When browsers appeared, we thought of the web as what was accessible > by them. FTP, HTTP and Gopher were among this in the early days. Many browsers can also display local files (which is not internet), and many newer ones can display PDF files (whether or not they are accessed by the internet), too, though. > Today's big$$$-browsers converge to single protocol network file viewers > and unluckily the smallweb browsers do too. Some of the small web browsers do support multiple protocols and multiple file formats. Unfortunately the major web browsers do not support such things very well even if you add extensions, though; and they have many other problems too other than just this, anyways. > Let's prefer multi protocol browsers and return to all goof stuff being > just a click away from each. > > That was what the web was meant to be and we should make it exactly that > again. > > First step: Prefer writing plugins for existing browsers over creating > more single protocol file viewers. I think that it should be done, although you can still make up new browsers that may support such plugins too. I also think that the protocols and the file formats should be handled separately, so there will be one plugin for Gemini protocol and one plugin for Gemini file format (although they will probably be a part of the same package, since they are used together), and one plugin for Spartan protocol (which also uses Gemini file format so you do not need a separate plugin for Spartan file format), etc. -- Don't laugh at the moon when it is day time in France.