Acidus
Acidus
Lagrange currently has a "Copy Fingerprint" button under a "Certificate" section of the "Page Information" model. Lagrange uses this to mean the SHA-256 hash of just the bytes of the...
I'm running the latest version of Lagrange. Looking at server logs, I see the correct status code, MIME type, and bytes being sent.
There are files in Geminispace incorrectly served with a `text/gemini` MIME type that are really binaries. Lagrange crashes, locks up, or becomes very slow when loading these URLs, depending on...
This PR adds an `images-only` option to the `--links` parameter. `--links images-only` behaves just like `--links off` except it *does* convert image links into gemtext link lines. I'm not a...
md2gemini removes any trailing newlines or whitespace in the source file from its output. The file `3.md` below ends with 3 `\n` characters. But the output of `md2gemini` has no...
I can appreciate the challenges of converting hyperlinks in Markdown to gemtext, and I think the `--links` options cover most use-cases. However image links are different. They are also semantically...
`warcio recompress` will silently add a `WARC-Payload-Digest` field to records that don't already have a payload digest field. This appears to only happen if the record already has a `WARC-Block-Digest`...
It appears that `warcio recompress` will add `WARC-Block-Digest` fields to records that do not already have that field. In the ZIP there are 2 warcs. [example-warcs.zip](https://github.com/webrecorder/warcio/files/13865484/example-warcs.zip) In `orig.warc` the `warcinfo`...
I'm using WARC files with non-HTTP traffic, specifically [the Gemini protocol](https://en.wikipedia.org/wiki/Gemini_(protocol)). I'm setting the `WARC-Content-Type` appropriately to reflect this. `warcio check` has been helpful to find problems with WARCs such...
Buran 1.12 is not properly resolving relative URLs. Specifically, Buran is not removing "dot segments" (e.g. `../` or `./`) which is required by RFC 3986 when resolving URLs. Look at...