@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
> Guy on his first day as juniour developer accidentally destroys the production database
> Gets fired and threatened with legal action
Am amazed at the incompetence of the CTO who allowed that to be possible.
@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.
@KitRedgrave oh, a stable version is finally out? guess I know what I'm going to be doing the next few days
it's going to be hell due to the change to webpack, to merge everything in, but supposedly it'll make mastodon's web facing client smaller and run less like crap, so
@KitRedgrave thrashing is good, it reminds the user the computer is on
@andlabs @KitRedgrave eep?
Yes yes monologuing is pretty good for that I guess
OH FREAKING FINALLY https://is.a.qute.dog/media/2v1NF2nPigt9syizWtI
This was after at *least* ten failed promotion chances where I got matched with someone with a rating >1000 above mine
@Spex Awoo.space only federates/communicates with a very specific set of servers so keep in mind, you may lose connections to people on other servers.
That is part of the reason I left awoo.space and ran my own instance (the other half being to add my own customizations to Mastodon). Point's mostly moot now though, since my own server is on awoo.space's whitelist.
@andlabs neon blue and red is better than bland gray
@squirrel me every day