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.
At 6:42:29 AM UTC (1:42:29 AM ET) this morning, December 22nd, 2022, the first native Cross-Subnet Message was sent on #Avalanche Mainnet using **Avalanche Warp Messaging**.
1/ Avalanche Warp Messaging (AWM) is the Native #Avalanche Subnet-to-Subnet communication protocol that allows ANY 2 blockchains running on different Subnets to send/verify arbitrary messages to/from each other.
2/ While AWM is now live as of Banff 5 (AvalancheGo@v1.9.5), the foundations for this new mechanism were being laid since the launch of #Avalanche Mainnet.
3/ It all starts with the #Avalanche design. Since the launch of the network, all validators have had to validate the Primary Network AND all Subnets they are participating in.
This is VERY important because the P-Chain (in the Primary Network) contains all Subnet staking info.
4/ Between AvalancheGo@v1.3-1.8, the P-Chain was rewritten and optimized a number of times to enable the efficient storage and lookup of staking info about any Subnet or Avalanche Validator on demand.
6/ Banff 1-4 added a number of tweaks to the P-Chain and VM interfaces to make it possible for any Subnet running on #Avalanche to access the staking info and BLS Public Keys associated with any Subnet.
(check out my previous tweets for a full accounting of this progress š¤)
7/ Banff 5 adds the final pieces to the VM Interface to make native Cross-Subnet messaging possible:
1) BLS Signature Generation via gRPC interface (so that BLS secret key is not exposed to any VM)
2) BLS Multi-Signature Verification using stake weights
8/ So how does this all work?
Lucky for you, I crafted šØ this simple diagram to explain how AWMs are generated and verified:
9/ First, any #Avalanche Validator that wants to generate BLS signatures must register their BLS Public Key and BLS Proof-of-Possession on the P-Chain when starting their staking period.
This BLS key is recorded in the P-Chain database so that any VM can quickly query its value.
10/ Next, that validator must join a Subnet (or Elastic Subnet) of their own creation or one that already exists.
(yes, AWM works for both Subnets AND Elastic Subnets š )
11/ At any point, the VM running on the Subnet can trigger the generation of a BLS signature over an arbitrary payload.
It is up to the VM to determine both the fee on the blockchain for triggering a generation and for determining what to put in this payload (any byte array).
12/ Once each validator has generated a BLS signature over the payload, anyone wishing to broadcast the message to another Subnet can collect the validator signatures and form a BLS Multi-Signature that can be processed by any other #Avalanche Subnet.
(more on this later)
13/ Now for the fun part.
It is up to each Subnet to determine if it wants to accept messages from another Subnet and, if so, how much stake must have signed a message for it to be considered valid and/or safe.
TL;DR each Subnet defines its own AWM security level. š
14/ If a Subnet chooses to process another Subnet's message, it will look up both BLS Public Keys and stake of the origin Subnet from the P-Chain.
This means there is no "per connection" overhead to maintain communication between Subnets, making any-to-any comms practical.
15/ The "stake" here is the Subnet's native unit of weight, not the amount of AVAX its validators' have staked.
In a Subnet this is the "weight" assigned by the Subnet operator or the amount of "user-specified custom tokens" staked by each Elastic Subnet participant.
16/ If a Subnet wishes to broadcast data to any Subnet willing to listen, it can send an "Anycast Message".
This enables an "oracle" Subnet to emit a periodic heartbeat that can be utilized by any other Subnet (it does not need to send a direct message to every other Subnet).
17/ To make AWM as scalable as possible, messages do not pass through the Primary Network at all.
It is up to Subnets and their users to determine how they want to ferry data from source to destination and what sort of guarantees they want to provide around transport.
18/ AWM is a primitive that any VM developer can use how they see fit. They get to determine what messages look like and how their VM will interact with these messages.
You can even overlay messaging formats from other teams on top of AWM if they work with your VM.
19/ So what happened at 6:42:29 AM UTC on 12/22/2022?
@stephenbuttolph sent the FIRST Avalanche Warp Message using a new Proof-of-Concept VM he made called XSVM (github.com/ava-labs/xsvm).
This VM allows for simple AWM transfers between any 2 Subnets running it out-of-the-box.
21/ Because AWM communications are not recorded on any chain in the Primary Network, the only way for you to view this historic moment is to join either of these Subnets on your node.
Or better yet, create your own Subnets and try it out yourself: github.com/ava-labs/avalanchego/tree/master/wallet/subnet/primary/examples
22/ In the coming weeks, we'll share a more technical write-up of how all this works but we couldn't wait to share all of this AWESOME news with the #Avalanche community ASAP!
23/ Avalanche Warp Messaging (AWM) is the catalyst that will spark a Cambrian explosion of Avalanche Subnet development. With this release, Avalanche provides a best-in-class toolkit for blockchain developers.
24/ You can launch your own Golang or Rust-based blockchain and reward any node that stakes your own token for validating it, all while natively interoperating with the entire ecosystem.
This is the result of years of work and I couldn't be more proud of how it turned out. ā¤ļø
25/ To take advantage of AWM, update to Banff 5 (AvalancheGo@v1.9.5) today! github.com/ava-labs/avalanchego/releases/tag/v1.9.5
š§ This release introduces VM@v21 to support generating BLS signatures. If you run a Custom VM, you will need to update it to run with v1.9.5. š§