summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2021-06-05 10:08:55 +0100
committerPaul Buetow <paul@buetow.org>2021-06-05 10:08:55 +0100
commitbc449f1b85b3e69f34713c84b7e24e56ccdc8418 (patch)
tree471d5fbd88abd1b8649fb9c236bfa9a3171b5b82 /gemfeed
parent2d262af356854fd66eb838ef183f3cf109542a52 (diff)
add lagrange screenshot
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2021-04-24-welcome-to-the-geminispace.gmi5
-rw-r--r--gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.pngbin0 -> 104677 bytes
2 files changed, 3 insertions, 2 deletions
diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.gmi b/gemfeed/2021-04-24-welcome-to-the-geminispace.gmi
index 6e6774de..731fa09a 100644
--- a/gemfeed/2021-04-24-welcome-to-the-geminispace.gmi
+++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.gmi
@@ -1,6 +1,6 @@
# Welcome to the Geminispace
-> Written by Paul Buetow 2021-04-24, last updated 2021-04-30, ASCII Art by Andy Hood
+> Written by Paul Buetow 2021-04-24, last updated 2021-06-05, ASCII Art by Andy Hood
Have you reached this article already via Gemini? It requires a Gemini client; web browsers such as Firefox, Chrome, Safari, etc., don't support the Gemini protocol. The Gemini address of this site (or the address of this capsule as people say in Geminispace) is:
@@ -44,9 +44,10 @@ All I wanted was to read an interesting article, but after a big advertising pop
Around the same time, I discovered a relatively new, more lightweight protocol named Gemini, which does not support all these CPU-intensive features like HTML, JavaScript, and CSS. Also, tracking and ads are unsupported by the Gemini protocol.
-The "downside" is that due to the limited capabilities of the Gemini protocol, all sites look very old and spartan. But that is not a downside; that is, in fact, a design choice people made. It is up to the client software how your capsule looks. For example, you could use a graphical client with nice font renderings and colours to improve the appearance. Or you could use a very minimalistic command line black-and-white Gemini client. It's your (the user's) choice.
+The "downside" is that due to the limited capabilities of the Gemini protocol, all sites look very old and spartan. But that is not a downside; that is, in fact, a design choice people made. It is up to the client software how your capsule looks. For example, you could use a graphical client, such as Lagrange, with nice font renderings and colours to improve the appearance. Or you could use a very minimalistic command line black-and-white Gemini client. It's your (the user's) choice.
=> ./2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png Screenshot Amfora Gemini terminal client surfing this site
+=> ./2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png Screenshot graphical Lagrange Gemini client surfing this site
Why is there a need for a new protocol? As the modern web is a superset of Gemini, can't we use simple HTML 1.0 instead? That's a good and valid question. It is not a technical problem but a human problem. We tend to abuse the features once they are available. You can ensure that things stay efficient and straightforward as long as you are using the Gemini protocol. On the other hand, you can't force every website on the modern web to only create plain and straightforward-looking HTML pages.
diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png b/gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png
new file mode 100644
index 00000000..478d2fdd
--- /dev/null
+++ b/gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png
Binary files differ