Re: [gentoo-user] Re: Trouble on the horizon!

2018-09-24 Thread Mark David Dumlao
On Mon, Sep 24, 2018 at 6:34 PM Nikos Chantziaras  wrote:
>
> On 24/09/2018 13:11, R0b0t1 wrote:
> > On Mon, Sep 24, 2018 at 11:01 AM, Nikos Chantziaras  
> > wrote:
> >>
> >> To me it looks like youtubers and some sites trying to make money through
> >> clickbait?
> >>
> >
> > If you had not heard of it elsewhere the Linux code of conduct was
> > amended. It makes the CoC similar to those of other projects where
> > there are a number of (usually nontechnical) contributors who identify
> > as a champion of social justice.
> > [...]
> Well, if kernel developers are fine with that, then I don't see how
> that's relevant to anyone who isn't a kernel dev. If they want to adopt
> social justice politics, that's really their prerogative.
>

Actually, social justice politics didn't seem to have anything to do
with the CoC
adoption. It was more of Linus taking a backseat (due to how he self-assessed
his vacation behavior) and pretty soon after, they adopted CoC, most likely as
some kind of "standardization"

Barely a week has passed since the CoC though, and already there are political
manuevers to oust high-profile kernel devs to the point that some contributors
have started talks on exercising their copyright privileges and
withholding their
code. Which they have a right to do, by the way, if they feel the foundation
has betrayed them.

So as esr has put it:
> First, let me confirm that this threat has teeth. I researched the relevant 
> law
> when I was founding the Open Source Initiative. In the U.S. there is case law
> confirming that reputational losses relating to conversion of the rights of a
> contributor to a GPLed project are judicable in law. I do not know the case 
> law
> outside the U.S., but in countries observing the Berne Convention without the
> U.S.’s opt-out of the “moral rights” clause, that clause probably gives the
> objectors an even stronger case.

(http://esr.ibiblio.org/?p=8139)

This is not a little online trollfest that only affects kernel devs.
This can affect
literally everything. Biblical proportions, dogs and cats living together, etc.
-- 
This email is:[ ] actionable   [x] fyi[x] social
Response needed:  [ ] yes  [ ] up to you  [x] no
Time-sensitive:   [ ] immediate[ ] soon   [x] none



Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread gevisz
пн, 24 сент. 2018 г. в 21:24, J. Roeleveld :
> On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote:
> > I did note in a msg to this list earlier this year (2018)
> > that there had been no kernel stabilised by Gentoo since spring 2017,
> > which suggested there had been some decline in kernel quality.
>
> Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent.

After I configured gentoo-sources-4.14.52 kernel with make oldconfig,
it even could not shut down the computer. So, I came to the same
decision about kernel quality and masked everything later than
gentoo-sources-4.9.95. (My 5 cents. :)



Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor

2018-09-24 Thread gevisz
Thanks to all who has replied to this thread so far.



Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor

2018-09-24 Thread gevisz
вс, 23 сент. 2018 г. в 10:10, Walter Dnes :
>
> On Thu, Sep 20, 2018 at 01:00:39AM +0300, gevisz wrote
> > , 19 . 2018 ??. ?? 11:38, Walter Dnes :
>
> > >  According to
> > > http://www.cpu-world.com/sspec/SL/SLA8Z.html it has...
> > >
> > > MMX SSE SSE2 SSE3 SSSE3
> >
> > Do you mean that it would be enough to set
> > CFLAGS="-O2 -pipe mmx sse sse2 sse3 ssse3"
> > without setting the march cflag at all?
>
>   Yes, that would work.  Remember also to include in make.conf
>
> CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3"

The target processor does not support mmxext.

>   In your jpeg image, I see that the flags include mmx, sse, sse2, pni,
> and ssse3. "pni" == "Prescott New Instructions" == "SSE3".  Looking at
> https://gcc.gnu.org/onlinedocs/gcc-7.3.0/gcc/x86-Options.html#x86-Options
> I suggest "-march=core2" with CPU_FLAGS_X86 same as above.  The "core2"
> option uses MMX, SSE, SSE2, SSE3 and SSSE3 instructions, all of which
> show up in the listing on your jpeg.

Thank you. Looking into https://wiki.gentoo.org/wiki/Safe_CFLAGS#Intel
I also concluded that for the target processor I should set "-march=core2"
but I did not know that core2 option is exactly equivalent to setting mmx,
sse, sse2, sse3 and ssse3 instructions.

So, I decided to spend a day to get my hands on the target computer
and compile everything on it with "-march=native" no matter how much
time it takes.

To conclude this thread, I will post the output of the commands
suggested in this thread later, after the system install will be finished,
just in case somebody will need them in the future.



Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Walter Dnes
On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote

> This is worse than I expected.  OK, therefore never signing into Google's 
> systems with Chromium is the only way to stop this invasion of privacy.  
> Thankfully, we still have Firefox.  ;-)

