Where did /write/ go

./blog.sh v1.11 — part 2 of 12

As of 1.11 the /write/ page does not exist. 1.10 announced its leaving: the page you could write from a phone on, and the SendPost shortcut, are going, and the apps take their place. The Android app is out. The iPhone app is not yet, and that is what this post is mostly about.

What exactly went

The /write/ page went, with its editor, its preview and its row of marks, the files the build copied for it, its site.js and the answers under /write/r/. The SendPost shortcut went with it. The page was switched on with the line write: true; whoever never used it has nothing to look for.

Whoever switched it on does not have to rework anything. ./blog.sh doctor points out the write: key left behind and nothing else changes. The first deploy after the upgrade takes the page off the site, so links to it lead to a 404; ./blog.sh check names every such link (link_dead). Going back to 1.10, write: true takes effect again and the page is published once more.

The receiver stayed, scripts/receive.sh, and so did the receipt: line, which makes a delivery that arrives twice one post. The publish.txt and drafts.txt requests stayed too, though 1.10 said they would go. The apps do not need them, but whatever talks to the receiver goes on talking to it.

Android: from today

A phone now writes through an app, and for Android there is one: blog.sh for Android, version 0.8.1, to be had as a signed APK on the releases page. It needs Android 10 or newer and engine 1.10 or newer on the server. It is installed by hand, not from a store; every later release is installed straight over the one before.

The app connects to the blog over the SSH the server already has and runs the same commands you type in the terminal. Nobody enters an address, an account or a key: ./blog.sh pair shows a code in the terminal, the app reads it with the camera and is connected. The key it works with was made on the phone and never leaves it.

It does not only replace /write/. It has the whole menu of ./blog.sh: a new post with photographs, the text in every language of the site, the properties of a post, the queue of scheduled ones, the archive with its search, the trash and a rebuild of the site. The row of marks over the text that /write/ offered, the editor in the app has too.

Two things the page could not do. What you write is kept on the phone at every letter, so leaving the form loses nothing. And when the server does not answer, the post waits, and as soon as the server is heard from it goes by itself as a draft.

Whoever wants to look the app over first, with no server, will find a practice blog in it with seven posts; nothing is written to it.

The first screen of the Android app on the practice blog: drafts in progress, the queue, buttons for a new post, the posts, the queue, the archive, the trash and the site, a search field and the blog's counts.
The practice blog in the Android app. Nothing here is sent anywhere.

iPhone: the app is done, but it waits for an account

The iPhone app is practically done, but we cannot release it yet. Whether through TestFlight or through the App Store, it needs a paid Apple developer account. That one is paid for, and Apple has not approved it yet. We cannot promise a date, because it does not depend on us. One thing we can promise: as soon as Apple approves the account, the app comes out.

Until then an iPhone writes as it did before there was a /write/ page: through an SSH client, in a terminal, with ./blog.sh add. You upload a photograph over SFTP into the incoming/ folder and point at it in the text by its bare file name, without a path: ![caption](photo.jpg). On saving, the engine moves it to the post. The whole procedure is in the engine's documentation, under Writing from a phone. It is not comfortable, but it works, and 1.11 changes nothing about it.

Why 1.11 does not wait

1.11 comes out before the iPhone app. We know that both at once would be better. But 1.10 announced the leaving of /write/ for exactly this release, and waiting for a decision that is not ours would hold back the skins, the series and the guides. Whoever writes from Android loses nothing the page could do. Whoever writes from an iPhone loses comfort for a time we cannot estimate, and should hear it beforehand, not from a 404.

Comments