matt @matt@writing.exchange

@gytis @staticsafe @write_as thanks! :)

@mara_cav_ @wion @DuthOlec Yep, general thoughts and chatter are great here too.

There's definitely an impression that people should split up their personalities across instances -- and I tried that in the early days, too -- but I don't want to force that much work on people.

I'm of the mind that we're all here because we share a common interest ("writing"), and everything else should be able to flow from there.

@maloki Definitely interested with WriteFreely

@maloki @matt Yep! They're recognized in the fediverse no matter what 😃

I can definitely see how this isn't intuitive though -- I made a note to add it to our docs.

@mariusor @write_as :) Thanks!

#WritingExchange is now on Mastodon v2.9!

Among other things, this brings an optional single-column layout, which you can set by unchecking the "Enable advanced web interface" option in your user settings.

https://blog.joinmastodon.org/2019/06/mastodon-2.9/

I've also updated our custom stylesheet here on Writing Exchange to keep the wider compose area in both the single- and multi-column views. (But let me know if anything looks funky.)

@bix It keeps the original draft's publish date.

I could see how different behavior might be good, though. Please feel free to propose it on the forum if you want

@mrb no problem 👍

@mrb Things are validated. Now all core development is done on feature branches off of `develop`, with code review before merging. (So, more validated than the master branch used to be.)

Of course, there may be some larger features that get added over several pull requests (thus might need fixes / changes), but in general we're trying to avoid that.

@mrb Sure, now that we have a few core developers we're doing everything off of the `develop` branch (instead of `master` like before). We'll then merge it into `master` when we do an official release.

@bix This looks like an issue with $GOPATH/bin not being in your $PATH. It's looking for the `go-bindata` executable after fetching it, but isn't finding it.

@bix What command are you running when you encounter the error?

@wion Yep, I'm mostly paying attention to users on this instance. I do appreciate the input.

I'd just like a bit more time to think about this and decide on which way to go.