Write.as Development @writeas_dev@abunchtell.com

Might just set up my own Debian repo to host the desktop app

Finally got the CLI packaged and building correctly Launchpad. Next to get the GTK app built

Switched from building the CLI based off the code, but I can't even get Launchpad to successfully build the package with a single binary in it. Think I've wasted enough time on this today.

Holy moley. Debian packaging -- not fun!

Actually, going to put everything under a single PPA: https://launchpad.net/~writeas/+archive/ubuntu/ppa

Finally got the .deb built for the desktop app!

Now just updating the CLI ppa (https://launchpad.net/~writeas/+archive/ubuntu/writeas-cli), uploading the GTK app package, testing installation, and finishing up the download page on the site.

Also, this new site is powered by a fork of http://gopkg.in I modified to work with my Gitea instance, https://code.as.

In case you want to self-host instead of relying on gopkg.in, here's the code for that: https://code.as/abunchtell/gopkg

Recently had to make some ⚠️ breaking changes to the go-writeas library ⚠️ so if you're using it in any projects, I'd recommend switching from github to our new versioned path as soon as possible: https://go.code.as/writeas.v1

go-writeas library is getting closer to 100% API coverage (https://github.com/writeas/go-writeas) and I'm updating the API docs along the way (https://developers.write.as/docs/api/).

Main reason for all these updates is custom work I'm currently doing around the CLI, which will be really useful for a lot of people.

Here are some of the changes I've been making: https://github.com/writeas/writeas-cli/commits/local-workflow

A few fixes for @snap_as deploying soon.

Making a few tweaks to the API to support the new CLI changes... adding a `url` property on collections and adding a logout endpoint for non-web clients: DELETE /api/auth/me

As an aside to that: like Write.as, Snap.as will have an open API so you can build on top of it. I'm aiming to have the API design solidified and documented by the end of this month. And I'd like to build it so the endpoints can blend with the Write.as API, so any apps built today will continue working with your self-hosted blog.

https://developers.snap.as/

Today I'm working towards this by starting a Snap.as CLI project (https://github.com/snapas/snapas-cli) that'll work on its own, but I'll also include in the Write.as CLI. The latter will upload to Snap.as today, and when https://writeas.org is released, you'll have the option to upload photos to your own instance instead.

The self-hosted version of Write.as is going to have image hosting built-in.

While it makes sense to have this functionality separated in @snap_as today for the hosted platform, it would be a pain for you to have to install and maintain two separate applications just for this.

Now that I'm actually using the go-writeas library for the CLI, I'm also fixing inconsistent / wrong examples in the API docs https://developers.write.as/docs/api/?go#update-a-post

Interacting with our Tor hidden service is now supported in the go-writeas API client: https://godoc.org/github.com/writeas/go-writeas#NewTorClient

A very minor update to the CLI, v1.1, is out now: https://github.com/writeas/writeas-cli/releases/tag/v1.1

* Adds --user-agent flag
* Fixes `go get`
* Refactors some things