Ahemm... 
https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firefox.html

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications



[gentoo-user] Re: OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Nikos Chantziaras

On 25/09/2018 00:09, Andrew Udvare wrote:




On Sep 24, 2018, at 10:20, Nikos Chantziaras  wrote:

There is an option for this, actually. Go to:

  chrome://flags/#account-consistency

and set it to "Disabled."



Flags come and go and they are not intended for use by regular users. Based on 
the fact that the flag can be enabled automatically via random field testing, I 
assume the flag will disappear soon in the future, and the feature will be on. 
This is the price of using Chrome unfortunately.


It's not like there's a shortage of browsers. For now, the flags works 
perfectly. If it stops working, well, let's just say I'm not married to 
Google.





[gentoo-user] Re : kernel delay

2018-09-24 Thread Philip Webb
180924 J. Roeleveld wrote:
> On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote:
>> I did note in a msg to this list earlier this year (2018)
>> that there had been no kernel stabilised by Gentoo since spring 2017,
>> which suggested there had been some decline in kernel quality.
> Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent.
> Which are you referring to?

I wrote above 'had', not 'has' : look at the list archive for details.

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] Re: OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Andrew Udvare



> On Sep 24, 2018, at 10:20, Nikos Chantziaras  wrote:
> 
> There is an option for this, actually. Go to:
> 
>  chrome://flags/#account-consistency
> 
> and set it to "Disabled."
> 

Flags come and go and they are not intended for use by regular users. Based on 
the fact that the flag can be enabled automatically via random field testing, I 
assume the flag will disappear soon in the future, and the feature will be on. 
This is the price of using Chrome unfortunately.

Andrew


Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread J. Roeleveld
On Monday, September 24, 2018 2:59:02 PM CEST Rich Freeman wrote:
> On Mon, Sep 24, 2018 at 8:42 AM Philip Webb  wrote:

> > He's  48 yo  & beginning to age a bit & it's no threat to anyone
> > if he's decided to take a break for a few kernel cycles.
> 
> ++  Nobody owns Linus.

Except maybe his wife ;)

> By now the kernel should be at a point where
> others can manage the workflow if he isn't around.

I would assume so.






Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread J. Roeleveld
On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote:
> 180924 Alan Grimes wrote:
> > Whatever SJWs touch, DIES.
> > https://www.youtube.com/watch?v=v5VvJiNUCIA
> > https://itsfoss.com/linux-code-of-conduct/
> > https://lulz.com/linux-devs-threaten-killswitch-coc-controversy-1252/
> 
> I read the texts via LWN.  Linus has been the sergeant-major
> who has to yell at the troops sometimes, when they get sloppy.
> He's a brilliant software engineer & generally knows how to herd cats.
> 
> The problem seems to have arisen when he arranged a family holiday
> which clashed with an important Linux conference
> & irritated a lot of important people in the corporate Linux world.
> He's  48 yo  & beginning to age a bit & it's no threat to anyone
> if he's decided to take a break for a few kernel cycles.
> I did note in a msg to this list earlier this year (2018)
> that there had been no kernel stabilised by Gentoo since spring 2017,
> which suggested there had been some decline in kernel quality.

Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent.

Which are you referring to?

--
Joost





[gentoo-user] ganeti upgrade question

2018-09-24 Thread Alarig Le Lay
Hi,

