Different gemini clients seem to disagree about the format of finger urls #224
I started using finger://user@hostname for finger urls but then noticed that it didn't work in Lagrange so I changed it to finger://hostname/username as suggested by the author of Lagrange, now it does not work in Bombardillo since that expects the first format (Amfora fails on both, apparently it has no support for finger internally)
I wonder if it would make sense to support either or which one is the right one. The spec was never finalized as I understand
We support a format that is compliant with RFC1738 (the lagrange format is also compliant). The Lynx web browser supports finger as well and supports both formats. An argument can be made that both lagrange and bombadillo should support both. This is essentially a dead application in terms of updates (though it should work just fine). So I will not be updating so little used a feature at this time. skyjake is generally very proactive w/ lagrange development. I'll try to remember to mention the various formats supported and see if they can update their end.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?