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.
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.
π οΈ π οΈ #Avalanche Cortina 10 is out: github.com/ava-labs/avalanchego/releases/tag/v1.10.10 π οΈ π οΈ
This version (v1.10.10) is backwards compatible to v1.10.0. It is optional but recommended.
π Release Focus: Pull-Based C-Chain Gossip + ProposerVM Block Pruning + MerkleDB Split Intermediate/Value Nodes
β Compatibility Check: VM Interface (v28) β
Cortina 10 does NOT modify the VM interface. If you are running a Custom VM on v1.10.9, it will work with v1.10.10.
Pull-Based C-Chain Gossip (cont.)
@joshuagkim researched the effectiveness of this approach and showed via simulations that propagation slows down exponentially as txs are "absorbed", leading to longer than expected e2e finalization latency.
github.com/ava-labs/coreth/pull/266
Pull-Based C-Chain Gossip (cont.)
Thus far, this change has only been applied to the C-Chain but will be ported to the X/P/Subnet-EVM (using the P2P SDK).
HyperSDK, however, uses a different gossip algo (doesn't have a long-lived mempool) and won't adopt this work.
ProposerVM Block Pruning
High-throughput blockchains produce a LOT of data. For example, a chain with 25k TPS (where each tx is ~400 bytes) will store 10MB/second -> 864GB/day -> 315TB/year of JUST block data.
Turns out operators don't want to manage this much data π.
ProposerVM Block Pruning (cont.)
Starting in Cortina 10, Custom VMs can control how much historical block data they want to keep (defaults to all blocks).
github.com/ava-labs/avalanchego/pull/1929
WARNING: If all nodes on a Subnet delete old blocks, new nodes will only be able to state sync.
ProposerVM Block Pruning (cont.)
The HyperSDK (which runs at a high target throughput and only supports state sync), however, defaults to only storing 768 of recently accepted blocks.
github.com/ava-labs/hypersdk/pull/436
MerkleDB Split Intermediate/Value Nodes
The work to productionize MerkleDB continues full force in Cortina 10 (20 related PRs merged). The most significant of these improvements is storing intermediate and value nodes in separate database prefixes.
github.com/ava-labs/avalanchego/pull/1918
MerkleDB Split Intermediate/Value Nodes (cont.)
When all nodes are stored in the same database, generating range/change proofs requires TONS of useless disk IO (you will read intermediate nodes from disk when you just want value nodes).
This change removes this overhead.
MerkleDB Split Intermediate/Value Nodes (cont.)
This PR also unblocks the ability to store keys in a more compressed format and provides much more granular control over caches used to store nodes (can make the intermediate cache much larger than the value cache).
(Bonus) Gracefully Exit RPCChainVM
The default behavior of systemd is to send a SIGTERM to the entire process group (AvalancheGo + Custom VMs), which can cause Custom VMs to shut down before AvalancheGo triggers a clean shutdown (also uses SIGTERM).
freedesktop.org/software/systemd/man/systemd.kill.html
(Bonus) Gracefully Exit RPCChainVM (cont.)
Instead of shipping a custom systemd configuration, @stephenbuttolph introduced a PR that modifies the VM signal handler to only listen for a SIGTERM after AvalancheGo has initiated graceful shutdown flow.
github.com/ava-labs/avalanchego/pull/1988