[ilaksh]

I 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.

[SahAssar]

> 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.

[marginalia_nu]

Here is a nice aggregator for gemini

https://proxy.vulpes.one/gemini/warmedal.se/~antenna/

[ilaksh]

I was playing with it for awhile. Its not literally one person. But anyway the point was really not about Gemini being popular or not but just that general category would continue to be a thing.

[beders]

We called this the WWW back in the day using Gopher and then web browsers with HTML ;)

Tags introduced in HTML 1.0: <TITLE>, <NEXTID>, Base Address, <A>, <ISINDEX>, <PLAINTEXT>, <LISTING>, <P>, <H1>..., <ADDRESS>, <HP1>..., <DL> (with <DT> and <DD>), <UL> (with <LI>), <MENU> and <DIR>.

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?

[ilaksh]

Wow I will have to look up some of those.

https://en.wikipedia.org/wiki/Content_centric_networking

[hinkley]

Low bandwidth internet would also be very useful with mesh networking solutions, which will tend to have bottlenecks at the exit nodes.