Different gemini clients seem to disagree about the format of finger urls #224

Closed
opened 2023-02-18 13:07:46 +00:00 by alexlehm · 1 comment

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

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
Owner

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.

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](https://lynx.invisible-island.net/lynx_help/lynx_url_support.html#finger_url). 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.
sloum closed this issue 2023-11-30 01:59:29 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sloum/bombadillo#224
No description provided.