The plain-text internet is coming
protocol.com
The plain-text internet is coming
1–10 of 35 posts
Re: The plain-text internet is coming
#2noscript/basic (x)html can do wonders. But it is so stable in time, planned obsolescence is very, very hard to do: web scammers (or brain-washed web devs) don't like that with their absurdely huge and grotesquely complex google(blink/geeko) and apple(webkit) based browsers.
Re: The plain-text internet is coming
#3I think more things like the Gemini Protocol will continue to be popular.
An internet that is deliberately severely bandwidth limited could make navigating between sites much faster. For example, a limit of 100K or even 1K per page for content, or something similar for web assembly applications/modules.
Possibly combine that with entirely ditching JavaScript for web assembly and entirely separating applications from content handled with markdown.
Also going 100% content-centric could be a revolution. Things like IPFS, or maybe build a sandboxed UDP or libp2p API into web assembly.
Re: The plain-text internet is coming
#4noscript/basic (x)html can do wonders. But it is so stable in time, planned obsolescence is very, very hard to do: web scammers (or brain-washed web devs) don't like that with their absurdely huge and grotesquely complex google(blink/geeko) and apple(webkit) based browsers.
I suggest a new meme: byoCSS (i.e. assuming classless html)
Perhaps there is already support for this via extensions.
I wonder if some flag (among a set?) could be placed within a basic classless html (and no js) page to call forth one or a number of user/user-agent controlled stylings.
Re: The plain-text internet is coming
#5noscript/basic (x)html can do wonders. But it is so stable in time, planned obsolescence is very, very hard to do: web scammers (or brain-washed web devs) don't like that with their absurdely huge and grotesquely complex google(blink/geeko) and apple(webkit) based browsers.
I suggest a new meme: byoCSS (i.e. assuming classless html) Perhaps there is already support for this via extensions. I wonder if some flag (among a set?) could be placed within a basic classless html (and no js) page to call forth one or a number of user/user-agent controlled stylings.
This is how I imagine browser support for markdown could work. Plain text comes in over the wire and is rendered to taste.
Re: The plain-text internet is coming
#6I think more things like the Gemini Protocol will continue to be popular. An internet that is deliberately severely bandwidth limited could make navigating between sites much faster. For example, a limit of 100K or even 1K per page for content, or something similar for web assembly applications/modules. Possibly combine that with entirely ditching JavaScript for web assembly and entirely separating applications from…
We called this the WWW back in the day using Gopher and then web browsers with HTML ;)
Tags introduced in HTML 1.0: , , Base Address, , , , ,
, ..., , ..., (with and ), (with ), and .
Gemtext 1.0(?) markup: headlines (three levels), list items, pre-formatted text, quotes, links.
Not sure what you mean with 100% content-centric. No ads? Brutalist Websites?
Re: The plain-text internet is coming
#7Earlier quoted context omitted.
I suggest a new meme: byoCSS (i.e. assuming classless html) Perhaps there is already support for this via extensions. I wonder if some flag (among a set?) could be placed within a basic classless html (and no js) page to call forth one or a number of user/user-agent controlled stylings.
This is how I imagine browser support for markdown could work. Plain text comes in over the wire and is rendered to taste.
You should check out Gemini[1]. That's basically how it works.
Re: The plain-text internet is coming
#8I think more things like the Gemini Protocol will continue to be popular. An internet that is deliberately severely bandwidth limited could make navigating between sites much faster. For example, a limit of 100K or even 1K per page for content, or something similar for web assembly applications/modules. Possibly combine that with entirely ditching JavaScript for web assembly and entirely separating applications from…
> I think more things like the Gemini Protocol will continue to be popular.
Saying "continue" would mean that it is popular now, outside of a very small handful of niche sites I'd say gemini is not popular. I follow this space a bit and I basically only know of https://drewdevault.com/ that actually use it.
Re: The plain-text internet is coming
#9Earlier quoted context omitted.
This is how I imagine browser support for markdown could work. Plain text comes in over the wire and is rendered to taste.
You should check out Gemini[1]. That's basically how it works. [1]: https://gemini.circumlunar.space/
Gemini sets a good example, but what I’m specifically advocating for is an incremental improvement to how we use the existing web. Fixing e.g. [1] (falling back to plaintext) should be trivial, and with that obstacle removed there would be nothing stopping early adopters from publishing in markdown today.
Re: The plain-text internet is coming
#10I think more things like the Gemini Protocol will continue to be popular. An internet that is deliberately severely bandwidth limited could make navigating between sites much faster. For example, a limit of 100K or even 1K per page for content, or something similar for web assembly applications/modules. Possibly combine that with entirely ditching JavaScript for web assembly and entirely separating applications from…
We called this the WWW back in the day using Gopher and then web browsers with HTML ;) Tags introduced in HTML 1.0: , , Base Address, , , , , , ..., , ..., (with and ), (with ), and . Gemtext 1.0(?) markup: headlines (three levels), list items, pre-formatted text, quotes, links. Not sure what you mean with 100% content-centric. No ads? Brutalist Websites?
Wow I will have to look up some of those.