Lost upvote/downvote buttons
-
iOS 10, Safari, iPhone 6
Tried hard refresh, tried opening in a new tab.
Filed under: not that it bothers me, all of your posts suck anyway!
-
@kt_ also, @mods, categories on mobile still don't work, so if could kindly move this to bugs, I'd be thankful.
-
FUCK THIS.
Mea culpa, just read the notice board properly.
Please disregard this stupid blind FUCK that I am here.
-
-
@kt_ said in Lost upvote/downvote buttons:
Please disregard this stupid blind FUCK that I am here.
Done. ;)
-
@kt_ they appear to have returned.....
-
@accalia The updating really doesn't take all that long.
-
@boomzilla said in Lost upvote/downvote buttons:
@accalia The updating really doesn't take all that long.
/me defaults to "Windows Update" speeds when assuming how long updates take
-
-
-
@kt_ said in Lost upvote/downvote buttons:
Please disregard this stupid blind FUCK that I am here.
Don't worry, on Mobile it should have taken at least three seconds for the banner to jellypotato in, so it's easy to miss if you're not at a topic list.
-
@Tsaukpaetra said in Lost upvote/downvote buttons:
@kt_ said in Lost upvote/downvote buttons:
Please disregard this stupid blind FUCK that I am here.
Don't worry, on Mobile it should have taken at least three seconds for the banner to jellypotato in, so it's easy to miss if you're not at a topic list.
It took up my entire view, I had to scroll down to get to any topics when it jellypotato'd me back to the top.
-
@boomzilla said in Lost upvote/downvote buttons:
@accalia The updating really doesn't take all that long.
-
@ben_lubar oh look, we were one hour early for this:
-
@ben_lubar said in Lost upvote/downvote buttons:
@ben_lubar oh look, we were one hour early for this:
I was wondering why it seemed somewhat unstable for a while.
-
@Tsaukpaetra said in Lost upvote/downvote buttons:
@ben_lubar said in Lost upvote/downvote buttons:
@ben_lubar oh look, we were one hour early for this:
I was wondering why it seemed somewhat unstable for a while.
So far, the update script has only run once. But if the Docker container gets restarted before the next update, it'll be 503-ing until it finishes that script.