Built for š, LinkedIn, and Threads, powered by AI
Write & schedule, effortlessly
Craft and publish engaging content in an app built for creators.
NEW
Publish anywhere
Post on LinkedIn, Threads, & Mastodon at the same time, in one click.
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
170,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.
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.
An insane story of code being used as a weapon
A huge project just pushed out a new version that wipes your hard drive if your IP is from Belarus/Russia
This project is downloaded 1 Million+ times a week
It's now a NATIONAL security issue ranked 9.8/10 in severity
The story:
This project is what's known as a "package"
This means when nerds like me want to write complicated code, we start by downloading someone else's code to save time
The problem? Most of the time, this is done _automatically_
So overnight, 30k+ downloads happened instantly
This is so dangerous, it's now listed in the National Vulnerability Database: nvd.nist.gov/vuln/detail/CVE-2022-23812
The code in question is node-ipc: npmjs.com/package/node-ipc
Let's just say it's really important code for a lot of software
But let's explain the new, bad code in English:
Step 1: Check your IP
Step 2: Grab all the root folders on your computers (everything on your PC is stored on /)
Step 3: if you're in Russia or Belarus, delete everything.
That's literally it.
It doesn't take complicated code or a genius to do something extremely dangerous like this.
The author of the scary code defended himself here when he was called out by a user of the package (code)
You'll notice you can only see the author's comments, as the author has deleted a lot of what others were saying
This will do more than delete data
github.com/RIAEvangelist/node-ipc/issues/233
The danger here is not just to people that have downloaded the scary code, but the message this sends
So much of software in 2022 is built by using other people's code to save you time
If you can't trust other people's code...
We're in trouble
Not just now, but in the future
For a long time, this has been a concern for many.
In fact, even programs that run your code (compilers) have had scary code in them
Imagine if Google Docs saved any passwords you typed into a doc?
That's the kind of danger we're talking about today
win.tue.nl/~aeb/linux/hh/thompson/trust.html
There's not much we can do to fix this problem on a large scale
It's existed for a long time, and will continue to be a danger
We build great code on the shoulders of old great code
But the foundation can always fall, and it might take a lot with it
But for now, do this:
First, if you're using vue-cli, you're at risk
Check your version and version-lock to the newest version that fixes this issue for at least vue users
ESPECIALLY if you made a new project recently
Scroll to "How to mitigate the node-ipc issue" here:
snyk.io/blog/peacenotwar-malicious-npm-node-ipc-package-vulnerability/
Beyond that, check your dependencies, across all your projects.
If node-ipc is in there, version-lock to something safe.
Even if you're not in Russia, two changed lines of code in the next version could ruin your servers or worse.
Beyond that...
Just be careful what you npm i
Obviously I'm not in Russia, but a lot of our friends are
Share this thread around, many still don't know and are in danger of bricked computers in a time of warfare
Regardless of what "side" of this you're on, software shouldn't be a weapon
Not like this.