I have an hypervisor running gentoo. The ganeti version currently
installed is 2.15.2-r5. Emerge asks me to unmask 2.15.2-r7 in order to
install ghc-8 and upgrade dev-haskell/snap-core and
dev-haskell/snap-server.

However app-emulation/ganeti-2.15.2-r7 is marked as ~arch and pulls
sys-fs/lvm2-2.02.181, which is also ~arch.

Is it safe to run those versions in production?

Thanks,
-- 
Alarig



Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread Jack

On 2018.09.24 08:59, Rich Freeman wrote:

++  Nobody owns Linus.


Ain't that the truth, even if it is a typo.

Jack


Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor

2018-09-24 Thread james
On 9/23/18 3:09 AM, Walter Dnes wrote:
> On Thu, Sep 20, 2018 at 01:00:39AM +0300, gevisz wrote
>> , 19 . 2018 ??. ?? 11:38, Walter Dnes :
> 
>>>  According to
>>> http://www.cpu-world.com/sspec/SL/SLA8Z.html it has...
>>>
>>> MMX SSE SSE2 SSE3 SSSE3
>>
>> Do you mean that it would be enough to set
>> CFLAGS="-O2 -pipe mmx sse sse2 sse3 ssse3"
>> without setting the march cflag at all?
> 
>   Yes, that would work.  Remember also to include in make.conf
> 
> CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3"
> 
>   In your jpeg image, I see that the flags include mmx, sse, sse2, pni,
> and ssse3. "pni" == "Prescott New Instructions" == "SSE3".  Looking at
> https://gcc.gnu.org/onlinedocs/gcc-7.3.0/gcc/x86-Options.html#x86-Options
> I suggest "-march=core2" with CPU_FLAGS_X86 same as above.  The "core2"
> option uses MMX, SSE, SSE2, SSE3 and SSSE3 instructions, all of which
> show up in the listing on your jpeg.
> 
> https://en.wikipedia.org/wiki/SSE3
>> SSE3, Streaming SIMD Extensions 3, also known by its Intel code name
>> Prescott New Instructions (PNI), is the third iteration of the SSE
>> instruction set for the IA-32 (x86) architecture.
> 


https://wiki.gentoo.org/wiki/CPU_FLAGS_X86

and similar wiki pages are good links to reference.
MG (M. Gorny) has blogged on this subject too::

https://nlug.ml1.co.uk/2016/09/gentoo-portage-cpu_flags_x86-introduction-2015-01-28/5332

I'd be interested in blogs, irc, docs, etc, where distcc is being used
as part of a (gentoo-centric) CI/CD and/or cross-compiling for
smaller/older target systems, of any architecture (arm or mips or x86 or ?).


James



Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor

2018-09-24 Thread james
On 9/23/18 3:20 AM, Walter Dnes wrote:
> On Thu, Sep 20, 2018 at 01:00:39AM +0300, gevisz wrote
>> , 19 . 2018 ??. ?? 11:38, Walter Dnes :
> 
>>>  According to
>>> http://www.cpu-world.com/sspec/SL/SLA8Z.html it has...
>>>
>>> MMX SSE SSE2 SSE3 SSSE3
>>
>> Do you mean that it would be enough to set
>> CFLAGS="-O2 -pipe mmx sse sse2 sse3 ssse3"
>> without setting the march cflag at all?
> 
>   Yes, that would work.  Remember also to include in make.conf
> 
> CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3"
> 
>   In your jpeg image, I see that the flags include mmx, sse, sse2, pni,
> and ssse3. "pni" == "Prescott New Instructions" == "SSE3".  Looking at
> https://gcc.gnu.org/onlinedocs/gcc-7.3.0/gcc/x86-Options.html#x86-Options
> I suggest "-march=core2" with CPU_FLAGS_X86 same as above.  The "core2"
> option uses MMX, SSE, SSE2, SSE3 and SSSE3 instructions, all of which
> show up in the listing on your jpeg.
> 
> https://en.wikipedia.org/wiki/SSE3
>> SSE3, Streaming SIMD Extensions 3, also known by its Intel code name
>> Prescott New Instructions (PNI), is the third iteration of the SSE
>> instruction set for the IA-32 (x86) architecture.
> 

