💾 Archived View for rawtext.club › ~sloum › geminilist › 000693.gmi captured on 2020-09-24 at 02:23:40. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
colecmac at protonmail.com colecmac at protonmail.com
Fri May 15 23:19:29 BST 2020
- - - - - - - - - - - - - - - - - - - ``` Personally, I think markdown would make the most sense in this usecase. > I have an idea for quickly and vastly expanding the amount of content > that is available in Geminispace. What about a Wikipedia mirror/proxy? I think this idea is kinda flawed. I can only speak for myself,but I'm guessing that most people here want the Geminispace to expandnaturally, and for interesting and unique content to come up. There'snothing wrong with a Wikipedia proxy, but I feel like it misses thepoint a bit. If I want to read Wikipedia, I would just use Firefox. makeworld ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐On Friday, May 15, 2020 6:10 PM, Travis Briggs <audiodude at gmail.com> wrote: > Hello, > > I have an idea for quickly and vastly expanding the amount of content that is available in Geminispace. What about a Wikipedia mirror/proxy? I put proxy in quotes because it would modify the documents it returned in order to be largely text based. > > The main thing that's tripping me up is the fact that wikipedia articles are written with a lot of inline links. And navigating those links is a key part of the Wikipedia browsing experience. > > My naive read of the text/gemini format is that I would have to do something like: > > The main thing that's > = > gemini://gem.wiki-mirror.pizza/article.cgi?Tripping tripping > me up is the fact that > = > gemini://gem.wiki-mirror.pizza/article.cgi?Wikipedia wikipedia > articles are > = > gemini://gem.wiki-mirror.pizza/article.cgi?Writing written > with a lot of inline links. > > Which seems really clunky. The other option I'm considering is serving text/markdown, which I assume most Gemini clients would display as plain text. The problem then is that [links won't be clickable](http://dev/null). But maybe the mere existence of so much markdown content would incentivize some client author to add native support? > > Feedback is appreciated, thanks! > -Travis