Topic: (OLD) The Bug Report Thread

Posted under Site Bug Reports & Feature Requests

This topic has been locked.

SSL issues

Bug: SSL doesn't seem to work on user home pages (http://e621.net/user/show/xxxx)

Expected behavior: SSL everywhere

Actual behavior: SSL available everywhere but user home pages

Steps to duplicate: Visit any user home page
e.g. https://e621.net/user/show/41009

fix pending
-

tony311 said:
It's the standard, but Opera (and possibly other browsers) don't recognize it correctly and require 'none'.

Oh, didn't know that

Updated by anonymous

Bug: Searching for "" returns a 500 (note that there's nothing between for and returns)
Expected behavior: Some error or message indicating that there is nothing to search
Actial behavior: A wild Error 500 appears
Steps to duplicate: Go to Recent Changes and click on the Search user button (don't type anything). Apparently it only happens there

Updated by anonymous

DragonRanger said:
Uploading appears to be broken at the moment.

And just when I'd found something to upload too...

Updated by anonymous

DragonRanger said:
Uploading appears to be broken at the moment.

Really? Since when?

Updated by anonymous

xLuna said:
Really? Since when?

At a guess, since about 6 hours before your post.

Updated by anonymous

slyroon

Former Staff

Bug: Tag subscription stay after deletion of subscribed tag

Expected behavior: they should disappear from user page

Actual behavior: they stay

Steps to duplicate: delete a tag you have subscribed to and watch aa the thumbnail stays on your userpage
Taag subscriptions update once every thirty minutes. Learn to be patient

Updated by anonymous

Bug: <Description of bug> Searching Loli returns pictures without loli tag

Expected behavior: <What is expected to happen> Only returns pictures with loli tag

Actual behavior: <What actually happens> Returns everything with loli, young, shota (tag association?)

Steps to duplicate: <How to recreate the bug reliably> search loli

Updated by anonymous

PhrozenFox said:
Bug: <Description of bug> Searching Loli returns pictures without loli tag

Expected behavior: <What is expected to happen> Only returns pictures with loli tag

Actual behavior: <What actually happens> Returns everything with loli, young, shota (tag association?)

Steps to duplicate: <How to recreate the bug reliably> search loli

That's not a bug. Loli has been aliased to young. Refer to forum #38123.

Updated by anonymous

ippiki_ookami said:

Bug: cannot vote on flagged images

Expected behavior: you should be able to

Actual behavior: i spill ketchup on my shirt

Steps to duplicate: take a spiritual journey with the buffalo

[/section]
If this was fixed it is broken again. If it hasn't been fixed yet then sorry to bug.

Updated by anonymous

Test-Subject_217601 said:
Uploading seems to be borkd again.

we keep growing faster then the amount of drives we can feed this bitch. XD

All realistic predictions have been greatly proven underestimated.

Updated by anonymous

Aurali said:
we keep growing faster then the amount of drives we can feed this bitch. XD

All realistic predictions have been greatly proven underestimated.

~table flip~
DRIVE SPACE, Y U SO SMALL?!

Updated by anonymous

Aurali said:
we keep growing faster then the amount of drives we can feed this bitch. XD

All realistic predictions have been greatly proven underestimated.

How much space/many disk drives has e6? please, don't tell me it's less than 250GB

Updated by anonymous

xLuna said:
How much space/many disk drives has e6? please, don't tell me it's less than 250GB

2kb. Websites don't need any more than two kilobytes, maybe three if you're really hosting a lot of files.

Updated by anonymous

Blaziken said:
2kb. Websites don't need any more than two kilobytes, maybe three if you're really hosting a lot of files.

Damn, you're stingy. Bill is offering 640kb.

Updated by anonymous

Blaziken said:
2kb. Websites don't need any more than two kilobytes, maybe three if you're really hosting a lot of files.

In the most basic page, right? Cuz with 6.5KB (HTML, CSS, JS and 2 PNGs) I have a scrolling SMW background :V just sayin'

Snowy said:
Damn, you're stingy. Bill is offering 640kb.

640KB? Still, is quite short :/

Updated by anonymous

All pages with thumbnails on it appear to be borked...not including avatar thumbnails.

Updated by anonymous

Fixed in next update

Updated pixiv urls break the automatic url source converter

Bug: When using the new direct image url on pixiv, the source is no longer parsed to the

http://www.pixiv.net/member_illust.php?mode=[medium]&illust_id=[id]

format

Expected behavior: Automatic link parsing

Actual behavior: The direct source url is still used (which leads to a blank page)

Steps to duplicate: Upload any pixiv image (with the direct url) that uses the new format

- Credit to Munkelzahn & Blx24 for pointing out that the urls no longer automatically change

N.B The previous direct url format was:
http://img[##].pixiv.net/[medium]/[pixiv username]/[image id].[file extension]

Where [*] was (usually):

  • [##] = A 2-digit integer
  • [medium] = "img"
  • [pixiv username] = The unique pixiv username of the artist
  • [image id] = The unique image id of the post, as an integer (supposedly any length)
  • [file extension] = jpg, png or gif

-

The new format:

http://i[#].pixiv.net/img[##]/img/[pixiv username]/[image id].[file extension]

Where:

  • [#] = A single digit integer; usually 1 or 2
  • [##] = An arbitrary integer (usually 2 digits)

Updated by anonymous

img.preview { border-radius: 4px 4px 0 0 }

Great job on the update, thumbs barely rounding on the corners directly above each's respective status bar is threatening to drive me mad though.

Updated by anonymous

Bug: the favcount on image thumbs seems to be broken
Expected behavior: all favorites should be counted
Actual behavor: only some favorites are counted
This can be seen by the fact that even if you search for fav:$username, results can show up with 0 favorites indicated. It doesn't seem to be "only favorites from privileged+ users count" as suggested elsewhere, because some privileged users and even admins have favorites with 0 favorites indicated on the thumbnail.

As an example, try fav:SnowWolf order:favcount_asc. There's a page and a half of "♥0".

Updated by anonymous

Yeah, strangely enough only privs and higher can change that score.. I'm gonna fix that sunday sunday sunday after all the bugs get fixed.

CoffeeFly said:
Not sure if counts as bug or not but...

Bug: Blips section not on http://www.e621.net/static/more

Expected behavior: Blips should be there, along with everything else

Actual behavior: Blips are not there, only in the top menu

Steps to duplicate: Go to http://www.e621.net/static/more

The secret of blips have yet to be revealed. They will have an overlying purpose, but for now they are just for fun :)

Unless tony beats me to it
|
V

Updated by anonymous

Snowy said:
Bug: the favcount on image thumbs seems to be broken
Expected behavior: all favorites should be counted
Actual behavor: only some favorites are counted
This can be seen by the fact that even if you search for fav:$username, results can show up with 0 favorites indicated. It doesn't seem to be "only favorites from privileged+ users count" as suggested elsewhere, because some privileged users and even admins have favorites with 0 favorites indicated on the thumbnail.

As an example, try fav:SnowWolf order:favcount_asc. There's a page and a half of "♥0".

It's already fixed in the next update.

Updated by anonymous

Kald

Former Staff

Bug: the bars containing a post's stats (votes/favs/comments counts) don't appear on thumbnails that are not large enough.
For example : http://www.e621.net/post?tags=id%3A87905
Expected behavior: the aforementioned bars should have a minimum width, regardless of the associated thumbnail's width

Somehow I have the feeling the problem was known even before the feature was implemented.

Updated by anonymous

MaShCr said:

img.preview { border-radius: 4px 4px 0 0 }

Great job on the update, thumbs barely rounding on the corners directly above each's respective status bar is threatening to drive me mad though.

Here, have this:

span.thumb img.preview {
  border-bottom-left-radius: 0px !important;
  border-bottom-right-radius: 0px !important;
}

---
Bug: Userlevel and date of post have the same classname ("date"). While userlevel displays the "help" cursor, the date displays the "hand/link" cursor (which leads to post id).
Expected behavior: It shouldn't be that way, I suppose

Updated by anonymous

xLuna said:
Here, have this:

span.thumb img.preview {
  border-bottom-left-radius: 0px !important;
  border-bottom-right-radius: 0px !important;
}

---
Bug: Userlevel and date of post have the same classname ("date"). While userlevel displays the "help" cursor, the date displays the "hand/link" cursor (which leads to post id).
Expected behavior: It shouldn't be that way, I suppose

xLuna do you know ruby?

Updated by anonymous

Aurali said:
xLuna do you know ruby?

Nopey, just basic html, js and css

Updated by anonymous

Bug: dtext linking markup and formatting markup interact oddly
Expected behavior: a dtext link in "":url format immediately next to a formatting tag should be handled gracefully.
Actual behavior: the HTML gets appended to the url, except for the closing >, which shows up on the post (at least in preview). If it is a closing tag, the rest of the post will have the formatting that the tag was supposed to close. I'm not sure if that will flow past the post, and will be testing in this thread momentarily.
this is a test moar words
EDIT: test removed because PROBLEMS

test the second

Updated by anonymous

test[/i]

Oh wow, that's a problem.

...even worse than expected.

Okay, it overflows the post, and ALSO cannot be closed by a closing tag in the next post. PICTURE!

An opening formatting tag with no closing tag is handled properly.

Updated by anonymous

Snowy said:
test[/i]

Oh wow, that's a problem.

...even worse than expected.

Okay, it overflows the post, and ALSO cannot be closed by a closing tag in the next post. PICTURE!

An opening formatting tag with no closing tag is handled properly.

I like the italics on the paginator *takes notes*
---
Bug: Deleted posts show no images
Actual behavior: This (at least on my pc, cache cleared)
Expected behavior: The old "Deleted" image
Steps to duplicate: Search status:deleted

Updated by anonymous

Bug: logged-out/unregistered users are unable to view categorized forum topics.
Expected behavior: it is possible to browse the forums without logging in
Actual behavior: Only old threads are visible. Since, in the few days between tests, it went from "month+ old threads" to "3+ month old threads", I believe that only uncategorized topics are viewable (and that the mod team is going back through the archives and categorizing topics)
Steps to duplicate: Log out, attempt to view forums.

Updated by anonymous

Snowy said:
Bug: logged-out/unregistered users are unable to view categorized forum topics.
Expected behavior: it is possible to browse the forums without logging in
Actual behavior: Only old threads are visible. Since, in the few days between tests, it went from "month+ old threads" to "3+ month old threads", I believe that only uncategorized topics are viewable (and that the mod team is going back through the archives and categorizing topics)
Steps to duplicate: Log out, attempt to view forums.

Fixed.

Updated by anonymous

Snowy said:
Bug: logged-out/unregistered users are unable to view categorized forum topics.
Expected behavior: it is possible to browse the forums without logging in
Actual behavior: Only old threads are visible. Since, in the few days between tests, it went from "month+ old threads" to "3+ month old threads", I believe that only uncategorized topics are viewable (and that the mod team is going back through the archives and categorizing topics)
Steps to duplicate: Log out, attempt to view forums.

not a bug. just settings being dumb

Updated by anonymous

Aurali said:
not a bug. just settings being dumb

You want I should make a "settings being dumb" thread, and add to the clutter? Oy.

Yiddishisms are fun <3

Updated by anonymous

Bug: When a user is added to a blacklist and the option to hide comments is selected, clicking to show comments that are "below threshold" that contains a comment by the user causes the page to lock in an unloadable loop.
Expected Behavior: Comments by users not blacklisted, but below threshold should be loaded when electing to show comments below the threshold.
Actual Behavior: The page becomes unloadable and locks in a loop, browser eventually determines that the action can never be completed.
Steps to duplicate: Tried other browsers and combination of users blacklisted with the same result.

Updated by anonymous

Bug: Changing password
Expected Behavior: To change a pass
Actual Behavior: 500
Steps to Duplicate: Enter in new pass confirm it and submit

Updated by anonymous

So apparently the JSON API doesn't include the "count" attribute to tell you how many posts your search returned. I would expect both APIs to give identical results in different formats.

[edit] and I don't know how to make URLs

Updated by anonymous

RenaKunisaki said:
So apparently the JSON API doesn't include the "count" attribute to tell you how many posts your search returned. I would expect both APIs to give identical results in different formats.

[edit] and I don't know how to make URLs

the json api isn't designed to be public, just for the javascript engine to use. This was like the guy who wanted to have the json api extended to show dangerous data off site.

Updated by anonymous

Even though this is probably intentional, still mentioning it just in case

Bug: Adding a hyphen-minus sign (-) to the blacklist blacklists all images

Expected Behavior: ?
Actual Behavior: All posts are blacklisted regardless of anything else that may be present in the user's blacklist
Steps to Duplicate: Enter "-" without quotation marks into your blacklist in a new line

Notes:
  • Other alphanumeric symbols don't affect the blacklist (such as ? or !)
  • Nor do non-existent tags (qwerty)
  • Adding "-" into a line with a tag already there has no apparent effect on the blacklist. Direction makes no difference either (- sex and sex - both do nothing)
  • Removing the space seems to treat the tag differently (sex- is treated as a tag (which removes sex from the blacklist, causing it to show up in posts, and -sex presumably does the same)

Updated by anonymous

Char

Former Staff

titaniachkt said:
Even though this is probably intentional, still mentioning it just in case

Bug: Adding a hyphen-minus sign (-) to the blacklist blacklists all images

Expected Behavior: ?
Actual Behavior: All posts are blacklisted regardless of anything else that may be present in the user's blacklist
Steps to Duplicate: Enter "-" without quotation marks into your blacklist in a new line

Notes:
  • Other alphanumeric symbols don't affect the blacklist (such as ? or !)
  • Nor do non-existent tags (qwerty)
  • Adding "-" into a line with a tag already there has no apparent effect on the blacklist. Direction makes no difference either (- sex and sex - both do nothing)
  • Removing the space seems to treat the tag differently (sex- is treated as a tag (which removes sex from the blacklist, causing it to show up in posts, and -sex presumably does the same)

I think this actually makes sense in a weird sort of way, but I might be totally off the mark with this explanation. Let's try to break this down anyways.

We know that searching for "-tag" will display all images that do not contain "tag".

On the blacklist, adding "-tag" has the opposite effect, and HIDES all images that do not contain "tag". Think of it as the site automatically searching for all images that do NOT contain "tag", and then saying "I'm going to hide all those images from you.". So the blacklist is just like performing a search on the site, and whatever results are returned are the ones that the blacklist is going to hide from you.

With this understanding, blacklisting just "-" means that the site is going to hide all images that don't contain... nothing, since you're not specifying a tag. That means that everything is going to be hidden.

Of course, if you perform a normal search for just "-", you would expect it to return every post on the site, since every post on the site doesn't contain "nothing" (aren't double-negatives fun?). In actuality, it turns out that the search returns no posts at all, which, in the context of our previously stated blacklist logic, would mean that the blacklist shouldn't hide anything, since no search results are returned when searching for just "-". That's not what happens though; it hides everything instead.

Best explanation I've got for this is that the search system is accounting for people searching for just "-" and treats it as a tag, whereas the blacklist does NOT account for this, and assumes that if there's a "-", you're trying to negate a tag, even if there's no tag suffixed to the "-".

So actually yeah I'd say this is a bug. To the best of my knowledge, the search system and the blacklist system should always yield the exact opposite results of each other. But that's not what's happening here.

Good catch. :P

Updated by anonymous

Char said:
To the best of my knowledge, the search system and the blacklist system should always yield the exact opposite results of each other.

Things like pool:suchandsuch, score:..2, ischild:true, etc, don't seem to work when put on the blacklist.

Also, Tag subscriptions don't work the same as pasting the exact same string of tags into the search bar.

As in clicking my sub brings this up

Whereas copy pasting it in the bar brings this up

Or

Subscription

Search bar

I'm not sure if this is a bug or if it was made that way but just putting it out.

Updated by anonymous

Rainbow_Crash said:
Things like pool:suchandsuch, score:..2, ischild:true, etc, don't seem to work when put on the blacklist.

Metatags have to be specifically coded for blacklist use and more often than not that coding is more complex than the original, un-blacklist-version of it is, so that's why a lot of them don't work yet.

Updated by anonymous

Bug: URLs containing a closing parenthesis are not properly parsed
Expected behavior: URLs with a closing parenthesis at the end should work
Actual behavior: The close parenthesis is not parsed as part of the URL, which breaks some links. A close parenthesis within a URL is parsed as part of the URL, but one at the end is not.
Example:
http://en.wikipedia.org/wiki/(_)_(disambiguation)

Updated by anonymous

tony311 said:
Metatags have to be specifically coded for blacklist use and more often than not that coding is more complex than the original, un-blacklist-version of it is, so that's why a lot of them don't work yet.

I see. Thanks Tony, but also, I think that would be a really great feature to have

Updated by anonymous

Bug: Hidden forum posts link to a regular post in the moderator actions
Expected behavior: Hidden forum posts should go to the "comment hidden" page
Actual behavior: They go to an actual post
Steps to Duplicate: Go to the moderator action page and click on a hidden forum post.
Example, if forum post number 1234 was hidden, clicking it takes you to post number 1234

Updated by anonymous

slyroon

Former Staff

Bug: Going to users pages, is taking way more time then anything else does.

Expected behavior: Should take about the same amount of time, like any other page.

Actual behavior: it's slow

Steps to Duplicate: go to a user page

Updated by anonymous

Char

Former Staff

slyroon said:
Bug: Going to users pages, is taking way more time then anything else does.

Expected behavior: Should take about the same amount of time, like any other page.

Actual behavior: it's slow

Steps to Duplicate: go to a user page

We're well aware of this one. It's at the top of our priorities to resolve at the moment.

Updated by anonymous

Char said:
I think this actually makes sense in a weird sort of way, but I might be totally off the mark with this explanation. Let's try to break this down anyways.

That does make a lot of sense if you put it like that
Though, now I wonder which of the two (between the blacklist and search query) is treating '-' incorrectly

Good catch. :P

Was messing around with separators
:p

Updated by anonymous

slyroon said:
Bug: Going to users pages, is taking way more time then anything else does.

Expected behavior: Should take about the same amount of time, like any other page.

Actual behavior: it's slow

Steps to Duplicate: go to a user page

Don't forget they sometimes end up in a 500 error

Updated by anonymous

Maybe the - "bug" is a feature in disguise. What happens if you do like: "- -rating:s"? You could turn it into a whitelist. :p

Aurali said:
the json api isn't designed to be public, just for the javascript engine to use. This was like the guy who wanted to have the json api extended to show dangerous data off site.

So we're not supposed to use the JSON API externally?

To be clear, what I consider a bug isn't "the JSON API doesn't return this information" but "all APIs should give the same information and provide the same methods".

Updated by anonymous

Also, all non-empty lines before and after a line containing an h6 (and presumably h1-h5) disappear:

Here's some text you can't see!
There might be quite a bit!

*OM NOM NOM*

Lots of text here!
Oh no, where did it go?

There are two lines above and two below that text that have vanished. Only the first and last lines of the post survive, because there's a blank line between them and those that are eaten. (Looks like the lower blank line vanished too.)

Also my wifi is fucking horrible. Anything you can do about that?

Updated by anonymous

RenaKunisaki said:
So we're not supposed to use the JSON API externally?

To be clear, what I consider a bug isn't "the JSON API doesn't return this information" but "all APIs should give the same information and provide the same methods".

No, we don't care what you use. I'll still try and fix the JSON call not returning count.

Updated by anonymous

Alright, thanks for the clarification.

On a related note, why isn't DText parsed server-side?

Updated by anonymous

RenaKunisaki said:
Alright, thanks for the clarification.

On a related note, why isn't DText parsed server-side?

It is.

Updated by anonymous

Bug: Nested Dtext is handled oddly inside \

\

brackets
Expected Behavior: 'Correct' parsing
Actual Behavior: What

Steps to Duplicate:
Some [b

bold text[/b] here 1]
Some long text here

[b

Some bold text here 2[/b]]
Some long text here

[i

Some italicized text here 3[/i]]
Some long text here

Some [i

italicized[/i] text here 4]
Some long text here

A "link":http://e621.net here 5

Some long text here

-
Yup, if it gets implemented; metatag blacklisting would be really useful to have

Updated by anonymous

Rainbow_Crash said:/post?tags=sub%3ARainbow_Crash%3AMy_Little_Hit_List

Search bar

intentional.

Updated by anonymous

RenaKunisaki said:
I get the raw source in JSON. o.O

Oh, for API calls. It's probably better to actually offer the forum post as it is, unparsed, than to turn everything into e621.net specific HTML/CSS. Which does make parsing it a bit harder. I can give you the DText parsing code if you need it (it's written in Ruby).

Updated by anonymous

Bug: When deleting a subscription the notice bar shows nothing
Expected behavior: A message confirming that I just deleted a subscription
Actual behavior: This
Steps to duplicate: Delete a subscription from the Tag Subscriptions (one that you just create or you don't want anymore)

Updated by anonymous

tony311 said:
Oh, for API calls. It's probably better to actually offer the forum post as it is, unparsed, than to turn everything into e621.net specific HTML/CSS. Which does make parsing it a bit harder. I can give you the DText parsing code if you need it (it's written in Ruby).

That would probably help; at least then I can be relatively certain I'm parsing the same way as the server does. What I'd do though is to give the raw text (as "source" perhaps) and parsed text. But I can see if you're parsing it into classes that rely on your own stylesheets, that might not be very useful.

Also, this server seems to ignore/not send a number of useful HTTP headers, making for both a lot of potentially wasted bandwidth and a lot of failed downloads:

  • Neither of Content-Length or Content-MD5 are sent. This prevents clients from detecting a failed download. Annoying to someone with a poor connection, since you can't be sure an image downloaded successfully except by looking at it.
  • Content-Range is not honoured. This means when a client retries a failed download, it has to start over from the beginning of the file, rather than skipping the part it already has, potentially wasting a lot of bandwidth.
  • If-Modified-Since is seemingly not honoured (even though Last-Modified is sent). This means every view of a post has to re-download the image.

Updated by anonymous

Char

Former Staff

RenaKunisaki said:
post #236700 seems to have the wrong file size? Only 137K, but it claims some 593K...

No, you're looking at the downsampled image, not the original. You need to either click the "Download" or "Full Size" button to get the original, or disable "Show Image Samples" in your options: https://e621.net/user/edit

Updated by anonymous

Hmm, well something odd happened there. It looks like the downscaled version is actually the same dimensions, just in JPEG format? I thought sample images were only used when the original is >800px wide? Or I'm just confused and insane...

Updated by anonymous

RenaKunisaki said:
Hmm, well something odd happened there. It looks like the downscaled version is actually the same dimensions, just in JPEG format? I thought sample images were only used when the original is >800px wide? Or I'm just confused and insane...

What field (if that's what they're called) and/or post are you reading?
---
Try connecting it to the power outlet and see if the mayo is still white. If that does not work open the request (assuming http://e621.net/post/index.json?limit=1) in a text editor

Updated by anonymous

Well, the JSON shows:
width: 600
height: 800
sample_width: 600
sample_height: 800
file_url: /data/2a/cf/2acf...4807.png
sample_url: /data/sample/2a/cf/2acf...4807.jpg

And then post #87225 doesn't have a low-res version? o.O (sample_width == width, sample_url == file_url and so forth, despite being extremely high res...)

Updated by anonymous

slyroon

Former Staff

Bug: The website randomly goes to the 500 error page and a few seconds later it works normally

Expected behavior: there shouldn't be problem

Actual behavior: goes to the 500 error page

Steps to duplicate: i don't know it just happens randomly

Updated by anonymous

Char

Former Staff

RenaKunisaki said:
Hmm, well something odd happened there. It looks like the downscaled version is actually the same dimensions, just in JPEG format? I thought sample images were only used when the original is >800px wide? Or I'm just confused and insane...

It's 800px wide OR tall. The text on the setting says "If enabled, images that are wider/taller than 800px will be replaced with a reduced-size image." It looks like it actually kicks in right at 800px though, but I'm not terribly worried about it; we're talking about 1 pixel.

Updated by anonymous

Bug: 500 Internal Server error when trying to change avatar

Expected Behavior: No error.

Actual Behavior: 500'd

Steps To Duplicate: Attempt to change your avatar.

Updated by anonymous

Char

Former Staff

Blaziken said:

Bug: 500 Internal Server error when trying to change avatar

Expected Behavior: No error.

Actual Behavior: 500'd

Steps To Duplicate: Attempt to change your avatar.

Works fine for me. Which post did you try to change your avatar to?

Updated by anonymous

Char

Former Staff

Blaziken said:
Tried to change it to http://www.e621.net/post/show/237982

...

And then it works again. Guess it was transient. Sorry!

Yeah, just bad timing is all. The site does occasionally experience brief 500 errors, I think usually whenever it needs to run some script/process. The outages are usually quite brief, but bound to be seen by some users anyways since we have so much traffic.

Updated by anonymous

Char said:
Yeah, just bad timing is all. The site does occasionally experience brief 500 errors, I think usually whenever it needs to run some script/process. The outages are usually quite brief, but bound to be seen by some users anyways since we have so much traffic.

Traffic? Great. I'm late already ლ(ಠ益ಠლ)

Is something wrong? (do servers have cache?)

Updated by anonymous