Built for 𝕏∙LinkedIn∙Bluesky∙Threads. Powered by AI
Write & schedule, effortlessly
Craft and publish engaging content in an app built for creators.
NEW
Publish anywhere
Publish on X, LinkedIn, Bluesky, Threads, & Mastodon at the same time.
Make it punchier 👊
Typefully
@typefully
We're launching a Command Bar today with great commands and features.
AI ideas and rewrites
Get suggestions, tweet ideas, and rewrites powered by AI.
Turn your tweets & threads into a social blog
Give your content new life with our beautiful, sharable pages. Make it go viral on other platforms too.
+14
Followers
Powerful analytics to grow faster
Easily track your engagement analytics to improve your content and grow faster.
Build in public
Share a recent learning with your followers.
Create engagement
Pose a thought-provoking question.
Never run out of ideas
Get prompts and ideas whenever you write - with examples of popular tweets.
@aaditsh
I think this thread hook could be improved.
@frankdilo
On it 🔥
Share drafts & leave comments
Write with your teammates and get feedback with comments.
NEW
Easlo
@heyeaslo
Reply with "Notion" to get early access to my new template.
Jaga
@kandros5591
Notion 🙏
DM Sent
Create giveaways with Auto-DMs
Send DMs automatically based on engagement with your tweets.
And much more:
Auto-Split Text in Posts
Thread Finisher
Tweet Numbering
Pin Drafts
Connect Multiple Accounts
Automatic Backups
Dark Mode
Keyboard Shortcuts
Creators love Typefully
180,000+ creators and teams chose Typefully to curate their Twitter presence.
Marc Köhlbrugge@marckohlbrugge
Tweeting more with @typefully these days.
🙈 Distraction-free
✍️ Write-only Twitter
🧵 Effortless threads
📈 Actionable metrics
I recommend giving it a shot.
Jurre Houtkamp@jurrehoutkamp
Typefully is fantastic and way too cheap for what you get.
We’ve tried many alternatives at @framer but nothing beats it. If you’re still tweeting from Twitter you’re wasting time.
DHH@dhh
This is my new go-to writing environment for Twitter threads.
They've built something wonderfully simple and distraction free with Typefully 😍
Santiago@svpino
For 24 months, I tried almost a dozen Twitter scheduling tools.
Then I found @typefully, and I've been using it for seven months straight.
When it comes down to the experience of scheduling and long-form content writing, Typefully is in a league of its own.
Luca Rossi ꩜@lucaronin
After trying literally all the major Twitter scheduling tools, I settled with @typefully.
Killer feature to me is the native image editor — unique and super useful 🙏
Visual Theory@visualtheory_
Really impressed by the way @typefully has simplified my Twitter writing + scheduling/publishing experience.
Beautiful user experience.
0 friction.
Simplicity is the ultimate sophistication.
Queue your content in seconds
Write, schedule and boost your tweets - with no need for extra apps.
Schedule with one click
Queue your post with a single click - or pick a time manually.
Pick the perfect time
Time each post to perfection with Typefully's performance analytics.
Boost your content
Retweet and plug your posts for automated engagement.
Start creating a content queue.
Write once, publish everywhere
We natively support multiple platforms, so that you can expand your reach easily.
Check the analytics that matter
Build your audience with insights that make sense.
Writing prompts & personalized post ideas
Break through writer's block with great ideas and suggestions.
Never run out of ideas
Enjoy daily prompts and ideas to inspire your writing.
Use AI for personalized suggestions
Get inspiration from ideas based on your own past tweets.
Flick through topics
Or skim through curated collections of trending tweets for each topic.
Write, edit, and track tweets together
Write and publish with your teammates and friends.
Share your drafts
Brainstorm and bounce ideas with your teammates.
NEW
@aaditsh
I think this thread hook could be improved.
@frankdilo
On it 🔥
Add comments
Get feedback from coworkers before you hit publish.
Read, Write, Publish
Read, WriteRead
Control user access
Decide who can view, edit, or publish your drafts.
This thread covers a key Dec 2022 report by the House Intelligence Committee, which aimed to review the Intelligence Community's response to the COVID-19 outbreak:
That report illustrates the role of the Director of National Intelligence at the time.
intelligence.house.gov/news/documentsingle.aspx?DocumentID=1225
But before I dig into it, let me set the expectations right:
👉🏼That report is not about the origins of Covid-19.
It is first about the work of the Intel Community (IC) 'once' the outbreak was public at end December 2019.
The origins question is touched on only indirectly.
Then it is about the use of the Trump administration of the intel it was presented with, especially via the President's Daily Briefs.
This, in theory at least, to highlight "where responsibility for our poor outcomes lie, and where it does not".
Please note that the House Intelligence Committee did not have full access at all.
As a result, their report is at times rather superficial and sometimes a bit 'guided' by whatever was disclosed to them.
Both the Biden and the Trump administrations did not fully cooperate.
In particular the President's Daily Briefs were out of reach.
These are high level all-source intel pieces that make it to the President desk.
They form a crucial product of the Intel Community (for good or bad - there is an intel debate about it).
intelligence.gov/publics-daily-brief/presidents-daily-brief
Done with the introduction. Let's jump to the interesting bits:
1️⃣ There is one major piece of information related to the origins that the report tries hard to downplay:
One IC element revised its origin assessment after the publication of the Biden report (Oct 2021).
🔎🦠
We only learn about this in a convoluted and redacted footnote 46.
The main text itself only tells us that the conclusions of the Intelligence are unchanged since the publication of that Biden report.
Footnote 46 tries to walk a tightrope by stating that:
- There was no coordinated effort to revise the Biden intel assessment, despite at least one IC element deciding to update its own contribution.
@dasher8090@RandPaul@RogerMarshallMD
But in fact ODNI should have coordinated it, as soon as DEFUSE and the FOIs were released.
In other words the ODNI / NIC sat on that IC element's reassessment and certainly did not invite other IC elements to confirm/review their own assessments based on recent key info.
Footnote 46 then tries to dress this lone reassessment as a 'healthy culture of objective analysis following the facts where they lead'.
Yet, nothing was done by the NIC (National Intelligence Council) or the ODNI to trigger an IC-wide re-assessment.
It's a bit rich. 🤡
And the footnote then goes on, diluting the meaning of any assessment of the origins.
Basically:
1. The Trump administration messed up anyway,
2. And whatever happened in fall 2019 - lab accident or zoonosis - is irrelevant.
,,, because, allegedly, the US should not act any differently if it was a research accident. Makes no difference (really??).
Seriously, I had to read that footnote many times.
It's a masterpiece of convoluted logic trying to drive us away from the key issues it raises.
That odd logic refers to the redacted part of footnote 46, which details the update of that IC element.
What this tries to say is that in the context of this committee report, which is not about the origins, an update of the Biden intel report does not matter.
Move on.
So moving on to the next pearl.
2️⃣ The report has a disingenuous section about the intel on several WIV workers falling ill in fall 2019.
[Intel likely based on routine hacking of Electronic Patient Records, on which the IC sat for ages before noticing the significance.]
This goes back to the State Dep fact sheet issued in the last few days of the Trump administration that stated that several researchers became sick in autumn 2019 'with symptoms consistent with BOTH Covid-19 and common seasonal illnesses'.
The factsheet was rather careful:
The House Intel Committee report spins this, plus subsequent remarks by Pompeo and a minority report, as being 'deeply' misleading.
I am not so sure. The minority report clearly says 'may have been' and does not wander much from the careful wording of the fact sheet.
The worst is that the House Committee report essentially paraphrases the State Dep fact sheet, in order to explain why this is misleading.
In the end, it seems to me that the point of contention for the House Intelligence Committee is that any statement mentioning the sick WIV workers is 'misleading' because the intel is not a diagnosis of COVID-19.
Which makes zero sense.
There was obviously no definite diagnosis of COVID-19 back in Nov 2019.
There was no recognized new disease, nothing called Covid-19, no RT-PCR test, no agreed symptoms, no sequence to match, basically nothing to hang a clear COVID-19 diagnosis on based on medical records.
But the best you could get is actually what the intel got: symptoms retrospectively matching COVID-19.
My understanding is that the hacked Electronic Patient Records were gold standard, with CT-scans compatible with COVID-19.
The task for the analysts is then to evaluate this against alternative diagnoses, in context.
- What were the patients' ages and previous medical conditions?
- What do their scans show?
- What is the chance of a simple seasonal illness across the 3?
But the House Intelligence Committee report spends a lot of time describing how good a job NCMI did, starting on 31 Dec 2019.
Nothing about its earlier work until a box on page 31:
... likely emergency health situation in Wuhan in early Nov 19, with a signal so strong that the Defense Intelligence Agency (DIA, from which it depends on) is said to have alerted NATO and the IDF at end Nov 2019.
mako.co.il/news-military/2020_q2/Article-27a575c46148171027.htm
Note that from the point of view of senior US administration figures, the distinction between raw and finished intel is essential, for a very simple reason:
They cannot so easily be blamed for not reacting to raw intel from one lone agency.
Especially one siloed like NCMI.
They can indeed always say that it was vague and partial.
But they have to take responsibility if they failed to act on an alert in the form of an all-source intel product.
There is a huge difference between the two. Hence, they keep making the distinction.
So if one wants to check what intel was being produced by NCMI at the time, one needs to check the situation reports during Nov 2019 and the DIA exchanges with key foreign military partners at end Nov.
The finished all-source intel products were produced only later.
As surprising as it may sound, there is indeed a NCMI/DIA silo within the IC.
Which meant that NCMI/DIA intel - as crucial as it was - did not have the same reach as if it had been pushed by the NSA or the CIA.
This is actually very much alluded to in the report:
Clearly still putting the lid on it.
In this case, mentioning signs of a Nov outbreak would not play well with the market jump stories of Science, based on 155 blurry points on a distorted map for cases, 100 of these at most confirmed.
Stories already in tatters following the confirmation via peer-reviewed papers of 247 to 260 cases in the official database at end Feb 2020, just after a gag order, with at least 165 confirmed and the rest diagnosed.
So much for the Science papers.
twitter.com/gdemaneuf/status/1596247403782230016?s=20&t=S0Ye5tb_oO1w1mczguyXZQ
A last point before I wrap this up:
4️⃣ There are some rather unnecessary redactions.
For instance see the one below, which takes two seconds to fill in (it's intel 101).
What's the point of it?
bit.ly/HSPCI_Gaps
Maybe the point is precisely that it links to the way NCMI detected an emergency health situation of some sort in Wuhan in early Nov 2019.
Something that this House Intelligence Committee report tries very hard not to dig into.
Another unnecessary redaction has to do with the Consulate General Wuhan holding an Emergency Action Committee meeting on 31 Dec 2019 to discuss reports of an outbreak of respiratory disease.