Craft and publish engaging content in an app built for creators.
NEW
Publish anywhere
Post on LinkedIn & Mastodon too. More platforms coming soon.
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
150,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.
With the recent announcement of @delegatecash, I noticed some misunderstanding of what this implementation achieves versus the @CyberKongz Guardian and @0xQuit's Guardian
Let me explain each of these implementations and why I think they're essential to the future of Web3 ๐งต๐๐ป
Firstly, let's begin with the trailblazer @OwlOfMoistness and his @CyberKongz Guardian contract.
This implementation allows a user to keep an asset in one address, while assigning another address as a Guardian.
While this Guardian address is set and the asset is locked, the asset cannot be transferred. Even if a bad actor has your seed phrase, or you've signed a token approval.
This implementation allows you to safely use your asset on a "hot" wallet while mitigating risk. Big win.
One of my favourite parts is that even when assets are locked, there is an Emergency Transfer button that allows you to initiate a transfer FROM the Guardian address.
This is important because it mitigates the risk of having to race the bad actor's transactions.
Usually with a seed phrase compromise a bad actor uses a sweeping bot that sends all ETH out from the address as soon as it's received.
This leaves people in situations where they are unable to retrieve staked assets, claim drops etc.
Emergency Transfer is initiated FROM THE GUARDIAN ADDRESS not the compromised address, so no need to race the bad actors transactions!
Pros:
-Locks any transfer of asset, unless unlocked or from Guardian
-Mitigates seed phrase compromise, token approval, and transfer phishing
Cons:
-Requires unlocking of asset to sell/transfer
-Asset loss if Guardian keys are lost
This is great for those who use a hardware wallet and are less likely to experience seed phrase compromise, and for assets that don't require "hot" wallet usage.
It allows you to first set token approvals that you might want (OS, LooksRare etc.) and then lock future approvals.
When you call the lockApprovals function, you parse a "Guardian" address which is necessary when you want to eventually unlock approvals.
Only this Guardian address is able to revoke the lock on token approvals. However, you can still transfer the asset like normal.
Pros:
-Focus on most likely threat - token approvals
-Can list without removing control
-Can still transfer asset if Guardian keys are lost
Cons:
-Does not mitigate against seed phrase compromise
-Does not mitigate transfer phishing
And lastly, the newest kid on the block - @delegatecash.
While the other two focused specifically on asset security, this new implementation focuses on safe delegation of ownership, which inherently increases security posture.
The intention is to allow someone to hold an asset in a cold wallet, while simultaneously being able to prove that they own said asset via a hot wallet, while the hot wallet has ZERO control over said asset.
This allows on-chain provable ownership without having to expose your valuable private keys or assets or use a centralised platform
Examples where this is beneficial include claiming NFT airdrops, claiming yield from a staking contract, attending in-person token-gated events etc
All of these examples stemmed from the same risk, and this risk was one of the largest hurdles to a future of Web3 becoming mainstream.
As you can see, all three of these implementations mitigate different risks and they are all incredibly important in moving the space forward.
Massive thanks to everyone involved in all of these tools! We owe you much wei and many CDBs.