It was thus said that the Great Travis Briggs once stated: > 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 > <https://en.wikipedia.org/wiki/Psychedelic_experience> me up is the fact > that wikipedia <https://en.wikipedia.org> articles are written > <https://en.wikipedia.org/wiki/Writing> 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? Okay, here's a blog post I made a few days ago [1] and how it could be rendered into a text/gemini. -spc [1] http://boston.conman.org/2020/04/23.1 === Of course, after I point the finger to LibreSSL [1] for the memory leak, I find the leak ? in my own code. => gemini://boston.conman.org/2020/04/22.1 [1] Sigh. Not knowing what else to do, I thought I would go through my TLS Lua module [2] to make sure I didn't miss anything. That's when I noticed that I was keeping a reference to a connection so that I can deal with the callbacks [3] from libtls. I was expecting the __gc() method to clean things up, but with a (non-weak) reference, that was never going to happen. => https://github.com/spc476/lua-conmanorg/blob/master/src/tls.c [2] => https://github.com/spc476/lua-conmanorg/blob/master/src/tls.c#L107 [3] Yes, just because you are using a garbage collected language doesn't mean you can't still have memory leaks. I verified that, yes indeed, the references were being kept around after the request was finished. It was then straightforward to fix the issue. That's not to say that libtls still isn't leaking memory?it is, but (it seems) only when you initialize it (which means it's not as bad). But I'll know in a day or two if I fixed the leak. I hope that was it.
---
Previous in thread (2 of 17): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)
Next in thread (4 of 17): 🗣️ Travis Briggs (audiodude (a) gmail.com)