Here is some short docs (by MG) on the subject, that are good to save
for future reference::


https://nlug.ml1.co.uk/2016/09/gentoo-portage-cpu_flags_x86-introduction-2015-01-28/5332

or in the gentoo wiki::
https://wiki.gentoo.org/wiki/CPU_FLAGS_X86

Note, some years ago, distcc was excellent as I used it daily. Like
most codes it changes/stresses over the years. So follow distcc
details closely if you intend for it's dependable results. Perhaps
someone (gentoo) is using it in a CI/CD configuration, which would
be of keen interest to many.


hth,
James



[gentoo-user] Re: OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Nikos Chantziaras

On 24/09/2018 10:09, Andrew Udvare wrote:

I can understand not wanting this feature but unfortunately Google
does not believe in options when it comes to Chrome. They are always
removing or obscuring them. They seem to have a feeling that if there
are options (more than one good default setting), something is
wrong.


There is an option for this, actually. Go to:

  chrome://flags/#account-consistency

and set it to "Disabled."




Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Mick
On Monday, 24 September 2018 13:47:05 BST Andrew Udvare wrote:
> > On 2018-09-24, at 06:29, Mick  wrote:
> > 
> > 
> > Unless I understood this wrong, 'Google Chrome' will not be able to
> > perform
> > this (dis)service, unless you have enabled the "Offer to save passwords"
> > feature AND|OR you use Chrome to sign in to an Alphabet related website.
> 
> This is not necessarily true because AFAIK it works by taking the session
> generated from within Google's main sign on page and applying that session
> to the browser.
> > Is Chromium also affected by this?
> 
> Yes.

:-(

This is worse than I expected.  OK, therefore never signing into Google's 
systems with Chromium is the only way to stop this invasion of privacy.  
Thankfully, we still have Firefox.  ;-)

I assume closing the browser terminates the session and login, both in the 
browser and in the Google websites.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread Rich Freeman
On Mon, Sep 24, 2018 at 8:42 AM Philip Webb  wrote:
>
> The problem seems to have arisen when he arranged a family holiday
> which clashed with an important Linux conference
> & irritated a lot of important people in the corporate Linux world.

I can't imagine that it helped when they moved the conference to where
he was going to be.  If somebody had booked flights months ago to get
lower rates, had hotels reserved, and so on, then that is a lot of
rebooking, change fees, and so on, and chances are the accommodations
aren't the same as what you'd have gotten with planning ahead.

> He's  48 yo  & beginning to age a bit & it's no threat to anyone
> if he's decided to take a break for a few kernel cycles.

++  Nobody owns Linus.  By now the kernel should be at a point where
others can manage the workflow if he isn't around.

-- 
Rich



Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Andrew Udvare



> On 2018-09-24, at 06:29, Mick  wrote:
> 
> 
> Unless I understood this wrong, 'Google Chrome' will not be able to perform 
> this (dis)service, unless you have enabled the "Offer to save passwords" 
> feature AND|OR you use Chrome to sign in to an Alphabet related website.

This is not necessarily true because AFAIK it works by taking the session 
generated from within Google's main sign on page and applying that session to 
the browser.

> 
> Is Chromium also affected by this?

Yes.

-- 
Andrew Udvare




Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread Philip Webb
180924 Alan Grimes wrote:
> Whatever SJWs touch, DIES.
> https://www.youtube.com/watch?v=v5VvJiNUCIA
> https://itsfoss.com/linux-code-of-conduct/
> https://lulz.com/linux-devs-threaten-killswitch-coc-controversy-1252/

I read the texts via LWN.  Linus has been the sergeant-major
who has to yell at the troops sometimes, when they get sloppy.
He's a brilliant software engineer & generally knows how to herd cats.

The problem seems to have arisen when he arranged a family holiday
which clashed with an important Linux conference
& irritated a lot of important people in the corporate Linux world.
He's  48 yo  & beginning to age a bit & it's no threat to anyone
if he's decided to take a break for a few kernel cycles.
I did note in a msg to this list earlier this year (2018)
that there had been no kernel stabilised by Gentoo since spring 2017,
which suggested there had been some decline in kernel quality.

