Going to wait for 1.4.0 before I do any major changes to my instance again. Too much stuff has already changed in master, it's going to be merging hell.
I guess I don't have much to say, do I?
Yep, this sure is a movie
Closed captions are on the TV too and they're also a jumbled mess
@KitRedgrave Hahahahahahahaha
Well, I still keep the branch up to date with the latest tagged release if anyone wants it so
@KitRedgrave what now I wonder?
I guess @TheKinrar finally got tired of my version number stretching the table out, haha
@KitRedgrave what there's a new 1.3.x version
time to go through merging hell
And this: https://github.com/TootCat/mastodon/issues/41
Guys, if you make your public posts require auth, _they aren't public anymore_. Not to mention making it incredibly difficult for users of any other instance in the fediverse to interact with you.
From looking at toot.cat's issues list, I don't feel that they have the slightest clue on how social media works when they propose things.
This, for example, is the most inane rule request I've seen in a while: https://github.com/TootCat/mastodon/issues/37
This is exactly why you follow people you're interested in, not try to hide EVERYTHING that any given person in the world might not understand behind a content warning!
@KitRedgrave That's like half the fun of having your own instance in the first place!
At least... it was for me...
Laying down with a tall glass of strawberry milk... <3
Issues with Mastodon's federation are extremely frustrating.
As is how sluggish the input box has gotten in 1.3.2, sheesh
oh look at that, posts aren't being sent to mastodon.social. again. for whatever reason the PuSH subscription has expired.
We're live again! Now running 1.3.2 with monologuing and all the other upgrades I'd made ported forward. IPv6 is now enabled and working on the server as well.
is.a.qute.dog will be going offline shortly while I update Mastodon to 1.3.2 and do some other maintenance on the server.
By the way, monologuing branch has been updated to 1.3.2 as well if anyone was using it.
I should probably start working on updating the monologuing branch to 1.3.2, along with the deployment branch I run for my server.
But that requires me to start up my desktop and I'm lazzzzzzy...
@KitRedgrave @ninjawedding @animeirl And it assumes posts won't contain multiple languages worth of text, which is also not necessarily correct...
I can immediately think of JP/EN mixed *tweets* as an example. The higher character limit just makes it more likely to happen.