https://wiki.rossmanngroup.com/wiki/Mozilla_introduces_TOS_to_Firefox
https://wiki.rossmanngroup.com/wiki/Mozilla
https://librewolf.net/

00:00:00 - tl;dr solution use librewolf
00:00:52 - my tl;dr thoughts
00:01:08 - what mozilla did
00:02:28 - mozilla crashed archive.org
00:03:03 - Louis gets trolled by a monster
00:03:56 - firefox’ removes statement on not selling personal data.
00:04:40 - terms were changed without explicitly alerting users
00:05:08 - mozilla did this at the WORST POSSIBLE TIME
00:07:05 - the worst communication policy
00:07:14 - California consumer protection act
00:08:03 - The suspicious part mozilla put in
00:08:26 - What is “selling data” ?
00:08:54 - Existing business practices exist in grey areas to CCPA
00:12:46 - Just use librewolf to avoid all this…
00:16:27 - Privacy policy is still fairly strong
00:17:20 - How money for nothing destroys people & companies

  • easily3667@lemmus.org
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    2
    ·
    edit-2
    16 hours ago

    Weird take. Web browsers are document display systems that got a bunch built on top of them. Old websites are just documents. Web browsers are meant to render them. New websites are a single html entry point that hands all website construction to JavaScript which then creates a fake document in memory for the web browser to render.

    Which one is the convoluted, hard to implement and support one?

    Example: NYTimes website is literally a giant document. It could be pure html and lose nothing by being rendered on the server side…except capitalism. So it can’t be a document because the NYTimes needs to extract a reliable and consistent money stream from people, which means it needs to be enforced (according to them) and thus JavaScript.