it's done.

a visual enigma machine simulator: https://t.co/eLE4Sb97HW

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.

We’ve recently seen research about so-called “bots” and misinformation on Twitter and wanted to share our perspective on why findings that might seem remarkable at first are likely inaccurate. We’re working on a more detailed explanation, but some comments for now.

We continue to be excited by the research opportunities that Twitter data provides. Our service is the largest source of real-time social media data, and we make this data available to the public for free through our public API. No other major service does this.

Many researchers, academics, and journalists use our public API — a set of tools for programmatically accessing information on Twitter. We make all public Twitter content available via our APIs. You can learn more about them here:

The basic issue with much of the research based on our public APIs is simple: The APIs don't provide insight into our defensive actions to protect Twitter from manipulation, including bots.

Because of this, API-based research can't distinguish between accounts we've already identified as bad (and hidden or removed) and real, authentic ones.

“Why are Tumblr and Facebook cracking down on sex so much? And why is Facebook in so over zealous about it? It’s all Apples fault!” Etc etc

I can explain all. It is largely the fault of a set of US laws called SESTA and FOSTA.

When you complain about an open source project's management you'll get the reply, "Use something else if you don't like it!" That'd be true except for the tiny problem that *many* projects also strive for complete monopolistic dominance.

Let me tell you about Java in early 2k:

I was programming in Java since it's release, and all through the late 90s into the early 2000s. At first Java was very determined to unseat C++ and it used various propaganda tactics to turn C++ and malloc into a weird enemy for all of us to hate. This worked great!

Everything was fine though because there were plenty of jobs in tech because of the dot-com boom, and then suddenly there were not jobs because of the dot-com bomb.

Overnight it seemed as if the *only* way to get a job was at giant companies, and they *loved* Enterprise Java.

Now, this is the golden ticket for many open source projects and corporations. They all want to be the top dog #1 in the industry for their particular use, and once they gain that position they become abusive by ignoring user needs and extracting wealth from them.

With Java the dominance was so insane that *every* language had to copy Java's weirdness to survive. If you wonder why a language has some odd CamelCase things it's because early Python, Ruby, and others had to copy Java's semantics and style to even be considered "serious".

Following up last year’s surprisingly popular "10 things you likely didn’t know about Darkroom" and your many requests for more tips, we put together a second edition that focuses on workflows in Darkroom. Click through to read it all right here in this thread.

1/10 Copy & Paste your Edits in Batch. Skip the hassles of re-applying each edit over and over again by copying your edits from the tap-and-hold library menu, History tool, or the Actions (•••) menu. Go to your other photos, and paste your edits onto them.

2/10 The joy of seeing your wonderful shot in motion is why we love Live Photos so much, and why we fully support editing and exporting them! While editing, Tap the “LIVE” button at the left top when viewing a Live Photo for playback.

3/10 Turn your iPhone to landscape for an iPad like editing experience, bringing some iPad exclusive functionality to iPhone. In the library grid we show the Library Sidebar, when viewing or editing we show the Photo Strip, and in the color tool we show our Color Histogram.

4/10 Manage while editing with the Photostrip. With the photo strip available on all devices in landscape orientation, you can skip & hop through your library while editing, or quickly compare multiple photos to find the one with the perfect expression or the perfect light.