Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #201411

Re: basilisk-browser

From <tomas@tuxteam.de>
Newsgroups linux.debian.user
Subject Re: basilisk-browser
Date 2018-10-18 11:20 +0200
Message-ID <wKcDf-49r-9@gated-at.bofh.it> (permalink)
References <wKb4t-36V-5@gated-at.bofh.it> <wKbxv-3wD-7@gated-at.bofh.it> <wKcjU-3Na-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thu, Oct 18, 2018 at 11:49:44AM +0300, Reco wrote:
> 	Hi.
> 
> On Thu, Oct 18, 2018 at 10:02:42AM +0200, tomas@tuxteam.de wrote:
> > > I think its an good alternative to Firefox Quantum.
> > > 
> > > More Infos here: https://www.basilisk-browser.org/
> > 
> > Indeed, it does look good.
> 
> No, it does not. UXP means Palemoon Browser.
> Palemoon means extremely hostile upstream - [1].

Thanks for the link, very instructive.

That would mean (in the context of Debian) that one would have to
(a) use the Basilisk-bundled libs (generally a no-no in Debian)
or (b) use a different name & brand. Yes, we know this story with
Firefox/Iceweasel. That'd mean that the packaging effort would
be a bit... more interesting.

I think both sides have their point, and the sad part for me is
that they didn't manage to tackle the conflict in a more civil
manner. Perhaps a lesson in humility for us all.

> Does Debian project really needs yet another Iceweasel incident?

What the world needs (badly) is more browser alternatives. I'm
seeing everything converging towards the dystopia where one huge
corporation controls the server and the client. We had that, and
it wasn't pretty; nowadays with smartphones, always-on, IoT and
perhaps worse, we are far more vulnerable to that (business?) model.

Cheers
-- t

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

basilisk-browser basti <mailinglist@unix-solution.de> - 2018-10-18 09:40 +0200
  Re: basilisk-browser <tomas@tuxteam.de> - 2018-10-18 10:10 +0200
    Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 11:00 +0200
      Re: basilisk-browser <tomas@tuxteam.de> - 2018-10-18 11:20 +0200
        Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-18 14:50 +0200
          Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 16:40 +0200
            Re: basilisk-browser basti <mailinglist@unix-solution.de> - 2018-10-18 17:00 +0200
              Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 17:10 +0200
        Re: basilisk-browser John Crawley <john@bunsenlabs.org> - 2018-10-19 03:00 +0200
      Re: basilisk-browser Doug <dmcgarrett@optonline.net> - 2018-10-19 01:40 +0200
        Re: basilisk-browser Ben Finney <bignose@debian.org> - 2018-10-19 06:30 +0200
          Re: basilisk-browser Gene Heskett <gheskett@shentel.net> - 2018-10-19 12:40 +0200
        Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 08:40 +0200
          Re: basilisk-browser Dominik George <natureshadow@debian.org> - 2018-10-19 09:00 +0200
            Re: basilisk-browser mick crane <mick.crane@gmail.com> - 2018-10-19 09:30 +0200
              Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 12:30 +0200
                Re: basilisk-browser mick crane <mick.crane@gmail.com> - 2018-10-19 13:10 +0200
              Re: basilisk-browser Gene Heskett <gheskett@shentel.net> - 2018-10-19 12:50 +0200
            Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 11:30 +0200
              Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-19 15:40 +0200
            Re: basilisk-browser Ben Finney <bignose@debian.org> - 2018-10-20 04:20 +0200
              Re: basilisk-browser fmneto@fmneto.com.br - 2018-10-20 05:00 +0200
                Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-20 14:00 +0200

csiph-web