kixik
Neither servo rendering engine (like gecko), nor verso (an actual rust based web browser based on servo) are quite ready for prime time. But I’m hoping they will be there sooner rather than later. I don’t use Firefox directly, but rather wrappers based on it, Librewolf for the desktop and Mull in part because I’m lazy (I prefer the ankerfox stuff and other to be done for me), and if I want to avoid chromium based browsers, dominating big time (MS browser edge is as well chromium base, electron is chromium in disguise, and now a days QT web engine underneath is chromium as well) well there’s no option yet.
On the other side, nothing guarantees servo and verso (or whatever other servo based browsers in the future) will care about net free advocacy, neither user freedoms, just be concerned about being better technical solutions, :( But I still have high hopes as you might…
Just being a good technical alternative is not good enough now days, :(
This is sad, not just because it’s a trend on Mozilla, but because it shows how mozilla has embraced the corporative kind of mindset. The advocacy team was fundamental for net free principles.
Mozilla based browsers keep being the only practical alternative to web browser dominance, but it itself has degrading its status of resisting bad practices against users and the web in general. And emerging alternatives are also technical alternatives only, with no intention of net freedom advocacy, GPL sort of principles to protect the user and so on.
Sad days indeed, :/
What they’re saying there is that when trying to auto detect the server configurations, there are unexpected connections to cloudfare IPs, which didn’t usually happen with K9. Who posted the concern associated this to telemetry, but the answers are pointing a different direction. But at this point it just guesses, :(
I guess some more formal traffic inspection needs to happen to understand if truly there’s unexpected traffic, where it is directed to, and hopefully infer somehow its purpose. The guesses about what’s happening suggest it’s just about the auto connection, but again, just guesses.
I explored the configurations, and I didn’t find anything about telemetry, and so neither how to disable it. K9 does not have an about:config advanced configuration like desktop Thunderbird does, so if there’s truly telemetry or some other sort of information leakage, then after proving it, perhaps developers realize they can do better. But so far nothing really proving telemetry or information leakage.
Oh, you mean using divestos-fdroid-repo? Well, before it became part of official f-droid I used to do that. I’m not sure how long it’ll take to fix the official f-droid.org builds though, since I’d like to go back to it. The sad thing is that to move from one repo to another one loses all configurations/settings, :( But perhaps it’s truly unsafe to wait until the build on f-droid.org gets fixed, if it ever does it.
Anyone aware if there are efforts to get it back building for f-droid.org? Does it depend on the Fennec issue getting resolved?
I use mull from f-droid, and f-droid started showing that when upgrading Today to version 1.21.1. No idea why until this f-droid app upgrade.
I guess the mull issue is the same. Both fennec and mull are at the same version on f-droid, 129.0.2, and both show in their anti-features that the app contains a known security vulnerability, indicating firefox has fixed several security vulnerabilities since 130.
Is it right to hope that once fennec can get distributed on f-droid, then mull will follow? I’m not planning to move away from mull.
Thanks !
Ohh, do you have miniflux self hosted somewhere so it does the feeds collection, and then on newsflash you hook with the miniflux reader?
What I do to sync (I don’t read feeds on the phone) between desktops is to rsync these 3 dirs:
~/.config/news-flash
~/.local/share/news-flash
~/.local/share/news_flash
That so I don’t lose the feed subscriptions neither the history of what I have already looked at, neither what I’ve kept as starred (there are interesting feeds I want to keep). If miniflux had sort of a client, similar to newsFlash, but that set everything in miniflux rather than locally, so that no matter different desktops (even phones) will have the same starred kept feeds, and the whole history and the like on miniflux… There’s a python client, but I don’t know if it gets any closer to newsFlash. I guess having miniflux, one can hook to it through any web browser as well, but I really like newsFlash interface, hehe.
The sad thing is needing to somehow keep miniflux running somewhere, which is not feasible for me, and perhaps for others, but it’s interesting…
Just so you know you can get push notifications on Jami. Jami has been supporting unified push notification for a while now, but it’s opt-in, some might not opt for it considering reducing privacy a bit, as some actually disable the proxy and some phone specific feature intending to prevent battery exhausting too fast.
For unified push support you can take a look at jami’s article about its unified push support. I use ntfy BTW.
