Are you using it as a podcast provider or as a live radio? For the latter, it’s usually possible to extract the streaming URL via web inspector. or simply search for it on your favorite radio app.
The live feature works.
Not sure what “podcast” covers, as you don’t have to actively download/save. But indeed, I have a problem re-playing, so as you say, it is a stored-somewhere file.
I admit beyond laziness, I could rummage to find the mp3 file, but I need a big screen for that. Not hyper fun in the bus.
And sometimes, it is nice to press and listen, simply. CLI-lifestyle relief :–)
You don’t have to do that with podcasts either. What I meant is chosing episodes* to listen to, as opposed to letting the station choose what’s on right now.
But to the point, yeah of course you won’t open the web inspector on the jolla browser (is that even possible?). The only other solution I can see are RSS feeds for your favorite station. Searching “radio france rss feeds”, this comes up:
* the site itself refers to these as podcasts
1 Like
Thank you very much for these pointers, let’s see how I can get closer to the play button 'lazy experience".
if this is the current version of the SFOS browser then twitter no longer works.
Works fine here. Are you sure it wasn’t an issue on their end?
it stopped working about four days ago, so out for about three days, but i too noticed it started loading the page content again yesterday. and still does so as expected today…
so yes; looks like a temp problem their end.
I’m curious re this site:
Is this because of a misconfiguration in their certificate or something else?
Can others get to it or see:
"Secure Connection Failed”
For me on C2 going to fairphone.com causes a segmentation fault in the browser
https://www.file.io/ shared link to video = blank white page
Talking about local network apps, TrueNAS and PiHole stopped working 
This is due to SVG sprite icons lacking a height. I would guess something like a low-priority :where(.icon, .Icon) { height: 1em } in the userContent.css might be safe enough to prevent this (where if we at least go v103 you could set user_pref("layout.css.has-selector.enabled", true); in ~/.local/share/org.sailfishos/browser/.mozilla/user.js something like svg:has(use[href*="icon.svg#"], use[href*="icons.svg#"]) { height: 1em; } would be a closer bet vs. class names).
That’s because everybody uses the same crappy framework(s).
This probably isn’t that true. I agree that some of these knobs are too aggressively targeting “evergreen” browsers or 1% of market usage, but there are 2 issues:
- most of the tooling is built around
browserslist& Jolla doesn’t have themselves even on the list so you have to know to target Fx 91 - Fx 91 was released 2021-08-10, which is a long time for a full-featured browser for even security reasons. You can even see Mozilla putting a big warning callout that 115 is getting an emergency extension for Window 7–8.1. Everything before that is end of life, not getting security updates so it’s quite unsafe to be even browsing on a browser this old. A simpler browser like NetSurf or Dillo can get away with languishing a bit better since they lack so many features that they don’t even support JavaScript or SVG.
Do most sites even use half the features from more modern browser? Not really, & web devs had workarounds to make all of this just fine/good enough last decade, but there have been improvements as well that devs don’t want to ignore for a tiny slice of the market.
One of the lowest-hanging courses of action tho would be to get visibility in browserslist + caniuse.com to let developers at least have an easy way to know Sailfish OS is a target.
1 Like
The Sailfish browser does not even have proper versioning or it’s own user-agent, so it cannot be targeted by such tools.
True… but I am wondering if there is so nuance like how Vivaldi just fully lies that it is Chromium to deal with all the compatibility issues of legitimately bad web dev doing UA sniffing over feature detection. UAs are an absolute mess, but do you know why the browser chooses not to identify itself?
Because of the same stupid compatibility issues with websites just looking at the user-agent I would assume. There is even a workaround list in the browser for specific websites to use another user-agent if needed.
Yeah… I have
$ cat ~/.local/share/org.sailfishos/browser/.mozilla/user.js
user_pref("dom.dialog_element.enabled", true);
// workaround for Shopee saying this isn’t a mobile browser lol
user_pref("general.useragent.override", "Mozilla/5.0 (Android 15; Mobile; rv:141.0) Gecko/147.0 Firefox/147.0");
user_pref("layout.css.more_color_4.enabled", true);
user_pref("layout.css.grid-template-masonry-value.enabled", true);
To try to turn on some ‘experimental’ CSS features now standard in an attempt to keep more websites working. It might be worth the community here curating a list here of about:config features that could help—even if they aren’t in a fully-tested state.
1 Like
To follow up, Nextcloud followed up on their threat and the latest update of my local nextcloud (33.0.5snap1) now gives this:
I doubt it. And you can change easily and on multiple ways anyway.