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.
🧵 What is a zero-knowledge proof [system]?
It's the *sane* way of proving a statement is true.
For example, say I want to convince you I can solve a Sudoku puzzle *x*.
Why should I have to give you the solution *w* to the puzzle? You did not ask me for the solution, did you?
You asked me to convince you I can solve the puzzle! Those are very different asks.
Isn't it a bit *insane* for me to give you the solution *w* if you only want to be convinced I can solve the puzzle?
The difficulty is we're used to this *insanity*, both on the web & in society
For example, we assume a website must be given a user's password as a proof that the user knows the password. Nonsense.
Or, we assume that an identity verifier must be given a person's social security # as a proof that they have been issued that #. (Dangerous) nonsense, which...
In general, a ZKP for an *algorithm* *R* enables a *prover* to convince a *verifier* that the prover knows a secret *w* such that *R(x, w) = 1*, where *x* is known by both the prover & the verifier.
A bit of a tedious/boring abstraction... what is this *R*? Let's talk alcohol...
You are the *prover*. You have an ID card, which includes your date of birth (DOB) & is digitally-signed by your government.
The bar is the *verifier*.
They want to check that their `R = CanDrink` age verification algorithm succeeds: i.e., you are of drinking age.
On the other hand, you want to hide your name & DoB from the bar.
The bar only has the current date & the PK under which your ID is signed.
You compute a ZKP for the `CanDrink` algorithm, which (1) checks your ID's signature, (2) checks your age given the current date.
Most importantly, this ZKP hides your secrets: i.e., your name, DoB & the digital signature on your ID (which leaks name+DoB via bruteforcing).
The bar verifies this ZKP only against the current date & the PK.
The bar is *only* convinced that you *have* a valid ID & are of age.
Remember: The *sane* way is to *just* convince the bar that you can drink, without *insanely* leaking your name and DoB which, if done electronically, would leave a potentially-embarrassing trail of the (little) drinking you've been doing to all of your Eastern European friends.
ZKPs do more than maintain secrecy of the witness *w* when you prove that R(x, w) = 1.
1. They can have an extremely *succinct* proof (even though *x* and *w* might be large)
2. They can be much faster to verify than re-executing *R(x, w)* itself
This opens many other applications.
Let's do a complicated example of a (non-ZK)P, where the ZK property is not needed, but the succinctness of the proof & the fast verification is (points 1 & 2 from above).
This assumes familiarity with Merkle trees and/or state commitments.
e.g., rollups for L2s for payments!
Here, the L1 should verify that a block of L2 payment TXNs were valid, updating an old Merkle root of the L2 state to a new one.
The L1 (i.e., the *verifier*) has the old & new Merkle roots and the block of TXNs (i.e., the statement *x*)
(Note: This is an L2 rollup that cares about data availability, so it stores the L2 TXNs on the L1.)
The L2 *prover* has everything from above (i.e., *x*), plus Merkle proofs for the payers & payees in the block of TXNs (i.e., the witness *w*).
The L1 verifier, will check, via the (non-ZK)P, that the block validation function succeeds on the specified block of payment TXNs, using the Merkle proofs to validate the balances of the payers & update the balances of everyone.
(You can see how such "stateless" validation, based only on the old Merkle root, could work for payments in account-based cryptocurrencies in eprint.iacr.org/2018/968.pdf).
Summary:
(1) ZKPs are the *sane* way of proving something is true, without revealing any unnecessary information.
(2) If you understand that what is being proved is R(x, w) = 1, without leaking w, you understand ZKPs.
(3) Understand (2) via examples: docs.google.com/presentation/d/1b2FoHN983iA_ZkiISMCKa0JqlE40CeqaqNxWjWiJQjE