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.
12 destructive Linux terminal commands every Linux user must be aware of (don't run these):
1. Recursive deletion πποΈ
This is one of the scariest commands. When you run this command, it deletes everything in the root directory forcibly and recursively. As a result, all of your directories and subdirectories will be deleted, and all of your data will be lost.
2. Implode hard drive π³οΈ
This command will move all data to a special location in Linux known as the black hole, which is located in your system at /dev/null.
Everything that is moved to this location is destroyed.
As a result, if you accidentally move your data to this folder, it will not be recovered
3. The fork bomb π΄π£
This is my personal best, a simple bash recursive function that, when executed, creates copies of itself, which in turn creates another set of copies of itself. This takes up CPU time and memory. As a result, it loops until the system freezes.
Fortunately, you can defend against this attack by limiting the number of processes run by users to around 4000.
You can accomplish this by issuing the following command:
$ ulimit -S -u 4000
4. Overwrite the hard drive βοΈπΏ
This command writes raw data (command output) to the specified partition. This causes data loss on the hard drive or specified partition.
command - this could be any Linux command.
5. Blindly download and execute malicious script β οΈπ
Wget and curl are useful Linux commands for retrieving and downloading files from the internet. However, if we blindly download and execute a malicious script, these commands can be dangerous.
Please keep in mind the source from which you are downloading packages and scripts. Use only scripts or applications downloaded from a reputable source.
6. Breach the System π
This command does not physically affect your system in the same way that the other commands do, but it does provide a security breach on the system.
The chmod command changes file permissions to configure user access to a specific file or directory.
By running this command, you grant all system users the ability to read, write, and execute data on your system. In terms of security, this is risky and dangerous.
7. The hidden recursive deletion (rm -rf /) πποΈ
The following command is the same as the previously mentioned rm -rf / command. The codes are hidden in hex here to fool an unsuspecting user.
Running the code below in your terminal will delete your root partition leaving your system unusable.
8. Unknowingly format a hard drive π§Ήπ
This command will erase your hard drive and recreate it.
These should only be used when you have a backup of your data on the cloud or an external device.
9. Write random junk to hard drive π³π
This command will write random garbage data to your hard drive.
Your system will not be recovered as a result of this command.
10. Re-running all the history commands ππ
Because it executes every command from that you have already executed, the history | sh command can be dangerous. The action may cause system instability and the execution of commands that you do not want to repeat.
11. The ^foo^bar Command π
The ^foo^bar command has the potential to be both helpful and dangerous. While the command saves time by allowing you to edit a previously run command and re-run it,
it can also cause problems if you don't thoroughly check the changes you make before running it.
The command changes the first occurrence of foo to bar.
12. Blindly deleting the crontabs π€π
The crontab command aids in the automation of routine tasks. All commands and instructions, however, are saved in a single crontab file, which can be removed by using the -r option and the crontab command.
This can happen if you want to specify the -e flag but accidentally type -r. There is no yes/no prompt before removing the file, so be cautious.
Make a backup of your crontab file because there aren't many recovery options if it gets deleted.
Please DO NOT run any of the above commands in your Linux terminal or shell, or on the computers of your friends or coworkers. Run them in a virtual machine if you want to test them.
Any inconsistency or data loss caused by the execution of the preceding command will bring your system to a halt.
That's a wrap!
Thank you for taking your time to read our thread.
If you know of any other dangerous Linux commands that I have missed, please leave them in the comments.
And be sure to rt, like and follow us (@linuxopsys) for more future Linux content.