You want to write posts with Markdown formatting on Mastodon, but the standard Mastodon software does not support Markdown in post composition. Glitch-Soc is a modified fork of Mastodon that adds Markdown support for post content, along with other features like longer character limits and advanced moderation tools. This article explains how to migrate your existing Mastodon account to a Glitch-Soc instance so you can use Markdown in your posts. You will learn the prerequisites, the step-by-step migration process, and what to do if something goes wrong.
Key Takeaways: Migrating Mastodon to Glitch-Soc for Markdown
- Preferences > Account > Move to a different account: Initiates the follower migration handshake to the new Glitch-Soc account.
- Export CSV from Preferences > Import and Export: Downloads your following list, mute list, block list, and domain blocks for import into the new account.
- Archive download from Preferences > Import and Export: Creates a complete backup of your posts and media before the migration.
Why Glitch-Soc Adds Markdown Support to Mastodon
Standard Mastodon uses a limited markup language for post formatting. You can use HTML tags like <b> and <i> in posts, but the platform does not support Markdown syntax such as asterisks for emphasis, backticks for code, or hash symbols for headings. Glitch-Soc is a fork of Mastodon that adds these capabilities directly in the composer. When you write a post on a Glitch-Soc instance, you can use Markdown tokens, and the software renders them as formatted HTML in the public timeline and your profile.
Glitch-Soc also includes other changes from the standard Mastodon codebase. It supports longer posts up to 5000 characters by default, advanced moderation tools like thread-based moderation, and the ability to mark custom CSS in your profile. The migration process moves your followers, profile, and content to a new account on a Glitch-Soc instance. Your old account remains as a redirect so followers can find you.
What You Need Before Migrating
Before you start, you need two things. First, a new account on a Glitch-Soc instance. You can find a list of public Glitch-Soc instances at joinmastodon.org or instances.social by filtering for the Glitch-Soc software. Second, access to your current Mastodon account. You must be able to log in and reach the Preferences menu. You also need the password for the new Glitch-Soc account and access to the email address associated with it.
Steps to Migrate Mastodon to Glitch-Soc for Markdown Support
The migration process has two phases. First, you export your data from the old Mastodon account. Second, you import that data into the new Glitch-Soc account and initiate the follower migration. Follow these steps in order.
- Export your data from the old Mastodon account
Log in to your current Mastodon instance. Click the gear icon in the top-right corner to open Preferences. Select Import and Export from the left menu. Click the Export tab. Download each CSV file listed: following_accounts.csv, mute_accounts.csv, block_accounts.csv, and domain_blocks.csv. Save these files to a folder on your computer. Do not skip any file. - Download your archive from the old Mastodon account
Still on the Import and Export page, scroll to the Data Export section. Click the Request your archive button. The instance will prepare a ZIP file containing your posts, media attachments, and profile information. This process can take several minutes. When the archive is ready, you will receive an email notification. Return to the Import and Export page and click the Download archive link. Save the ZIP file to your computer. - Create a new account on a Glitch-Soc instance
Open the Glitch-Soc instance you chose. Click the Create account button. Fill in your username, email address, and password. Confirm your email address by clicking the link sent to your inbox. Log in to the new account. - Import your data into the new Glitch-Soc account
On the new Glitch-Soc account, open Preferences. Select Import and Export. Click the Import tab. For each CSV file you downloaded, choose the corresponding import type from the dropdown menu: following, mute, block, or domain_blocks. Click Upload and select the file from your computer. Click Import. Repeat for each file. This will add all the accounts you followed or blocked on your old instance to your new account. - Set up the redirect on your old Mastodon account
Return to your old Mastodon account. Open Preferences and select Account. Scroll to the Move to a different account section. Enter the username of your new Glitch-Soc account in the format @username@instance.domain. Click Move followers. You will be asked to confirm your password. Enter your old Mastodon account password and click Confirm. This action tells the old instance to redirect your profile and send a migration request to your new account. - Accept the migration request on the new Glitch-Soc account
Log in to your new Glitch-Soc account. You should see a notification about the incoming migration. Open the notification and click Accept. This final step transfers your followers from the old account to the new account. After acceptance, the old account will display a notice that you have moved.
Common Issues When Migrating Mastodon to Glitch-Soc
Followers Not Appearing After Migration
If your followers do not appear on the new Glitch-Soc account after 48 hours, the migration may not have completed. This usually happens if you did not accept the migration request on the new account. Log in to the new account and check your notifications for the migration request. Accept it. If the request is missing, repeat step 5 and step 6. Also confirm that the old account displays a redirect notice on its profile page.
Markdown Not Rendering in Posts
If you write Markdown syntax in your posts but it appears as plain text, the Glitch-Soc instance may have Markdown disabled in its settings. Some instance administrators disable Markdown to maintain consistent formatting. Check the Glitch-Soc instance documentation or contact the administrator. If Markdown is disabled, you cannot enable it through your account settings. You must choose a different Glitch-Soc instance that supports Markdown.
Old Account Still Active After Migration
After migration, your old Mastodon account should show a redirect notice and you should not be able to post from it. If the old account still allows posting, the migration was not fully accepted. Go back to the old account and repeat steps 5 and 6. Make sure you click Move followers and confirm with your password. Then check the new account for the migration request.
Standard Mastodon vs Glitch-Soc: Markdown and Feature Comparison
| Item | Standard Mastodon | Glitch-Soc |
|---|---|---|
| Markdown support in posts | No | Yes |
| Default character limit | 500 | 5000 |
| Custom CSS in profile | No | Yes |
| Thread-based moderation | No | Yes |
| Migration compatibility | Standard Mastodon instances | Standard Mastodon and other Glitch-Soc instances |
Now you can post with Markdown formatting on your new Glitch-Soc account. Use syntax like double asterisks for bold, single asterisk for italic, and backticks for inline code. Your followers from the old account have been transferred automatically. To keep your new account secure, enable two-factor authentication in Preferences > Account > Two-factor Auth after the migration completes.