Write.as Development @writeas_dev@abunchtell.com

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

Starting on the go-writeas library (https://github.com/writeas/go-writeas) upgrades to API v2, and then the CLI's support for it (https://github.com/writeas/writeas-cli)

Next deploy will have some new localizations: Arabic, Persian, Tajik, and Esperanto. https://github.com/writeas/web-core/tree/master/l10n

#microblogpub does indeed work on #readas! Just need to get that outbox imported.

Here's that #ReadAs demo instance, running the just-released v0.2: https://readas.labs.abunchtell.com

Once v1.0 is finished, I'll put it up on https://Read.as and open up registration to everyone.

#Microblogpub blogs can also be followed with #ReadAs, and should handle posts without any issues (still need to test). But existing posts aren't pulled in on follow either, because of how the outbox is set up.

Going to need to fully use go-fed for outbox parsing, instead of my currently hacked-together (and much less robust) solution.

Now #ReadAs works with #Plume -- everything besides fetching existing posts when you first follow someone, as Plume's outbox does things differently than other platforms I've seen. Might be able to hack around it in the future.

#ReadAs getting close to a point where I can throw up a demo instance.

✅ Pulling in a user's existing posts when you first follow them
✅ Fixing post viewing when not logged in
✅ Fixing database schema so it can eventually support posts from both local and remote users
- Typography improvements
- Instance configuration with JSON file

Home again after a week of house sitting and coding nearly nonstop.

Almost completely caught up on emails. Finishing a short video demoing federation on Write.as, then knocking out some small feature requests in the backlog.

Okay, the issue with Pleroma should be fixed now on my end. Will test again once I've made a few other fixes.

Threw #ReadAs up on a public instance and ended up breaking #Pleroma, so need to fix a few more things before I have a demo instance for everyone to try out.

This is just a small test to see if the post shows up on #readas.

Roadmap and current progress on #ReadAs here: https://github.com/writeas/Read.as/projects/1

As soon as v0.2 is out, I'll start creating issues that'll be up for anyone to grab. If you're interested in helping with development or documentation, let me know!

Okay, #readas schema looks better now -- all users in the same table, and the domain discovered on the webfinger request is used, for Mastodon instances that are hosted on a different domain than the one used in user handles.

A few more things I'd like to add on Write.as in the near future:

- Auto-linking fediverse handles in bios (need to resolve handles to fetch profile URLs; store usernames)
- Support mentioning fediverse users (resolve handles, send mention activities, shorten and link handle URL)
- Make canonical handles more discoverable on custom domains (searching for something like @blog@example.com returns correct @handle in webfinger request, or whatever will make this work)