Write.as Development @writeas_dev@abunchtell.com

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)

After I get these changes in (mostly around the database) I'll throw up an instance so I can start testing with #Plume and microblogging platforms. But so far everything works great in my testing with Write.as

Now Update and Delete activities are handled on #ReadAs, and requests are being verified. Going to mark this as v0.1 and move on to:

- 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

Now Read.as receives posts and adds them to your stream 🎉

Fixing up the design a bit and getting individual post links working, then I'll push up the latest changes.

Got the basic web UI going for Read.as, including authentication.

Part of the fun I have with this is figuring out how to build a simple application in as little time as possible that's still useful from day 1 -- and after some thinking I figured it out.

So v0.1 will have a GUI only for the primary use case: reading things. It'll eventually be multi-user (schema is set up for it), but single-user upon release. And to do anything besides the primary use case, you'll use cURL or Postman or whatever to call the API.

Last night got the database schema worked out to handle everything that'll be in the MVP and versions after. Today have been adding the API layer and bringing over code I needed from Write.as.

It's been a long day, but I have enough energy for more coding if it's for pure fun -- a new project, a blank canvas. Let's see how far I can get on this tonight.

We're now sending out Update activities, but it seems Mastodon doesn't do anything with them, so titles and URLs won't update. Still, it'll work on any future platforms that do something with the event.

Blogs are now discoverable on #Pleroma, but following doesn't seem to work -- no request is made to Write.as -- and the URL to the blog isn't correct. Will keep picking away at it.

Now finishing testing on new Update activities being sent out. In the course of doing this I also figured out how to make scheduled posts work with federation, so that should be a really nice feature when it's ready.

Patched the go-webfinger library (https://github.com/writeas/go-webfinger) so it supports requests without the acct: scheme and that seems to make blogs discoverable on #Pleroma. Still needs more testing.

Going to make individual posts findable in the #fediverse via search

@ernie @cesaraovivo Agreed, there's a ton of different uses / specializations to fill still -- this is just one part

@0x1C3B00DA @write_as 👍 will do!