Write.as Development @writeas_dev@abunchtell.com

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!

@frvl Oh absolutely. I'm really not a fan of using bots to answer questions -- there will be enough of that in the world. Talking to a real human is always better.

But especially as Write.as is growing there are common questions that regularly come up, and as the one person answering them it takes me away from development. So I just need to make sure the reading materials are obvious and answer frequent questions, to reduce the load a bit.

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.

A bunch of refactoring necessary to get JS working, but this will make permissions consistent and less error-prone for the future.

#fixed -- put something in place to prevent this on the backend. Will look into what might've caused it on the frontend soon.

Looking into multiple cross-posts. For some reason, cross-post destinations are being added to the `crosspost` form value multiple times.

You can now add custom JS, but it'll only be visible to you. Fixing.