Considering mine with the ability to integrate the mobile apps a bit more; I'd imagine a revised approach would be:
- Use App Links as described by Tib as the primary solution, due to the better UX
- Keep the core concept of the universal link idea but ammend the logic to work on Anchors rather than URL Parameters, for situations the above doesn't work.
2.1) Add a huge "Install/Open Joplin" button, to cover people who don't have it installed at all. Unfortunately I don't think this covers people without JS.
So I'm no web tech, but from what I've seen in e.g Bitwarden or Protonmail, the browser doesn't send anchors as part of the HTTP payload, so hypothetically e.g:
joplincloud.com/redirect#noteID
Is all you need.
Unlike my (original) example, we know the target is always joplin://, so there's no point including it and making it impossible for malicious users to change it to e.g steam:// is a huge win.
And secondly, the server doesn't recieve the note ID at all, even in any HTTP logs, becuase the browser physically never sends the NoteID to the server.
So following, it's still stateless and cheap, since it's all client side logic (all files including the App Link JSON files are static).
1 Like
