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.
some folks read my thread yesterday and concluded "patrick isn't pursuing single-chain scaling ... he believes low-throughput primary network + many subnets are the only way"
i wanted to take some time to clarify my position (as it is meaningfully different)
twitter.com/_patrickogrady/status/1736489913326170277?s=20
capacity is key to making PIV accessible because it dramatically increases the aggregate fee payment required for transaction fees to stay at a certain level
if capacity increases 10x, actors pay ~10x aggregate fees to keep fees unchanged (all else equal)
at the limit, i do believe interconnected, multi-chain capacity is a key part of making PIV accessible (scaling blockchains to world-scale)
however, there are clear benefits/practical considerations for a community to operate over a single, high-throughput state space
belief in the former (horizontal, heterogenous scaling to reach massive usage) does not justify not focusing on optimizing the performance of a single chain
native interconnectivity and chain capacity play off each other and more of one shouldn't be substituted for the other
for the last ~1.5 years, i've spent the vast majority of my time on productionizing the hypersdk to bring massive single-chain capacity to avalanche
the hypersdk serves as a testbed for the primary network (x/p/c) and leveraging its "greatest hits" will help scale it
twitter.com/_patrickogrady/status/1628109791267819520
the hypersdk's main focus is on:
1) increasing underlying capacity via decoupled SMR
2) managing increased capacity using multi-dimensional fees (MDF)
in the remainder of this thread, i'll share my thoughts around (2) and then will follow-up with specifics around (1) [see qt]
twitter.com/_patrickogrady/status/1736489929797157216?s=20
increasing the "block resource limit" can increase the capacity for storing more data in blocks but also opens the door to using that extra capacity for interacting more with **all** defined vm operations
for example, limit A may allow for 2MB of block data and limit B (2*A) may allow for 4MB of block data
limit A may allow for 100 state writes and limit B may allow for 200 state writes
alternatively, one could instead modify the relative cost of different opcodes (like allowing data inclusion to be 0.5x or even 0.01x as expensive) while keeping the "block limit" the same
this would lower the cost for this action but also increase the max usage of a resource
the inherent tension here is that single unit resource accounting forces fee designers to come up with some relationship between unrelated resources (like bandwidth and RAM) and to enforce limits based on the most constrained resource (usually state addition)
the hypersdk (and this vm-agnostic mechanism more broadly) allows usage across different dimensions to be metered and limited independently to avoid opening a dos for one resource while increasing the capacity of another
twitter.com/_patrickogrady/status/1694011879931449419
increasing capacity and the general work of optimization is never "complete" (not that i'm the first to say it lol)
i plan to continue writing about this research (especially when new information changes my mind), if you'd like to contribute hop in here: github.com/ava-labs/hypersdk
[bonus] some of the thoughts that inspired the forthcoming thread on decoupled SMR are here (finally figured out the edge cases around preventing unexecutable transaction spam):
twitter.com/_patrickogrady/status/1673372491333640192