As for New Yorker + their drama queen Ms Theythem,
they're simply trying to cash in on the incident to promote themselves.
The rest of us should concentrate on the real world + its many problems.

My  CAD 0,02 .

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] Re: Trouble on the horizon!

2018-09-24 Thread R0b0t1
On Mon, Sep 24, 2018 at 12:33 PM, Nikos Chantziaras  wrote:
> On 24/09/2018 13:11, R0b0t1 wrote:
>>
>> On Mon, Sep 24, 2018 at 11:01 AM, Nikos Chantziaras 
>> wrote:
>>>
>>>
>>> To me it looks like youtubers and some sites trying to make money through
>>> clickbait?
>>>
>>
>> If you had not heard of it elsewhere the Linux code of conduct was
>> amended. It makes the CoC similar to those of other projects where
>> there are a number of (usually nontechnical) contributors who identify
>> as a champion of social justice.
>> [...]
>
> Well, if kernel developers are fine with that, then I don't see how that's
> relevant to anyone who isn't a kernel dev. If they want to adopt social
> justice politics, that's really their prerogative.
>
>

I suspect why he posted it is at least a few developers do not want
this to happen. Other large projects have had similar turmoil, but
there is usually no remedy if you disagree.

E.g. Django(?) had a large patch committed that changed the names of
master/slave to something else as the terms were considered abusive by
what looks to be a minority.



[gentoo-user] Re: Trouble on the horizon!

2018-09-24 Thread Nikos Chantziaras

On 24/09/2018 13:11, R0b0t1 wrote:

On Mon, Sep 24, 2018 at 11:01 AM, Nikos Chantziaras  wrote:


To me it looks like youtubers and some sites trying to make money through
clickbait?



If you had not heard of it elsewhere the Linux code of conduct was
amended. It makes the CoC similar to those of other projects where
there are a number of (usually nontechnical) contributors who identify
as a champion of social justice.
[...]
Well, if kernel developers are fine with that, then I don't see how 
that's relevant to anyone who isn't a kernel dev. If they want to adopt 
social justice politics, that's really their prerogative.





Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Mick
On Monday, 24 September 2018 08:09:30 BST Andrew Udvare wrote:
> > On 2018-09-24, at 02:47, Adam Carter  wrote:
> > 
> > From:
> > https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome
> > /
> > 
> > "A few weeks ago Google shipped an update to Chrome that fundamentally
> > changes the sign-in experience. From now on, every time you log into a
> > Google property (for example, Gmail), Chrome will automatically sign the
> > browser into your Google account for you. It’ll do this without asking,
> > or even explicitly notifying you. (However, and this is important: Google
> > developers claim this will not actually start synchronizing your data to
> > Google — yet. See further below.)"
> I use the Google features, with many Google accounts including ones I have
> no control of like work accounts. I have many Chrome profiles to avoid the
> confusion that Google is trying to solve with this feature. I wish they
> would solve it in a better way like allowing multiple user accounts open in
> one session complete with multi-account Gmail and others. I can understand
> that other users may not ever figure out to create separate profiles.
> 
> I can understand not wanting this feature but unfortunately Google does not
> believe in options when it comes to Chrome. They are always removing or
> obscuring them. They seem to have a feeling that if there are options (more
> than one good default setting), something is wrong.

Unless I understood this wrong, 'Google Chrome' will not be able to perform 
this (dis)service, unless you have enabled the "Offer to save passwords" 
feature AND|OR you use Chrome to sign in to an Alphabet related website.

If you value your privacy you can leave the "Offer to save passwords" setting 
disabled, or can use a profile where this is not enabled and can also avoid 
ever using Chrome to sign in to any of Alphabet's creations.

Is Chromium also affected by this?


-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: Trouble on the horizon!

2018-09-24 Thread R0b0t1
On Mon, Sep 24, 2018 at 11:01 AM, Nikos Chantziaras  wrote:
>
> To me it looks like youtubers and some sites trying to make money through
> clickbait?
>

If you had not heard of it elsewhere the Linux code of conduct was
amended. It makes the CoC similar to those of other projects where
there are a number of (usually nontechnical) contributors who identify
as a champion of social justice.

