Thread – Dump the Legacy Media; Turn to These News Sources

A. We all need sources less tainted by the Big Tech/globalist narratives that are echoed repeatedly throughout the legacy media. My brother sent me a list of alternatives from the Noq report.

Thread – Observations on the Past and Future

1. The following commentary received from a friend mirrors my own remembrances and thinking exactly. There are more of us than there are of them! Here is what he had to say.

Thread – Possible American Dystopias in 2021

1. Dystopia: an imagined place or state in which everything is unpleasant or bad, typically a totalitarian or environmentally degraded one.

2. I read an article the other day that predicted future dystopian possibilities in the US given all that we have seen and what has transpired in 2020. Talk about thought-provoking and frightening! Here are some excerpts.

3.

The general election of 2020 will be the stuff of argument and analysis for many years to come, here and abroad.

3A. Suffice to say here that a panicky over-reaction to the onset of the COVID-19 virus produced economic hardship and social disorder, compounded by months of riots, looting and arson afflicting hundreds of cities (almost all Democrat-governed) beginning in late May 2020.

3B. All of this set the stage for an election won overwhelmingly on November 3rd by President Donald Trump and lost by him in the following weeks to his Democrat opponent.

Thread – Questions from the Net for Democrats

1. Now that a false flag operation at the Capitol building provided cover for the Uniparty to certify The Hologram as the “winner” of the stolen election, an enterprising soul has some questions for the Left.

Thread – A Very Strange Christmas Indeed!

1. Went to a Missouri Synod Lutheran Christmas Eve service tonight, as we visited our daughter in Billings. The sermon was great; I will attempt to give the message justice.

2. This has been a strange Christmas for many people, if not most or all. No advent services, no Christmas parades, no office parties, no jumping from party to party on Christmas Eve. Fearmongering by the Democrat-media complex that minimizes attendance.

3. Social distancing and the wearing of masks in church. Human to human contact minimized. And so forth and so on. It just doesn’t feel like Christmas this year.

4. Yes, this Christmas has been strange. But then think about how strange the very first Christmas was. Here is the Christmas story from the Bible (Luke and Isaiah):

5. In the beginning was the Word, and the Word was with God, and the Word was God. He was in the beginning with God. All things were made through Him, and without Him was not any thing made that was made. In Him was life, and the life was the light of men.

Thread – A Survey of the Current Situation

1. The media (99%), the FBI, and the Justice Department, and most judges in federal judiciary seem fully complicit in protecting those guilty of the most massive corruption and sedition in American history.

Just published 15,000+ words on security keys. 🔐📱💻

With SIM attacks at their highest, now is a great time to take a closer look at your online security.

Removing SMS from your two-factor auth is a start, but authenticator apps have downsides too...

https://t.co/Dk0MPJHL2V

Just look at these headlines from recent SIM swap and port attacks.

It's all too established for attackers to find ways to socially engineer control of your phone number and start gaining control of your accounts.

I first talk about some general security tips.

Unfortunately not all websites let you remove your phone number from accounts.

You may consider migrating your phone carrier to @googlefi , which requires email account access to do anything (and can be locked down with security keys and even Advanced Protection)

Beyond SMS, I talk about issues that TOTP authenticator apps (the code generators) have as a form of two-factor auth. They're so, so much better than relying on SMS for your second factor but they still have issues like utilizing shared secrets and lacking phishing prevention.

Enter security keys!

Utilizing public key cryptography they don't have any shared secret between the client and the server. They prevent phishing by taking the website domain into account.

Even if you get tricked by a clone phishing website, your key won't.

Why did I leave Google? A thread.

This thread is going to include quotes from Wired's "Three Years of Misery Inside Google, the Happiest Company in Tech" because I'm not a professional writer

When I joined Google, I fell in love with the company immediately. I was excited to come to work, not just for the technical challenges, but because I really felt I was making a difference and working for the good guys.

I spent 20% of my week working on an app that helped people find lost loved ones after natural disasters. I spent more free time speaking to students about technology and diversity. For an entire school year, I taught CS classes twice a week at a local low income high school.

The company was open. We had a weekly meeting called TGIF where anyone in the company could ask questions of, and raise concerns with, the execs. We got real answers.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.

argh chrome updated and it seems they've intentionally broken custom search engines. I have had a keyword search for "foone" which searches my own twitter, so I just type "foone BLAH" and it gives me a twitter search for when I said BLAH, right?

but now I get that option in the titlebar of "search twitter self-search" which is the name of the search"
if I just type "foone blah" now...

it ignores the search I have had defined for years and just googles it.

and this is definitely on purpose because they didn't just break it, they changed it. it's now "fooneblah"

there doesn't seem to be an option to make this stop and get the old behavior back :(

The vast majority of images are jpegs, which are internally 420 YUV, but they get converted to 32 bit RGB for use in apps. Using native YUV formats would save half the memory and rendering bandwidth, speed loading, and provide a tiny quality improvement. It would also be \

a good path to supporting better video codec still image formats and 10 bit components. You can do it today, but you need to do the color conversion manually in a shader, which can be a big ask for some devs. Defining a FMT_JPEG_YUV that does driver injection akin to the \

external image support on Android could make it much more of a drop-in. Even doing it the hard way seems like it would be worthwhile for web browsers today.