Write.as Development @writeas_dev@abunchtell.com

An idea that came to me the other night: maybe adding some way to closely integrate Read.as with WriteFreely, for anyone who wants to host an instance with more than just the writing experience.

Probably need to implement oauth so users can have one identity across e.g. writefreelyinstance.com and read.writefreelyinstance.com. Or maybe they just share data somehow; Read.as boosts get posted to WriteFreely blogs, etc. Could be really interesting combining them in new ways.

Now that WriteFreely is out there, it's officially the name of the fediverse software underneath the Write.as blogging service / instance. That'll get updated on sites like the https://the-federation.info soon.

Imagining some interesting uses for the https://writefreely.org site, especially around helping people start up new instances.

Good morning!

Let's see if I can finish up the #writefreely v0.1 release today.

Figured out the UI for single-user instances last night, and I think it'll work pretty well.

Now the setup process for a single-user blog includes admin user creation.

The backend UI is gonna take some work, though. A lot of things need to move around and get streamlined to work for instances hosting only one blog. Might save that for a future release.

Now to fill in all the cracks that open up when you run it in production, and make sure single-user mode is solid.

Just tested federation and it's working 👍

Morning!

Stayed up too late trying to get #writefreely running on a test instance, couldn't figure out why basic routes weren't working.

Today immediately found what was causing the problem. (That's why you don't stay up when you're stuck on something)

Phew. Intense day of getting the basic #writefreely app to a runnable state and pushed up to GitHub. Right now everything looks good in multi-user, federated mode. All the uncertain areas are around different configuration combinations -- and single-user mode.

Once single-user mode is solid, I'll call it v0.1 and make the big announcement

https://github.com/writeas/writefreely

I also updated the landing page a bit for new users, and put the Write.as logo back in the corner of the editor when you're logged in.

The "view blogs" icon that was up there before was fine, but too generic. The official logo there is just sexy.

Moving around some sites tonight.

Decided I'll host a demo instance of #writefreely on my writefree.ly domain -- currently occupied by a little marketing site I put up a while ago. It doesn't get a ton of traffic, so that'll just move to an unaffiliated subdomain (https://howto.writefree.ly)

I want to keep our GitHub issues low and, really, not use GH for project management. So we'll probably just accept pull requests and bug reports there, and then continue using our Phabricator instance for all planning and working with long-term contributors.

You can see some of what's planned already: https://phabricator.write.as/tag/write_freely/

#writefreely

One minor difference you'll see in #writefreely: "Anonymous" posts are called "Drafts".

This is a great use for them already on @write_as, so they'll retain their function, but now the name will match.

Finished the basic #WriteFreely project site yesterday: https://writefreely.org

Added more restrictive spam filters on posts, which keep flooding in even as sign ups have slowed down significantly.

Deviating from new feature plans to fix some user issues today. Right now: pagination on tagged post pages.

I think once I've forgotten all the keyboard shortcuts in Android Studio that's a good sign I've been away long enough.

I was also focused on adding more features to the web app (the place where people could buy a subscription) so that more people would find it valuable enough to buy a subscription. Focusing on that took a few months before we saw our first customer that stayed.

I really wish I hadn't waited this long to take care of it -- I know plenty of people are waiting on the update. But the platform is at a good place, and I think I'm finally over the mobile development hangover. I'm ready to knock it out

I *really* never meant for it to be delayed for as long as it has. Mostly, they were personal reasons -- for one, I was doing both Android and iOS development at a day job for most of the time after we launched blogs/accounts in 2016. And having my days packed with nothing but that really made me not want to do more of it when I got home. Relatively speaking, native mobile development feels like going back to the days of programming with punch cards to me.

A few goals for the week: https://lobste.rs/s/2g4s1p/what_are_you_working_on_this_week#c_hmykdk

First up: our eternally-delayed Android app.