PhD student at the Smart Robotics Lab in Imperial College London/Technical University of Munich.
Oh I definitely don't consider it an urgent issue. Just posted it as something to consider in the future. Having a separate error cache sounds like a good idea.
offpunk fakedomain.foocreates a cache entry at
~/.cache/offpunk/gemini/fakedomain.foo/index.gmiwith the following contents:2022-11-24 16:44:31.224119 ERROR while caching gemini://fakedomain.foo/ ***** <class 'socket.gaierror'> = [Errno -2] Name or service not known ***** If you believe this error was temporary, type reload. The ressource will be tentatively fetched during next sync.
As a user experience it's probably better to not store anything if visiting a URL failed.
On 2022-11-09, ~adnano wrote:
Yes, this was intended behavior. I don't think there is a nice way to serialize the path for each certificate onto disk. I would be willing to accept a patch to implement this, as long as it's not too complicated.
-- View on the web: https://todo.sr.ht/~adnano/go-gemini/107#event-211888
One quick solution off the top of my head is replacing all slashes in the path with spaces to allow using it along with the hostname as the certificate filename. Spaces aren't allowed in URL paths so it should be possible to go back to the path from the filename. One issue I can think of though is other characters that are allowed on URL paths but not on filenames (probably only relevant for Windows).
According to section 4.3 of the v0.16.1:
A client certificate ... has its scope bound to the same hostname as the request URL and to all paths below the path of the request URL path.
The go-gemini certificate store currently sets the client certificate scope to just the hostname. Changing this might not be trivial since the on-disk representation of certificates will have to be modified as they're currently saved in files named after the hostname.
My yearly plan was billed about 10 hours ago. The green box in https://meta.sr.ht/billing says:
Your account is paid and up-to-date, and your last payment of $20.00 was made a year ago. Your current yearly payment is $20.00 and will be billed 10 hours ago.
Looking at the code used to generate it, it's using the time of the latest invoice. The invoice for the most recent (10 hours ago) payment is not available yet, resulting in the wrong text.
It was weirdly difficult to find the Markdown page for sr.ht. Could we make it more widespread somehow? (e.g. putting "markdown supported", which links to the page, below or near text boxes supporting markdown).
Agreed 100% on making the supported Markdown elements more discoverable. I still don't know where it is :D Adding it to the git.sr.ht docs would also be nice.
They used to render pretty nicely in both firefox and qutebrowser. But if this is not officially supported I can just change the readme. Is there some documentation about what parts of Markdown/extensions are supported?
Tables containing images used to work fine. See git.sr.ht/~sotirisp/parallaxis for an example that is now broken.
I especially agree on the heading part. More space before headers would make sections much easier to distinguish.
Some way to differentiate code blocks from normal text, such as the background color used in Github, would also be nice.