Cross-posting has very low usage, as far as I know.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Tue, Aug 11
Still need to fix the Snap.as issue, but this hasn't come up lately.
Deployed this on Write.as and confirmed it worked. Now built into WriteFreely v0.17.2, so we can close.
Mon, Aug 3
Images are now embedded in the ePub file, but this can still fail on a large instance like Write.as. We need to support asynchronous file generation.
Taking this on now as the first supported format for T608: Import posts from another WriteFreely instance.
Tue, Jul 28
Getting started on this now. It'll be the first dedicated import provider we support
Getting the import work underway now, so starting on this.
Apr 9 2026
Mar 13 2026
Feb 9 2026
Oct 16 2025
Oct 1 2025
Sep 5 2025
Not sure if this is really needed at this point.
Sep 4 2025
Unable to test on Safari personally, so reaching out for help.
Aug 25 2025
Jun 24 2025
May 22 2025
Feb 18 2025
Feb 11 2025
Need this for #fight_back_news to show more posts. Will initially make it available only to Teams customers.
Jan 24 2025
Dec 1 2024
Oct 19 2024
Oct 15 2024
This affects relatively few people, so isn't a pressing issue.
Mentioned in this comment, we'll need to be able to upload a full archive of the posts, metadata, images, and files from another WriteFreely instance (T822: Include photos with Write.as export).
This is live on Write.as. For WriteFreely, tracking in T924: Custom WriteFreely favicon and avatar.
Not sure of the initial motivation for this. But I don't think this is necessary anymore, since we do our rendering on the backend.
Still need to fix the Snap.as issue.
This isn't critical anymore.
This was superseded by T873: Archive page.
Oct 13 2024
Oct 11 2024
Oct 10 2024
Oct 8 2024
I've just updated the command-line utility for this (rWFM), so it is functional again. But we are still missing functionality beyond basic text import. Other dependencies:
Twitter (now X) is fading, and has seriously restricted their API. So we don't need to pursue this.