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.
๐ ๏ธ ๐ ๏ธ #Avalanche Cortina 12 is out: github.com/ava-labs/avalanchego/releases/tag/v1.10.12 ๐ ๏ธ ๐ ๏ธ
This version (v1.10.12) is backwards compatible to v1.10.0. It is optional but recommended.
๐ Release Focus: Height Voting for Chits + Dual-Alpha Support (Not Enabled) + Configurable MerkleDB Branch Factor
โ Compatibility Check: VM Interface (v28) โ
Cortina 12 does NOT modify the VM interface. If you are running a Custom VM on v1.10.9-v1.10.11, it will work with v1.10.12.
Height Voting for Chits
Cortina 12 introduces a RequestedHeight field to *Query messages and a PreferredIDByHeight field to Chits messages.
This consensus optimization converts vote bubbling from a liveness requirement to a performance optimization.
github.com/ava-labs/avalanchego/pull/2102
Height Voting for Chits (cont.)
When a node issues a query, it now also requests the query recipient's preference of its last accepted block height + 1.
When a virtuous node responds, the requesting node can fall back to applying the vote on top of its last accepted block.
Dual-Alpha Support (cont.)
Recall, a "poll" for a container in Avalanche+Snowman Consensus is successful if "alpha"/"k" responses are for a single containerID.
If nodes run "beta" consecutive successful polls for the same containerID, they will accept the container.
Dual-Alpha Support (cont.)
Nodes will "vote" with their preferred containerID, as measured by the number of successful polls they've ever seen for that containerID (if they've seen 4 successful polls for "A" and 3 successful polls for "B", they'll vote "A").
Dual-Alpha Support (cont.)
When the network is split ~50/50 between 2 containers, however, it can take rounds >> beta for the network to begin preferring a single color because nodes must start to get "alpha"/"k" polls for a single container to change their preference.
Dual-Alpha Support (cont.)
This optimization separates what "alpha" is used to be considered a successful "poll" for setting preference (AlphaPreference) vs the "alpha" used for finalizing a container (AlphaConfidence).
Specifically, the change to the spec looks like this:
Dual-Alpha Support (cont.)
The likelihood of performing a successful poll for AlphaPreference/k is much higher than AlphaConfidence/k (traditional alpha) when close to a 50/50 split.
This causes the network to "avalanche" to a single container quicker -> finalizing faster.
Dual-Alpha Support (cont.)
In practice, a ~50/50 split (or even having multiple containers to vote on at once) is pretty rare because of the randomness of block propagation (nodes set their initial preference to the first valid block they see) and because of Snowman++.
Dual-Alpha Support (cont.)
However, this change could come in handy if there is unusual network instability (if there are cross-region connectivity issues or some set of data centers go down) and there are many conflicting containers that could be accepted.
Dual-Alpha Support (cont.)
We are working with researchers (internal+external) to publish a proof that demonstrates that this change does not significantly impact the safety of consensus before enabling in AvalancheGo.
@stephenbuttolph shared his initial thoughts here:
Configurable MerkleDB Branch Factor
The MerkleDB now allows callers to choose a branching factor of 2, 4, 16, or 256.
This allows devs to tune MerkleDB to their workload (i.e. if proof size is important, use branch factor 2).
github.com/ava-labs/avalanchego/pull/2010
[Bonus] MerkleDB Path Prefetching
To improve the "real world" performance of the MerkleDB, devs can now trigger concurrent prefetching+caching of intermediate nodes on the paths of changed keys before starting root generation.
github.com/ava-labs/avalanchego/pull/2128
[Bonus] Warp Message Codification
Last but certainly not least, Cortina 12 codifies 2 Avalanche Warp Messaging payload formats that will be used in Teleporter (C-Chain <> EVM Subnets + EVM Subnet <> EVM Subnet communications).
github.com/ava-labs/avalanchego/pull/2116
[Bonus] Warp Message Codification (cont.)
While we expect most Teleporter users to use "Payload.AddressedCall" at first, we predict that most comms over AWM will eventually transition to using "Payload.Hash" (batches of messages proved with a single BLS Multi-Signature).