|
|
|
|
|
by caslon
1535 days ago
|
|
John wants to read a blog over HTTP. John reads the blog. There is a link. It is to a social media website. He clicks on the link. The social media website requires JavaScript. John has no context for the blog he was reading, and is saddened by the fact that his experience has been ruined. John wants to read a blog over Gopher. John reads the blog. There is a reference to another piece of content. It is either made to work with the form or is self-contained, so as to be usable in the context of a Gopher browser. John is happy. A platform's total capabilities matter, because there will be links to the edges of its capabilities. If you have a blog over Gopher, you probably aren't going to link to a JavaScript-heavy site, because an author posting over Gopher is more likely to be ideologically-opposed to JavaScript. If you have a blog over HTTP, you probably are. A platform's intentions matter. |
|
No I don't agree. If you have a HTTP blog where you go on tirades about how Javascript is bad, you probably won't post links to web sites that use Javascript either. I've seen people who actually do this. It's the same thing, there's no value added by using another platform which has nothing to do with it. You know you can also put HTTP links in a gopher site, and vice versa? They're just text. Either way you have no way of knowing what kind of links the blogger will share until you actually read the blog.
What you're more concerned about is actually the intention and motives of the blog operator, not the platform. If you believe Gopher is good at being an indicator of that because by this point it's become very insular and self-contained and all the users are bitter about outside things, I've also seen HTTP blog communities that are that way too. Gopher sites are not the only places where you can find blog rings. Hope that's helpful to your activities.