Comment by 🚀 mbays
Re: "Illegal Character In URL"
I think it's best to at least give a warning when encountering invalid link URIs. There are a lot of them about (including people jumping the gun and using IRIs), and there might be fewer if gemtext authors were warned by their client about it.
2025-09-14 · 8 months ago
2 Later Comments ↓
🌆 skyjake [...] · 2025-09-14 at 15:13:
@mbays I agree that warnings could help here. The major problem with that approach is that the warning is mostly shown to the wrong audience, i.e., people browsing stuff without any agency to fix the issue. Pragmatically, in this particular instance, Antenna should have acted as the validator and maybe even rejected the invalid URL.
🛸 bluesman [OP] · 2025-09-14 at 16:17:
I added a status message. Blink and you'll miss it though - the text gets replaced with load time, TLS type and cipher suite once the page is done loading. Someday I'll add a log viewer and curious minds will be able to find it there.
Original Post
Illegal Character In URL — A link showed up in Antenna today that won't open in Alhena because the URL contains an unecoded ">". Alhena uses Java's URI class to parse out the scheme, host, path and query and since the URI class strictly implements RFC3986, trying to parse the url throws an exception. That said, the link will open in Lagrange and Amfora. I could probably do some gymnastics to make it work but I'm leaning towards displaying an error message instead. I can't find anything in the...