Show newer

@snap_as was also the first product we launched separately from @write_as, and it was built on the assumption that an entirely separate codebase would be best.

The idea was that the applications would share common components (github.com/writeas/web-core), but would have separate application codebases and storage.

Show thread

Deployment got harder as their platform shifted beneath us, and one day recently our entire site was replaced by a simple message that said, "We no longer support Go 1.9." That was a fun day!

discuss.write.as/t/snap-as-is-

Show thread

A little background: this is driven by Google Cloud being a very, very bad cloud platform to build on as a small team.

We tried it in 2016 as an experiment, and a series of service deprecations since then have caused us downtime and meant us ultimately offering a stable, but stagnated service.

Show thread

This week I'm re-architecting and moving @snap_as from a separate application into our single @write_as application. Here are a few thoughts along the way.

[] AngeloStavrow opened writefreely-swiftui-multiplatform #45: Posts deleted from the server cannot be removed from the device github.com/writeas/writefreely

[] Closed #322: static assets served without cache policy leads to suboptimal page speed writefreely.org/issues/322

Show older

Write.as Development's choices:

A Bunch Tell

This instance is only for A Bunch Tell projects.