Write.as Development @writeas_dev@abunchtell.com

Getting there... Now just need a good #golang #activitystreams library

Experimenting with webfinger and activitypub this afternoon. Let's see how this goes.

I also plan on experimenting with new editor features via browser extensions.

So instead of adding a Markdown preview in the editor, you can install an extension that'll show you a preview when you click it. Instead of adding a @snap_as uploader, there'd be an extension that lets you upload files and get the Markdown back, or see your existing photos and click one to insert the Markdown into your post.

Just ideas now, but the goal is adding functionality without cluttering up the interface.

Looking at setting up a forum to collect product feedback in one place.

Got back from NYC this weekend, spent it decompressing. Almost completely cleared out a large backlog of communications that piled up over the last few months yesterday (sorry for the delay, everyone). Today: finally back to coding, mostly on @snap_as

My biggest priority over the past week or so has been getting ready for TechDay in NYC on May 10, where we'll be exhibiting.

Needed to put together a demo, get stuff for the booth, polish parts of the site that really needed work. Pretty much all of it is out of the way now, so back to focusing on development again.

Interesting thing about building a native app for any computing platform is taking advantage of the unique features of the platform.

With a desktop app, users get a dedicated computing space with access to the file system and DE. So we build around that.

👀

Done. Now it'll be much nicer to add custom CSS and JS. Update going out tomorrow

Ok, adding in the Ace editor for editing CSS and JS.

Okay, not quite tonight. It's late and I need to be up early for an all-day event tomorrow. Looking at a Friday launch for this.

Looks like I'll have all the @snap_as updates ready to go tonight!

Working on revamping our user guides (https://guides.write.as) to be better organized and available directly on our main site.

Have heard about discovery issues, and even I usually have trouble navigating it.

I'm building @snap_as on Google App Engine and was using their NoSQL datastore (because cheaper), but refactored everything today to use MySQL.

Going with something I'm comfortable in is going to mean a more stable, reliable product and less of my own sanity lost.

Yeah, launching a new product that people will rely on from day one and will change a lot in the near future is not the time to try out schema-less databases.

You might've seen a 500 error when updating post metadata in the past day or so -- that's fixed now.

Also a #policy on monetizing your blogs, as it's another question we've received.

Preparing our official #policy on removing content from #writeas, to be published on the site.