FLASH: "Emergency Directive 21-01 calls on all federal civilian agencies to review their networks for indicators of compromise and disconnect or power down SolarWinds Orion products immediately."-@CISAgov Read more:

7 Tactics To Increase Engagement on Your Threads

// THREAD //

People are constantly seeing the same stuff over and over again on their timeline.

This is why you need to learn how to stand out.

When they’re scrolling you need to grab their attention and reel them into something they want to read.

If you think about it, your job is just to get them to click your tweet. Once that’s done, they’ll be reading your other ones in no time.

In order to get them to click you need to show one of these 7 things:
> authority
> experience
> value
> lesson
> mystery
> opinion
> numbers

The easiest way to write headlines based off of these things is to write out your audience’s objections.

Then, indirectly counter their objection within your headline (sounds cool right?).

An old copywriting trick 😉

1. Authority

“Why should I read your thread? What have you done that makes me trust you”

Headline:
“$97,840 in Profit This Month Using This 5-Step Plan to Make Landing Pages”

Authority shows people you know what you’re doing by telling them a true stat/claim.

I did more research into the Parler dump. What probably happened was not so much a "hack", but this: When Twilio/Okta shut them down, they just disabled email/phone verification to create an account. This means anyone could directly create huge amounts of accounts via their API.

Someone also found out that fetching Parler posts could be done by enumerating IDs (e.g 1, 2, 3) instead of random IDs that can't be guessed. Unclear if this was via the ordinary API endpoint, or that they found a separate one by monitoring app network traffic.

So you combine these two things and you can create a script to scrape all the posts on the entire platform, using a lot of different accounts to avoid suspicion. Anyone could download and run this script to spread it out over many IP addresses as well.

What I'm still not sure about is whether deleted (meaning flagged as deleted, it's common that services never actually delete data) posts could be fetched without any special handling.

The verdict: The people who wrote Parler are fucking amateurs.

Company
Permanent suspension of @realDonaldTrump
By Twitter Inc.
Friday, 8 January 2021
After close review of recent Tweets from the @realDonaldTrump account and the context around them — specifically how they are being received and interpreted on and off Twitter —

we have permanently suspended the account due to the risk of further incitement of violence. 

In the context of horrific events this week, we made it clear on Wednesday that additional violations of the Twitter Rules would potentially result in this very course of action.

Our public interest framework exists to enable the public to hear from elected officials and world leaders directly. It is built on a principle that the people have a right to hold power to account in the open. 

However, we made it clear going back years that these accounts are

not above our rules entirely and cannot use Twitter to incite violence, among other things. We will continue to be transparent around our policies and their enforcement. 

The below is a comprehensive analysis of our policy enforcement approach in this case.

Overview

On January 8, 2021, President Donald J. Trump Tweeted:

“The 75,000,000 great American Patriots who voted for me, AMERICA FIRST, and MAKE AMERICA GREAT AGAIN, will have a GIANT VOICE long into the future. They will not be disrespected or treated unfairly in any way, shape or form

I'm going to tell you a little bit how we work on features at GitHub. It's simple, but very powerful in my opinion. At GitHub we have a high performance culture.

We are deploying changes almost all the time while keeping the service running and the deployment failure ratio needs to be super low! We are constantly working on new medium/big features, we have frequent deploys and required peer reviews.

How do we know that big features are not conflicting with each other in functionality and in version control. How do we merge the work done in these non-trivial features? How do we do prevent peer reviews slow down our productivity?

With basically two things: split the work in small batches and feature flags. We don't have long-lived feature branches. We do very small changes all the time and deploy them.

We could split a feature in tens or hundreds of PRs, but until it is beta or GA, we don't expose it to users by using feature flags.