-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
register gpodder:// protocol to support Podlove Subscribe Button #26
Comments
Yes, it's not implemented for the Sailfish OS browser yet. Thanks for noticing. |
OK, thanks. I wasn't sure at which end to report this, sorry. Do you know if this is already known to the Sailfish devs? |
We can maybe do it with a .desktop file like for other platforms, but I'll have to look at it. If it turns out that it's indeed a shortcoming of the browser, I'll look into forwarding the bug report. |
Currently doing some investigations what can be done at https://github.com/florianjacob/gpo-sailfish - maybe at least support other platforms or alternative sailfish browsers? |
The main problem is still that SailfishOS afaik doesn't have the xdg handler to parse such URI, but I would like to hear what @Keeper-of-the-Keys thinks about this. |
Hey @bionade24 as far as I know you are correct, if I remember correctly I saw that File Browser lists support for xdg-open as a OpenRepos only feature so we could look if we can also add it to the OpenRepos release. |
I'm not sure if Sailfish Browser supports xdg-open, though.
|
Hello!
I'm testing gPodder v4.4.0 on Sailfish 1.1.1.27 and noticed the following problem.
Situation: Using the default browser to click on the Podlove Subscribe Button (please find more details about that here) on a podcast website that supports it (many examples, including shameless self-promo)
Result: On the one hand, gPodder is correctly recognises as installed on the Jolla, but upon confirming to subscribe to that feed with gPodder, the following error appears (apparently when the browser attempts to transfer the feed URL):
The text was updated successfully, but these errors were encountered: