PrivateLemur@lemmy.one to Meta (lemmy.one)@lemmy.oneEnglish · edit-21 year agoIs it just me or all remote communities are broken?plus-squaremessage-squaremessage-square5fedilinkarrow-up14arrow-down10
arrow-up14arrow-down1message-squareIs it just me or all remote communities are broken?plus-squarePrivateLemur@lemmy.one to Meta (lemmy.one)@lemmy.oneEnglish · edit-21 year agomessage-square5fedilink
minus-squarePrivateLemur@lemmy.oneOPtoFirefox@lemmy.ml•Trackers in forks of Firefox for AndroidlinkfedilinkEnglisharrow-up1arrow-down1·1 year agoSo I think that this is a bad decision by Mozilla. Who’s idea was it to make a trackerless fork crash? I can’t think of any good reason for them to make it impossible for a forked browser to function properly, if they try to remove all trackers. Even if you can be sure that the code is junk and harmless, that’s unfortunate and just doesn’t look good IMO. linkfedilink
PrivateLemur@lemmy.one to Firefox@lemmy.ml · 1 year agoTrackers in forks of Firefox for Androidplus-squaremessage-squaremessage-square9fedilinkarrow-up131arrow-down13
arrow-up128arrow-down1message-squareTrackers in forks of Firefox for Androidplus-squarePrivateLemur@lemmy.one to Firefox@lemmy.ml · 1 year agomessage-square9fedilink
So I think that this is a bad decision by Mozilla. Who’s idea was it to make a trackerless fork crash?
I can’t think of any good reason for them to make it impossible for a forked browser to function properly, if they try to remove all trackers.
Even if you can be sure that the code is junk and harmless, that’s unfortunate and just doesn’t look good IMO.