Firefox is removing RSS features, but defaults to allowing third-party cookies.
Firefox, your priorities are wrong.
Remove the old RSS code, make it new. Block third-party cookies.
Or drop RSS like it was gopher+, and block third-party cookies.
Or ignore everything I've said and block third-party cookies.
@maiki there's something to be said for using icecat instead as it defaults to all the right things.
Most repos are still using the one based on ESR 52 atm though. I believe they recently released a new version based on ESR 60 to take advantage of the new Quantum changes
@maiki I take it you want to block third-party cookies
@maiki Honestly, Thunderbird was always better than Firefox for RSS imo, but Mozilla don't want to support it any more it seems.
@maiki how do you feel about third party cookies tho?
@maiki That might make me change to a different browser. Like Vivaldi, or go back to dooble.
@maiki Or at least turn on tracking protection by default. I don't think they'll ever default to something that breaks as much stuff as turning off third party cookies does.
@freakazoid I turn off third party cookies and I live an engaging life online. I have no doubt that some folks will be set back, but does it really "break as much"? Is the breaking happening to tracking systems?
@maiki One of the main things that ends up breaking for me is Duo, which my work uses for 2FA. In general anything that uses third-party authentication seems to break. Not sure if it breaks oauth. Hard to know since I use Privacy Badger instead due to the breakage I experienced before.
@freakazoid I hear what you're saying. You are affected. But your web browser shouldn't be able to betray you because companies use weird techniques. And that's the broader point: Mozilla/Firefox and whoever, we don't need *two* or *three* major browsers following Silicon Valley off the cliff. We **could definitely use** at least one mainstream browser that draw a hard line in the sand.
@maiki The average user is just going to switch back to Chrome if stuff mysteriously breaks in FF but works in Chrome. Unfortunately they need to walk a line between trying to protect people's privacy and actually being used. The vast majority of people don't care enough about privacy to be willing to put up with any amount of breakage at all for it.
@maiki There is definitely a place for this approach, but Mozilla's goal is not to protect privacy above all else, so they're not the organization to do it.
@freakazoid I agree. And it's kinda sad, because either I drank the wrong koolaid, or that project "adapted" enough to no longer be aligned with my values.
@freakazoid how has that point ever been proven, if no alternatives exist? Are we to design based on the idea that sheeple don't care and need protecting?
I'm kinda ranting. I'm done being okay with business as usual. For just once I'd like to see everyone let stubborn people vote themselves into an immediate nightmare, rather than drag the rest of us along in "compromise".
@maiki I totally agree with you. FF/Mozilla do need to push the envelope more, but they've lost a LOT of users to Chrome. I hate to say it but they probably need to be spending more time/money on marketing (i.e. education/outreach).
@maiki It'd be great if they could get more people to switch to FF *expecting* that some things will break and being fine with that or even wanting it.
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko