Offlineland.io's exporter thingy

exporter.js is a console snippet to export your account from Manyland (creations, collections, snaps, etc), and potentially import it back to Offlineland.io

To run, make sure you're logged in in-game, go to the info-rift page, then copy-paste this snippet into the console:

fetch("https://raw.githubusercontent.com/offlineland/exporter/main/exporter.js").then(res => res.text()).then(txt => eval(txt));

You can find more detailed informations here.

For developers:

The goal of this exporter is to save private data off of Manyland into a self-contained format (usable as-is for people to dig through all of their manyland content). Files should be human-readable and incidentally machine-readable (eg. the exported data can also be re-imported in Offlineland by programatically reading the .zip file's content).

Design goals:

• Don't hammer the Manyland servers:
  • Throttle the API calls (use sleep with appropriate times)
  • Avoid downloading public data (that is unrelated to the user) as it's all in the archives already
• Preserve user privacy:
  • All data must come from Manyland, stored on-device, and not sent anywhere. Ideally, don't ever make HTTP requests that aren't outbound to Manyland or a CDN - and when you do, only query public data. "Public" data is understood as being placed in a public area area or available from universe search.
  • Don't store other players' private or personal data - this mostly applies to boardposts. For more on the rationale, see the Responsible use section of the Archives repository.

The actual work is done on the exporter.ts file (.ts instead of .js) because I can't live without types. To set up a dev env:

• install dependencies:

bun install # or yarn, or npm....

• run the compiler in watch mode:

bun run dev

While developing, when copy-pasting the built exporter.js you'll need to be careful not to copy the first two lines:

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });

Typescript really really wants to include them (because exporter.ts is considered a "module" because we use import type ... in it, even though that syntax is erased at compile time) and has no option to control that behavior, but they make the browser throw an error.

(You only need to care about it when developping locally, the CI takes care of removing it on the .js file in the repo)

(If you manage to have tsc pick up the type for Zod.infer without using the import/export type ... syntax you're a god please help me)

About the dependencies we fetch

Bun

Bun is a "fast all-in-one JavaScript runtime". It's basically Node.js or Deno, except faster and way more convenient and has everything built-in

You should be able to replace bun above with yarn or npm, but I use bun for convenience in all the offlineland repos.

Zod

Zod is a powerful parsing + validation library; ideally I'd use it to validate all incoming data, but manyland's api is so full of holes and exceptions that I don't want to have it fail mid-way, so the exporter is mostly archiving everything as-is.

RE:DOM

RE:DOM is a "tiny turboboosted javascript library for creation user interfaces" - it's basically React, except way more barebones and no JSX. I use it because I didn't want to add all the annoying react tooling and a heavy transpilation step, and the exporter really doesn't need much.

It's a bit unsightly right now because I wrote 99% of it in a very basic style because I couldn't get my editor to work the types out, sorry about that!

The other libs are pretty self-explanatory: JSZip for zipping, csv-stringify for generating the .csv files, file-saver to be able to download the zip, and idb as a lightweight wrapper around the awful IndexedDB API.