fossilphant generates static websites from archives of your posts you can export from a Mastodon instance.

If your instance is shutting down, you can move to a new server, but your posts as a member of the departing instance will be effectively deleted from the internet.

To keep your posts alive...

1. download an archive of your posts
2. use fossilphant to generate simple, static website from the archive
3. rehost the site via any platform or service that supports simple websites

You can see examples in the two themes currently defined, shatter and tower.

shatter paginates your posts. tower places them all on one giant webpage. They are visually very similar.

Both themes collect your threads together, and display them in forward-chronological order (against the general reverse-chronological grain).

Both offer a "main" view that excludes your replies to other people's posts, and a posts-with-replies view that includes those.

"Boosts" are not republished.

You will need scala-cli installed on your machine. On a mac with homebrew that's just

$ brew install Virtuslab/scala-cli/scala-cli

Then...

1. Download your archive file from your Mastodon instance
2. Download the script fossilphant
3. Make it executable

   $ chmod +x fossilphant
   

4. Run the script

   $ ./fossilphant /path/to/my-mastodon-archive
   

   Note: If you want posts that you marked sensitive and/or followers-only posts included, then...

   $ ./fossilphant --include-followers-only --include-sensitive /path/to/my-mastodon-archive
   

   The archive can be an already extracted directory, or the original .tar.gz or .zip file. (The application will extract the compressed archive into a temporary directory if necessary.)

You should see a directory called public that contains your new website.

To customize, run

$ ./fossilphant --help

and check out the many options!

You will need scala-cli installed on your machine.

1. Download your archive file from your Mastodon instance
2. Download the script fossilphant.sc
3. Run the script

   C:\Users\steve>scala-cli fossilphant.sc /path/to/my-mastodon-archive
   

   Note: If you want posts that you marked sensitive and/or followers-only posts included, then...

   C:\Users\steve>scala-cli fossilphant.sc --include-followers-only --include-sensitive /path/to/my-mastodon-archive
   

   The archive can be an already extracted directory, or the original .tar.gz or .zip file. (The application will extract the compressed archive into a temporary directory if necessary.) You should see a directory called public that contains your new website.

To customize, run

C:\Users\steve>scala-cli fossilphant.sc --help

and check out the many options!

You will need a Java virtual machine, version 17 or higher, installed on your machine, and a UNIXy command line.

1. Download your archive file from your Mastodon instance
2. Clone or download this distribution
3. From the root directory of this distribution, run

   $ ./fossilphant-site-gen /path/to/my-mastodon-archive
   

   The archive can be an already extracted directory, or the original .tar.gz or .zip file. (The application will extract the compressed archive into a temporary directory if necessary.)

That's it!

You should see a directory called public that contains your new website.

At least for now, the full /media_attachments directory, containing all of the images and other media you might have posted, is copied into the website. This directory might include images associated with nonpublic posts.

Though it might be hard to guess the image file paths, they'll be there on a public webserver for anyone who might have those paths, including recipients of the original private posts, administrators of their servers, and whomever they talk to. And be sure that to set autoindex or its equivalent to off so that snoopers can't just browse your media library.

fossilphant is configurable, and for the truly ambitious, themable.

If you are running fossilphant via the scala-cli script, then just set command line arguments:

Usage: fossilphant [--include-followers-only] [--include-sensitive] [--output <outdir>] [--page-length <integer>] [--self-url <url>] [--tag-host <hostname>] [--tagline <string>] [--theme <shatter|tower>] [--theme-config <key:value>]... [--timezone <zone-id>] [--title <string>] <archive-tar-gz-or-dir>

Generates a static site from a Mastodon archive

Options and flags:
    --help
        Display this help text.
    --include-followers-only
        Include posts sent to all followers but not the full public
    --include-sensitive
        Include posts marked sensitive
    --output <outdir>, -o <outdir>
        Directory into which to generate site
    --page-length <integer>
        Number of posts per page (for themes that support paging)
    --self-url <url>
        URL to which you'd like your display name and handle to link
    --tag-host <hostname>
        Mastodon instance to which hashtag links should be directed (if not to the archived instance)
    --tagline <string>
        Main tagline for the generated site
    --theme <shatter|tower>, -t <shatter|tower>
        Name of theme for generated site
    --theme-config <key:value>
        Specify a configuration parameter for your theme.
    --timezone <zone-id>
        Timezone to use when generating post timestamps
    --title <string>
        Main title for the generated site

