undefined | Better HN

0 pointsGormo8mo ago0 comments

How do you stop users who aren't using the custom browser from accessing these 'tinyweb' HTTP sites? How do you prevent content scrapers and search indexers from accessing them? How do you suppress direct incorporation of 'mainstream' web content into 'tinyweb' content?

If your goal is precisely to create an parallel ecosystem that's "airgapped" from the mainstream web, and you're already going to have to develop custom clients, content formats, and server-side configuration to implement it on top of HTTP, and engage in lots of development work to imperfectly isolate the two ecosystems from each other, why wouldn't you just develop a parallel protocol and start with a clean slate?

0 comments

rglullis8mo ago

> How do you prevent content scrapers and search indexers from accessing them?

How do you that with Gemini?

> If your goal is precisely to create an parallel ecosystem that's "airgapped" from the mainstream web

There is no way you can have an air gapped network with public access. The moment this "parallel ecosystem" showed any content that hinted at something lucrative, you will have people creating bridges between the two networks. Case in point: Google and USENET.

GormoOP8mo ago

> How do you that with Gemini?

You keep it isolated from the ecosystem in which all of those things are taking place.

> The moment this "parallel ecosystem" showed any content that hinted at something lucrative, you will have people creating bridges between the two networks. Case in point: Google and USENET.

The whole point is to minimize the chance of that happening -- by limiting mainstream appeal, keeping it a niche, and avoiding Eternal September -- and to maximize the friction of bridging these two ecosystems. And so far, they've done a fairly good job of it, since Gemini has been expanding for six years without any indication of any of this starting to happen.

rglullis8mo ago

> and to maximize the friction of bridging these two ecosystems.

There is no friction. It's trivial to write a program that can scrape a Gemini network.

If there is no one pulling data from Gemini servers yet, is not because it's difficult do it, but merely because it's still too small to be relevant.

1 more reply

sneak8mo ago

Why would you need to? The big web existing doesn’t hinder or harm the existence of the tinyweb.

j / k navigate · click thread line to collapse

0 pointsGormo8mo ago0 comments

0 comments

rglullis8mo ago

> How do you prevent content scrapers and search indexers from accessing them?

How do you that with Gemini?

> If your goal is precisely to create an parallel ecosystem that's "airgapped" from the mainstream web

GormoOP8mo ago

> How do you that with Gemini?

You keep it isolated from the ecosystem in which all of those things are taking place.

> The moment this "parallel ecosystem" showed any content that hinted at something lucrative, you will have people creating bridges between the two networks. Case in point: Google and USENET.

rglullis8mo ago

> and to maximize the friction of bridging these two ecosystems.

There is no friction. It's trivial to write a program that can scrape a Gemini network.

If there is no one pulling data from Gemini servers yet, is not because it's difficult do it, but merely because it's still too small to be relevant.

1 more reply

sneak8mo ago

Why would you need to? The big web existing doesn’t hinder or harm the existence of the tinyweb.

j / k navigate · click thread line to collapse