Good morning. I feel embarrassed again because I *did* forget to bump the in-code version string to 1.4.5 yesterday night. I was asked about the performance regression in 1.4.4 by a friend (I didn't announce 1.4.4 for this reason - didn't want anyone to upgrade to that yet, since I discovered the regression only after releasing), so I was like "yeah, I know, we have a fix for that, let me tag it real quick" 😩
Yo yo yo!
#Mastodon v1.4.6 is released. I have not announced 1.4.4 and 1.4.5 (for a reason) so most will probably be upgrading straight from 1.4.3. For the full changelog, I do recommend looking through those two releases, but upgrade instructions are simple:
Notably, the "NSFW" button has been replaced with an eye icon for consistency, hashtag timelines now update in real time as they should, and spinny text is gone
I wish our SANs were just *BSD or Illumos running with ZFS exports, that'd be so much easier to work with than these weird proprietary solutions we have
The year is 2017, and people are STILL using telnet to configure their network infrastructure.
https://blog.doist.com/why-were-betting-against-real-time-team-messaging-521804a3da09 this seems like a neat thing, can't wait for it to be released so we can totally duplicate it as free software
@maiyannah I've seen it from both sides where the bug report looks like they have not read the documents or where I have got an answer like that.
Usually saying you have read the docs and been specific about where it's gone wrong "section 2 says press 3rd option but which screen do they mean" helps.
Programmers know their programs and often have a blind spot on assumed knowledge.
There is way more strange but interesting art and less advertising in languages I don't understand in this place.