If you are building from this distribution, rather than a scala-clie script, check out the file fossilphant/src/config.scala to customize basically the same variables. Configuration is documented in the comments of that file. Just edit it in place.

You can mess around with colors, direct self links to your new identity, redirect tag links to a new host so they don't break against a defunct instance, change the title, the tagline, or the whole theme.

Both current themes supprt the following configuration variable:

• page.background.color
• post.background.color
• post.text.color
• outer.text.color
• outer.link.color
• outer.link.color.visited
• post.link.color
• post.link.color.visited
• post.border.color
• thread.border.color

When you change these you are really just altering the CSS that will be generated, so the values should be CSS colors, in any format.

Here are the default values, presented in the form of command line arguments to the scala-cli scripts:

$ fossilphant \
    --theme-config="page.background.color:rgb(225,225,225)" \
    --theme-config="post.background.color:#FFFFFF"          \
    --theme-config="post.text.color:black"                  \
    --theme-config="outer.text.color:black"                 \
    --theme-config="outer.link.color:#0000EE"               \
    --theme-config="outer.link.color.visited:#551A8B"       \
    --theme-config="post.link.color:#0000EE"                \
    --theme-config="post.link.color.visited:#551A8B"        \
    --theme-config="post.border.color:gray"                 \
    --theme-config="thread.border.color:black"              \
   [--any-other-options] <archive-tar-gz-or-dir>

Although shatter is based around paged feeds linking to single-post pages, it also includes an unlinked-from-index endpoint /withrepliesSinglePage.html which (tower-like) shows all posts and replies in one very tall page.

The motivation for this that while shatter's paging may be good for normal browsing, it's nice to be able to search your posts just by <ctrl> or <command> F. /withrepliesSinglePage.html is emitted for that!

No notes yet!

fossilphant is built in Scala, on top of my own template (well, untemplate) library, and my static-site-generator generator unstatic.

If you are a front-end developer, the templates that define themes should be somewhat familiar, below headers of Scala code. (Theme tower is more accessible.) It's mostly HTML and CSS, should be pretty tweakble.

For the ambitious, themes are defined by untemplates ending in

• .gen.untemplate (one template generated per site)
• .genpost.untemplate (many templates generated, one per post)
• .genpagewithall.untemplate (several templates generated, one per page of paginated posts including all replies)
• .genpagewithothers.untemplate (several templates generated, one per page of paginated posts including replies only to others)
• .genpagewithout.untemplate (several templates generated, one per page of paginated posts, excluding replies)

Templates without a .gen*.untemplate suffix define helper functions, used by the root, autogenerated templates.

Every untemplate defines a scala function. The helpers may be defined to accept pretty much whatever arguments, ad hoc. (They each accept a single argument, but that can be a tuple, rendering them callable with multiple args.)

The root untemplates accept

The template-generated functions live in Scala packages, beneath com.mchange.fossilphant.theme.

Each theme also includes helper functions, as well as constructs written in normal Scala. You'll find those under the parallel Scala source packages.

$ ./mill fossilphant.releasable

compiles the code and generates a fossilphant script consistent with the current projectVersion in build.sc.

While you are developing, the version should be something -SNAPSHOT or some other clearly-not-final-and-public form of version.

If fossiphant.releasable succeeds, publish your tentative version locally:

$ ./mill fossilphant.publishLocal

You can now just run the generated fossilphant script, which lives in ./out/fossilphant/script/gen.dest/:

$ ./out/fossilphant/script/gen.dest/fossilphant /path/to/my/archive

The generated site will appear in public/ (which is in .gitignore, so your test site won't get caught in version control).

For now, this is the only "testing" I'm doing: build a site, how'd it look?

• unstatic — a static-site-generator generator
• untemplate — templates (html/css/any-kind-of-text) as thinly wrapped specifications of Scala functions

If you are interested in learning more about these libraries and tools, hit me up.

Themes shatter and tower both use the gorgeous sans-serif font Montserrat.

Site generation is built atop the very excellent mill.

Libraries of note beneath this include zio, tapir, os-lib, upickle, JArchiveLib, scopt, decline (yes, both!) and undoubtedly many more.