Kaito / Katie Sinclaire @KS@is.a.qute.dog

Laptop's charging cable just gave out for good, need to seek out a replacement now :\

@andlabs sounds like it would be "mutual followers only", which would be a nice middle ground between the current options of "anyone can follow you to see this" and "completely locked down"

@KitRedgrave Just keep being you; I'll still be here for you regardless of what happens, providing hugs and affection as I always do.

*hugs*

@pokemonrates yes that's two, now 98 more please

@KitRedgrave I mean, it's incredibly easy when there's tons of translations that all exist to clarify that things mean exactly what you want them to mean

I want to retoot/boost "Sylveon good" like 100 times

Discord is quality software https://is.a.qute.dog/media/2iWSS5iUN1ciMKnX1V8

@revenant now time to hack the titles

@andlabs @KitRedgrave that behavior seems really bad, like it should be a privacy setting instead of checking for emoji presence in a post

Might possibly cause unintended posts to be hidden (bot posts, etc), difficult for users unaware of the feature to tell *why* people are doing this, or for them to learn about the feature's existence in the first place

@vahnj in what way, specifically?

Because, um, this didn't show up on my home timeline until I refreshed the page, while other posts were showing up fine... so I might be having issues too.

What have I done... https://is.a.qute.dog/media/Pz6OamGruvggraZiQOw

@Trev oh, so you're the mysterious second user on Kit's formerly "single-user" instance o.o

Just a thought, for a while now my branch has replaced the sensitive button's content with the usual warning triangle as opposed to the text "NSFW", which I feel is both not encompassing entirely what "mark sensitive" means and is too wide horizontally compared to the rest of the buttons. Like so: https://is.a.qute.dog/media/Z21JSEqIjwjGZ5jlXUQ

I wonder if this is something to propose to others?

The monologuing branch is up to date now with 1.4.1. Since I needed to redo a lot of stuff due to the switch to webpack, the old branch for 1.3.3 is still available too.

So of course I wake up and the server is randomly dead, oh wonderful.

Of course, it had to do this while I was asleep. Couldn't do anything while I was still awake, that would make it too easy on me.

I'm not entirely sure what happened. May just have needed a restart for upgrades. Oh well.

And we're fully live again, finally. Had to do some server reconfiguration to make sure everything was working A-OK, but we're good now <3

So, uh... Clearly my instance is alive and running, but I'm not getting any CSS or JS on the actual server. I'm having to send this through Tusky.

Any ideas as to what's going on?

Is.a.qute.dog is going down in a couple of minutes to upgrade to 1.4.1.

I HOPE THIS WORKS

My "dealing with merging hell" music: https://www.youtube.com/watch?v=GAQRuZHboF4

I wonder if I can get this done before I have to leave for work tonight.