Re: Memory leak

From	piorunz <piorunz@gmx.com>
Newsgroups	linux.debian.user
Subject	Re: Memory leak
Date	2022-02-11 21:20 +0100
Message-ID	<DPKyB-19j7-3@gated-at.bofh.it> (permalink)
References	<DPGEF-16Zt-5@gated-at.bofh.it> <DPHr3-17fs-9@gated-at.bofh.it> <DPHAJ-17yF-1@gated-at.bofh.it> <DPJ9v-18kD-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 11/02/2022 18:40, Charles Curley wrote:

> My solution is simple: I switched to Vivaldi over a year ago, and
> haven't looked back. https://vivaldi.com. They have packages for
> Debian, and run a roughly two week release cycle. It's based on
> Chromium, but with better privacy settings for the defaults.

Unfortunately, Vivaldi is not acceptable for inclusion in Debian
project, because it's not GPL licensed. It's not fully open source, it
comes with EULA and privacy policy which you must accept in order to use
it. Binaries are not reproducible due to lack of 100% source code.

Therefore I must stay with Firefox for now, it's 100% FOSS, it's
maintained by Debian as well. I won't entrust commercial company,
Vivaldi Technologies AS from Oslo, with my browsing data.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

Thread

Memory leak Celejar <celejar@gmail.com> - 2022-02-11 17:10 +0100
  Re: Memory leak Charles Curley <charlescurley@charlescurley.com> - 2022-02-11 18:00 +0100
    Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 18:10 +0100
      Re: Memory leak Charles Curley <charlescurley@charlescurley.com> - 2022-02-11 19:50 +0100
        Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 21:10 +0100
          Re: Memory leak Charles Curley <charlescurley@charlescurley.com> - 2022-02-11 23:40 +0100
        Re: Memory leak piorunz <piorunz@gmx.com> - 2022-02-11 21:20 +0100
      Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 20:50 +0100
  Re: Memory leak Stefan Monnier <monnier@iro.umontreal.ca> - 2022-02-11 19:50 +0100
    Re: Memory leak Linux-Fan <Ma_Sys.ma@web.de> - 2022-02-11 20:20 +0100
      Re: Memory leak David Wright <deblis@lionunicorn.co.uk> - 2022-02-13 18:10 +0100
    Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 20:50 +0100
      Re: Memory leak Stefan Monnier <monnier@iro.umontreal.ca> - 2022-02-12 18:50 +0100
        Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-14 22:50 +0100
  Re: Memory leak "Roy J. Tellason, Sr." <roy@rtellason.com> - 2022-02-12 00:20 +0100
    Re: Memory leak piorunz <piorunz@gmx.com> - 2022-02-12 09:10 +0100
      Re: Memory leak Curt <curty@free.fr> - 2022-02-12 13:50 +0100
        Re: Memory leak piorunz <piorunz@gmx.com> - 2022-02-14 02:30 +0100
    Re: Memory leak Curt <curty@free.fr> - 2022-02-12 11:20 +0100
      Re: Memory leak rhkramer@gmail.com - 2022-02-12 15:30 +0100
        Re: Memory leak Felmon Davis <moelmoel2714@gmail.com> - 2022-02-12 23:50 +0100
        Re: Memory leak <tomas@tuxteam.de> - 2022-02-13 07:30 +0100
          Re: Memory leak rhkramer@gmail.com - 2022-02-13 16:10 +0100
            Re: Memory leak <tomas@tuxteam.de> - 2022-02-13 16:20 +0100
            Re: Memory leak "Andrew M.A. Cater" <amacater@einval.com> - 2022-02-13 17:10 +0100
        Re: Memory leak "Roy J. Tellason, Sr." <roy@rtellason.com> - 2022-02-13 21:00 +0100
          Re: Memory leak rhkramer@gmail.com - 2022-02-14 02:20 +0100
      Re: Memory leak Felmon Davis <moelmoel2714@gmail.com> - 2022-02-12 23:50 +0100
        Re: Memory leak <tomas@tuxteam.de> - 2022-02-13 07:40 +0100
          Re: Memory leak Tixy <tixy@yxit.co.uk> - 2022-02-13 09:10 +0100
            Re: Memory leak Andrei POPESCU <andreimpopescu@gmail.com> - 2022-02-13 17:10 +0100

csiph-web