Show newer

Last change to the desktop app before release is giving back Markdown-enabled URLs.

This is enabled with the changes in writeas-cli v1.2, which you can now get on GitHub or via Debian repo: github.com/writeas/writeas-cli

Last thing is to finish up the download page on the site, and see if I can get the app on the @elementary AppCenter -- not sure if it'll work since it has external dependencies like the CLI.

Either way, once the download page is finished I'll announce how everyone can install the desktop app.

Show thread

Got this set up, and installing on a fresh machine works great!

Show thread

Going to work on a @snap_as CLI, but need to get standalone accounts going first. So the need for the CLI will probably speed that up a bit.

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

Got our PPA up and running with the latest version of the CLI, so now #Debian / #Ubuntu users can install it and get its updates by running:

sudo add-apt-repository ppa:writeas
sudo apt-get update
sudo apt-get install writeas-cli

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.

Show thread

Finally got the .deb built for the desktop app!

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

I've seen toots here and there about federation over Tor, but I'm not sure exactly how it will work today.

I'll be looking to move that development forward with anyone else working on that as we get closer to the self-hosted version.

Show thread

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

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

Show thread

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: go.code.as/writeas.v1

go-writeas library is getting closer to 100% API coverage (github.com/writeas/go-writeas) and I'm updating the API docs along the way (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: github.com/writeas/writeas-cli

Now gallery navigation works completely without Javascript 🎉

The app still requires it while logged in, just for the nicer, snappy experience of an app that makes asynchronous requests and keeps photos loaded in memory. But anyone viewing your galleries no longer needs it enabled 👍

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.

developers.snap.as/

Show thread

Today I'm working towards this by starting a Snap.as CLI project (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 writeas.org is released, you'll have the option to upload photos to your own instance instead.

Show thread
Show older
A Bunch Tell

This instance is only for A Bunch Tell projects.