The second link is not horrible, but I think is badly formatted. Here
is a picture for you:
https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/croraline-meritocracy.jpg.

The last link is actually very informative. I would recommend reading
it. Some contributors have apparently threatened to revoke the license
to their code which is now in Linux.

My personal opinion is that generally these CoC documents do not do
what they set out to do. Even without a contributor agreement people
can be and are ejected from projects for any reason. However, the
particular entourage that follows these CoCs can be harmful for a
community due to the regularity they find offense with other people.
You find under the "SJW" label people who think a man accused of rape
has no legal rights, etc... So CoC violations tend to devolve into
witchhunts.


My personal experience was that I was not really able to go to school
because of my gender. I am male. I had female classmates with worse
grades than I did that had school completely paid for due to
scholarships. If I tried to say this to some people they would blow up
in my face because of my race and gender, but would claim they are not
racist or sexist.

It is fine to say not everyone is like that, but trying to divorce a
movement from its most vocal subgroups is the
https://en.wikipedia.org/wiki/No_true_Scotsman.

Cheers,
R0b0t1



[gentoo-user] Re: Trouble on the horizon!

2018-09-24 Thread Nikos Chantziaras

On 24/09/2018 10:02, Alan Grimes wrote:

Whatever SJWs touch, DIES.


https://www.youtube.com/watch?v=v5VvJiNUCIA

https://itsfoss.com/linux-code-of-conduct/

https://lulz.com/linux-devs-threaten-killswitch-coc-controversy-1252/


To me it looks like youtubers and some sites trying to make money 
through clickbait?





Re: [gentoo-user] Trouble on the horizon!

2018-09-24 Thread Adam Carter
> Whatever SJWs touch, DIES.


What do you think will be the outcome in this case?

What will die and what be the indicator of death?




>
>
> https://www.youtube.com/watch?v=v5VvJiNUCIA
>
> https://itsfoss.com/linux-code-of-conduct/
>
> https://lulz.com/linux-devs-threaten-killswitch-coc-controversy-1252/
>
>
>
> --
> Please report bounces from this address to a...@numentics.com
>
> Powers are not rights.
>
>
>


Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Andrew Udvare


> On 2018-09-24, at 02:47, Adam Carter  wrote:
> 
> From: 
> https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/
> 
> "A few weeks ago Google shipped an update to Chrome that fundamentally 
> changes the sign-in experience. From now on, every time you log into a Google 
> property (for example, Gmail), Chrome will automatically sign the browser 
> into your Google account for you. It’ll do this without asking, or even 
> explicitly notifying you. (However, and this is important: Google developers 
> claim this will not actually start synchronizing your data to Google — yet. 
> See further below.)"

I use the Google features, with many Google accounts including ones I have no 
control of like work accounts. I have many Chrome profiles to avoid the 
confusion that Google is trying to solve with this feature. I wish they would 
solve it in a better way like allowing multiple user accounts open in one 
session complete with multi-account Gmail and others. I can understand that 
other users may not ever figure out to create separate profiles.

I can understand not wanting this feature but unfortunately Google does not 
believe in options when it comes to Chrome. They are always removing or 
obscuring them. They seem to have a feeling that if there are options (more 
than one good default setting), something is wrong.

-- 
Andrew Udvare


[gentoo-user] Trouble on the horizon!

2018-09-24 Thread Alan Grimes
Whatever SJWs touch, DIES.


https://www.youtube.com/watch?v=v5VvJiNUCIA

https://itsfoss.com/linux-code-of-conduct/

https://lulz.com/linux-devs-threaten-killswitch-coc-controversy-1252/



-- 
Please report bounces from this address to a...@numentics.com

Powers are not rights.




[gentoo-user] OT: Noteworthy change in the way Chrome logs in

2018-09-24 Thread Adam Carter
From:
https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/

"A few weeks ago Google shipped an update to Chrome that fundamentally
changes the sign-in experience. From now on, every time you log into a
Google property (for example, Gmail), Chrome will automatically *sign the
browser into your Google account* for you. It’ll do this without asking, or
even explicitly notifying you. (However, and this is important: Google
developers claim this will not actually start synchronizing your data to
Google — yet. See further below.)"