Where can I find some Titan URLs to test my client implementation?

=> 😈 dimkr

2024-04-05 · 10 months ago · 👍 norayr

8 Comments ↓

=> 🕹️ skyjake [...] · 2024-04-05 at 08:42:

There is the transjovian.org wiki, and here on BBS you can do long text and image uploads in the draft composer, of course.

=> — transjovian.org/page/How%20To

Back when I added Titan support in Lagrange I also tested against a simple Titan server Python script, however I can't seem to find it any more. My GmCapsule server could be relatively easily configured to run a CGI script on Titan requests, though.

=> 😈 dimkr [OP] · 2024-04-09 at 10:18:

@skyjake Why does Lagrange append a trailing / in some Titan URLs, e.g. titan://hd.206267.xyz/users/avatar?

=> 🕹️ skyjake [...] · 2024-04-09 at 10:27:

As far as I can see, for example on the page

=> — hd.206267.xyz/users/settings

the URL in question does have a trailing /:

## Profile

=> /users/name 👺 Set display name
=> /users/bio 📜 Set bio
=> titan://hd.206267.xyz/users/avatar/ 📷 Set avatar

In other words, Lagrange is not appending a slash there. Do you have any other places where you are suspecting this?

=> 😈 dimkr [OP] · 2024-04-09 at 13:57:

@skyjake When I remove the trailing /, Lagrange is still appending it (and the server accepts /users/avatar, without trailing /), so I added the trailing / in the server side as a workaround. I'm using the Android version. For some reason, this doesn't happen with the post upload pages like /users/upload/private.

=> 😈 dimkr [OP] · 2024-04-09 at 17:41:

@skyjake Some screenshots to demonstrate https://imgur.com/a/TgyTs6f

=> 🕹️ skyjake [...] · 2024-04-10 at 08:04:

I can reproduce the erroneous slash-appending behavior on mobile (iOS) but not on desktop. Likely a mobile-specific bug then... The mobile UI is slightly different when it comes to entering the upload URL path so that's where the problem must be.

=> 🕹️ skyjake [...] · 2024-04-10 at 08:34:

This should fix it:

=> — Commit f4e0a60b6 on git.skyjake.fi

This will be included in future mobile builds.

The issue was indeed specific to mobile, and also required the URL to have a username prefix, "/users/" in this case. The code considered the slash redundant although it really isn't, leading to the slash being omitted/added based on the wrong conditions.

This is related to the wider issue on hd.206267.xyz where "/users/" appears without it meaning something like a subdirectory for user home directories, as Lagrange assumes.

IIRC, the plan was to add a site-specific setting to disable the user root detection to alleviate cases like this.

=> 😈 dimkr [OP] · 2024-04-10 at 12:16:

@skyjake Thanks, this explains many weird things I saw when writing my Titan client :)