Boomers have permanently crippled /pol/.
It's threads on the RV are all taken over by boomer Q posting and babies first conspiracy posts.

A lot of people don't understand that Trump & his incoming team didn't face a normal transition period, like it was over a in a matter of a few weeks or months.

The DOJ transition period JUST ENDED when Sessions left. Almost 2 exact years to get it there.

Pompeo at the CIA took over a year before he was done and ready to shift over to the State Department.

All kinds of stuff has been going on behind the scenes nobody leaks or talks about.

We only had the barest mention of the fact the Clinton Email investigation restarted

Nobody leaked in a year that Huber was deep diving into the Clinton Foundation.
Keep that in mind as all the usual suspects continue to INSIST nothing is happening/going to happen.

Rani Chennamma of Kittur was one of the first women rulers of India who fought against the might of the British Empire in 1824. Rani Chennamma was born in 1778 in a small village of Kakati in Belgaon distt of the State of Karnataka.

She was born into the Lingayat Community to a man named Dhulappa Desai. From a very young age she was trained in horse riding,sword fighting, archery and diplomacy. At a very young age of 15 yrs, she was married to the King of Kittur and became the Queen of Kittur.

It is said that King of Kittur Mallasarja was once moving around in the neighbouring kingdoms to find support to fight Tipu Sultan. It is then, when he came across Chennamma and he immediately got attracted to her sheer confidence and bravery.

Rani Chennamma and King Mallasarja had a son together who died very soon after the death of King Mallasarja in 1816. As the Queen of Kittur, Rani Chennamma immediately adopted Shivalingappa as her son and declared him the heir to the throne of Kittur.

This did not go well with the British East India Company who was enforcing the Doctrine of Lapse those days, according to which the adopted children of the Indian rulers were not allowed to become their heirs and if the native rulers did not have children of their own, their...

Gather round, Gentle Readers. It is time I tell the story of the worst decision I ever made in an office. Some of you have heard this. Some have not. Whatever you do in your office today, this week, the rest of this year, you can console yourself by recalling this tale.

A long time ago, I was a talent agent. I worked for a woman named Susan Smith, who had her own small boutique agency. She was known for three things:

1. She had fantastic taste in clients. If there is someone you admire, odds are good that at some point, she was their agent,

2. She could negotiate a deal like few who have ever trod the earth. Casting would give her all the money they had budgeted for that part, plus a little more, plus promising to get her dog Barnaby groomed. She was magnificent to watch.

3. She was insane.

I'm sure you're thinking, "Quinn, it's the entertainment industry, they are all insane." Yes, many are. So consider this; if you told someone you worked for Susan, people who worked for insane people would look and you and whisper, "I hear she's insane."

So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.