The endless browser wars
The endless browser wars
Posted Jan 25, 2021 23:15 UTC (Mon) by flussence (guest, #85566)Parent article: The endless browser wars
The setup instructions make it very clear that us non-enterprise peasants, perhaps everyone outside of Mozilla, are not supposed to be even looking at this stuff, much less trying to use it. While it might satisfy the bare minimum required by a legal department (or a distro maintainer who doesn't look too closely at the browsers they ship), it's not open by any stretch of common sense.
A lot of chromium-based products also claim to have source available — in the disused lavatory in the basement, at the end of the corridor filled with landmines, down the unlit stairs with three steps missing. Nobody pretends that's anything other than malicious compliance.
This API key thing is probably the last straw after years of Google being malicious for a lot of distro maintainers; getting Chromium itself to build is an experience in masochism. I wish they'd throw out QtWebEngine too. The Broken Web deserves no quarter in FOSS.
Posted Feb 8, 2021 7:36 UTC (Mon)
by emorrp1 (guest, #99512)
[Link]
I am a happy self-hoster of firefox-syncserver for the data, (but Firefox Account for just identity) and it's been pretty awesome to not worry about sending off my browser history and still be able to sling tabs between devices for reading on the go or at home.
The main issue is that despite some good efforts in 2017, it still hasn't been fully converted to python3 - so in the coming year I'll have to work out how best to keep running it following python2 removal from repositories. Hopefully someone else will do the hard work, then we can package it for debian (#900867) which would hopefully make running it yourself more accessible.
The endless browser wars