commit a891ce73d27312b826ac49429302068a39e58f32
parent 4e759ecf7cdf23d3a40a1a3b963fd88b230d5f13
Author: William Casarin <jb55@jb55.com>
Date: Wed, 27 Oct 2021 22:44:30 -0700
show known issues
Diffstat:
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/index.gmi b/index.gmi
@@ -9,3 +9,11 @@ Welcome to the fedwiki gemini portal. Here are some interesting links to get you
> When I think of federation I'm thinking about the distributed evolution of knowledge
=> https://www.youtube.com/watch?v=3nB8ml6UowE YouTube - The Federated Wiki
=> /ward.bay.wiki.org/distributed-truth Distributed Truth
+
+## Known Issues
+
+One unique aspect of the federated wiki is the amount of javascript client-side logic in the browser client. For instance, when you try to visit a local article that does not exist, it will look to see if this article is available elsewhere in the forked neighborhood. Since there is no way to do client-side logic in gemini you just get Not Found.
+
+We could do existence checks before the page is served, but this could slow down the request. I'm open to suggestions for ways to show neighborhoods and federation features.
+
+We could do a better job at rendering images and other content as well. Not every wiki item is supported. Mainly just paragraphs, unprocessed markdown, and unprocessed html at the moment. We could use a bit more code to clean up the markdown and html before rendering it to gemtext.
