Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-02 Thread Eli Schwartz via arch-dev-public
On 6/2/19 2:59 AM, Ike Devolder wrote: > On Sat, 2019-06-01 at 22:11 -0400, Eli Schwartz via arch-dev-public > wrote: >> On 6/1/19 5:43 PM, Allan McRae via arch-dev-public wrote: >>> On 2/6/19 1:53 am, Ike Devolder via arch-dev-public wrote: On Sat, 2019-06-01 at 21:30 +1000, Allan McRae

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-02 Thread Ike Devolder via arch-dev-public
On Sat, 2019-06-01 at 12:12 +0200, Ike Devolder wrote: > 3 years have passed since I first proposed to bring vivaldi into > community. Now there is a clear differentiation between what vivaldi > offers out-of-the box compared to other browsers. > > Vivaldi offers a ton of customisation features

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-02 Thread Ike Devolder via arch-dev-public
On Sat, 2019-06-01 at 22:11 -0400, Eli Schwartz via arch-dev-public wrote: > On 6/1/19 5:43 PM, Allan McRae via arch-dev-public wrote: > > On 2/6/19 1:53 am, Ike Devolder via arch-dev-public wrote: > > > On Sat, 2019-06-01 at 21:30 +1000, Allan McRae wrote: > > > > You don't seem to > > > >

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Eli Schwartz via arch-dev-public
On 6/1/19 5:43 PM, Allan McRae via arch-dev-public wrote: > On 2/6/19 1:53 am, Ike Devolder via arch-dev-public wrote: >> On Sat, 2019-06-01 at 21:30 +1000, Allan McRae wrote: >>> You don't seem to >>> explain why you need to ask in your email. >> >> Because it is proprietary and I explain that

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Allan McRae via arch-dev-public
On 2/6/19 1:53 am, Ike Devolder via arch-dev-public wrote: > On Sat, 2019-06-01 at 21:30 +1000, Allan McRae wrote: >> You don't seem to >> explain why you need to ask in your email. > > Because it is proprietary and I explain that now there is a valid > reason compared to 3 years ago where there

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Ike Devolder via arch-dev-public
On Sat, 2019-06-01 at 18:06 +0200, Andreas Radke via arch-dev-public wrote: > Am Sat, 01 Jun 2019 17:53:58 +0200 > schrieb Ike Devolder via arch-dev-public > : > > > On Sat, 2019-06-01 at 21:30 +1000, Allan McRae wrote: > > > You don't seem to > > > explain why you need to ask in your email. >

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Andreas Radke via arch-dev-public
Am Sat, 01 Jun 2019 17:53:58 +0200 schrieb Ike Devolder via arch-dev-public : > On Sat, 2019-06-01 at 21:30 +1000, Allan McRae wrote: > > You don't seem to > > explain why you need to ask in your email. > > Because it is proprietary and I explain that now there is a valid > reason compared to

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Ike Devolder via arch-dev-public
On Sat, 2019-06-01 at 21:30 +1000, Allan McRae wrote: > You don't seem to > explain why you need to ask in your email. Because it is proprietary and I explain that now there is a valid reason compared to 3 years ago where there was practically no difference between vivaldi, chromium and opera.

Re: [arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Allan McRae via arch-dev-public
On 1/6/19 8:12 pm, Ike Devolder via arch-dev-public wrote: > 3 years have passed since I first proposed to bring vivaldi into > community. Now there is a clear differentiation between what vivaldi > offers out-of-the box compared to other browsers. > > Vivaldi offers a ton of customisation

[arch-dev-public] bringing vivaldi browser to community

2019-06-01 Thread Ike Devolder via arch-dev-public
3 years have passed since I first proposed to bring vivaldi into community. Now there is a clear differentiation between what vivaldi offers out-of-the box compared to other browsers. Vivaldi offers a ton of customisation features out of the box, and is also able to just use the chrome/ium addons