Rainboom Dash 
Rainbooms4Ever
I NEVER use the fetcher… I always download the image first and then upload
Report site bugs here
M.W. 
Sorry, my bad. It previews the smaller image indeed, and I thought that it was the image that was being uploaded. But I just checked the fetcher’s response I should’ve checked it before reporting the “issue” and it’s grabbing the right url. My apologies.
In love with a blue pony
@M.W.
The fetcher still uploads the largest version that’s available, it just previews the smaller image. I think this is to reduce bandwidth and memory consumption.
Sorry, my bad. It previews the smaller image indeed, and I thought that it was the image that was being uploaded. But I just checked the fetcher’s response I should’ve checked it before reporting the “issue” and it’s grabbing the right url. My apologies.
NamelessNP 
What’s going on here? Lately I see this happen occasionally when changing pages on the site. I briefly see this before the next page loads.
Starlight and Sunny Fan
What’s going on here? Lately I see this happen occasionally when changing pages on the site. I briefly see this before the next page loads.
Rainboom Dash
Rainbooms4Ever
@thatguy
Probably internet connection issue
Sometimes pages fail to load properly… Just reload :P
It’s not their fault
Probably internet connection issue
Sometimes pages fail to load properly… Just reload :P
It’s not their fault
NamelessNP
Starlight and Sunny Fan
@Rainboom Dash
No no, I see stuff like this flash by real fast between page transitions. Nothing’s failing to load.
No no, I see stuff like this flash by real fast between page transitions. Nothing’s failing to load.
Anonshy 
Busy - May not Respond
@thatguy
I think I reported that exact problem months ago and it keeps happening. Usually happens (at least in my case) when you log in and it redirects you to the comment page of the image that you been watching but with a different URL. Try to acess here and you’ll see the problem.
@Rainboom Dash
Yes, it’s their fault :P
I think I reported that exact problem months ago and it keeps happening. Usually happens (at least in my case) when you log in and it redirects you to the comment page of the image that you been watching but with a different URL. Try to acess here and you’ll see the problem.
@Rainboom Dash
Yes, it’s their fault :P
Exedrus 
@TheAnonShy
Might be related, although thatguy’s image isn’t of a comments page. It looks like a regular image post page without the CSS. I’ve had a few instances when CSS wouldn’t load initially (although I’ve only gotten this when loading the front page) which leads to the strange formatting in the screencap, but things usually fixed themselves after refreshing the page.
Might be related, although thatguy’s image isn’t of a comments page. It looks like a regular image post page without the CSS. I’ve had a few instances when CSS wouldn’t load initially (although I’ve only gotten this when loading the front page) which leads to the strange formatting in the screencap, but things usually fixed themselves after refreshing the page.
DoublePipe 
@thatguy
That is what the site looks like without any styles applied. You can see that it is trying to load more files down in the corner. Your browser would normally cache the stylesheet file so that it doesn’t have to load again, but what you’re seeing suggests that it’s not doing so properly. You can try clearing your cache or potentially disable any extensions you’re using which might help resolve that.
@TheAnonShy
As Exedrus suggests that is a different issue, though I can understand why they would appear to be the same. Our comments are located on a separate page which is not meant to be seen on its own - you’re not meant to be redirected to it. We’ve recently talked about ways of rendering comments as part of the image pages again, which should take care of it.
That is what the site looks like without any styles applied. You can see that it is trying to load more files down in the corner. Your browser would normally cache the stylesheet file so that it doesn’t have to load again, but what you’re seeing suggests that it’s not doing so properly. You can try clearing your cache or potentially disable any extensions you’re using which might help resolve that.
@TheAnonShy
As Exedrus suggests that is a different issue, though I can understand why they would appear to be the same. Our comments are located on a separate page which is not meant to be seen on its own - you’re not meant to be redirected to it. We’ve recently talked about ways of rendering comments as part of the image pages again, which should take care of it.
Brokedownandmadeone 
BigThirsty ponybooru.org
I think I found one.
texttexttexttexttexttexttexttexttexttexttext
texttexttexttexttexttexttexttexttexttext:
texttext texttexttext texttexttexttexttexttexthttps://derpicdn.net/img/view/2017/4/8/1406985.pngtexttexttexttexttexttexttexttexttexttext:
texttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttext:
te x-t -texttext-text-textte-xttextte-xtt-ext-text-https://derpicdn.net/img/view/2017/4/8/1406985.pngtexttexttexttexttexttexttexttexttexttext:
No matter how you format everything in between, the strike through refuses to work when starting immediately after the starting quote. The only time it works, is if you have a text, space, then start the strike through.
@TheAnonShy
Slower internet connection here. Can confirm it initially loads like that before it self-corrects sometimes. Doesn’t happen all the time. Probably has something to do with the load order for the page, and the script loading after some other files.
@TheAnonShy
Slower internet connection here. Can confirm it initially loads like that before it self-corrects sometimes. Doesn’t happen all the time. Probably has something to do with the load order for the page, and the script loading after some other files.
Yoshimon1 
It isn’t really well documented anywhere iirc, the syntax quick reference only describes [==stuff you don’t want textile to parse], but you can do the same thing and just surround your text with [] if the Textile parser doesn’t correctly format nested stuff.
So in this case,stuff you want textile to strikethrough== forces the strikethrough.
Until the bug is fixed (if it’s actually a bug worth fixing and not just Textile being Textile), you can use this as a workaround.
yay(){ yay|yay & };yay
texttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttexttext:
It isn’t really well documented anywhere iirc, the syntax quick reference only describes [==stuff you don’t want textile to parse], but you can do the same thing and just surround your text with [] if the Textile parser doesn’t correctly format nested stuff.
So in this case,
Until the bug is fixed (if it’s actually a bug worth fixing and not just Textile being Textile), you can use this as a workaround.
SuperSupermario24
fluffy sylveon
@Yoshimon1
Indeed, and you can use the without brackets to escape textile parsing as well, like this== (quote to see).
I really think the site needs a more comprehensive/clear documentation on how it works.
Indeed, and you can use the without brackets to escape textile parsing as well, like this== (quote to see).
I really think the site needs a more comprehensive/clear documentation on how it works.
Some Pacifier Pone 
This!
um???? lmao???
I really think the site needs a more comprehensive/clear documentation on how it works.
This!
Brokedownandmadeone
Huh. Didn’t know you could just bracket the textiles separately for them to do it individually for the desired effect. Neat. That’s about the only thing that’s not mentioned in the Syntax quick reference.
BigThirsty ponybooru.org
@Yoshimon1 @SuperSupermario24
The reason I brought it up was because I wanted to use strike through at the start of the quote.I knew how to negate it with *_^equals signs^_* already. It was one of those head-scratchers that I figured I should mention.
Looking back at my quote, I realize you guys probably brought up the equals sign because it didn’t process the separate strikethroughs separately like I thought it would.
That’s an odd workaround.
The reason I brought it up was because I wanted to use strike through at the start of the quote.
Looking back at my quote, I realize you guys probably brought up the equals sign because it didn’t process the separate strikethroughs separately like I thought it would.
That’s an odd workaround.
te xttexttexttexttexttexttexttexttexttext https://derpicdn.net/img/view/2017/4/8/1406985.png -texttexttexttexttexttexttexttexttexttext:
Huh. Didn’t know you could just bracket the textiles separately for them to do it individually for the desired effect. Neat. That’s about the only thing that’s not mentioned in the Syntax quick reference.
Yoshimon1
Can confirm. The tl;dr tag page itself is fine, but when you click Next to open page 2, you get redirected to the home page.
yay(){ yay|yay & };yay
Semicolons aren’t encoded properly in some linksThe example is the tl;dr tag. Page 1 ishttps://derpibooru.org/tags/tl%3Bdr, page 2 ishttps://derpibooru.org/tags/tl;dr?page=2&q=tl%3Bdr.tags/tl;dr?isn’t a valid url.I wasn’t sure if this goes in Site or Tags discussion since as far as I know it only applies to tags.
Can confirm. The tl;dr tag page itself is fine, but when you click Next to open page 2, you get redirected to the home page.
Zeb 
Tag-Bot
@Yoshimon1
Oddly enough, if you search for the tl;dr tag, the other pages work fine. It’s only when you’re starting from the tag page itself.
https://derpibooru.org/search/index?page=2&q=tl%3Bdr
Oddly enough, if you search for the tl;dr tag, the other pages work fine. It’s only when you’re starting from the tag page itself.
https://derpibooru.org/search/index?page=2&q=tl%3Bdr
dt 
No Thank You
Mouse-scrolling does not seem to work for me on this website. Might be my hardware, but it works fine for other websites.
Prof.NightJack
Gizmonics Scientist
I’m guessing the Chrome scrolling bug differs by users as it happens to me on a few other pages but so far only once on this site.
Yoshimon1
yay(){ yay|yay & };yay
@Zeb
I’d try it with other tags, but this is the only one with ; and more than one page of results. Speaking of, if you manually enter the correct url to page 2 and then click Prev, the same thing happens. Also with First/Last.
For some reason, the URLs created by the First/Next/Prev/Last buttons unescape the escaped %3B back to ; and break everything. Which definitely shouldn’t happen, because there’s no reason to touch the first part of the url after adding/removing the ?page=x…
I’d try it with other tags, but this is the only one with ; and more than one page of results. Speaking of, if you manually enter the correct url to page 2 and then click Prev, the same thing happens. Also with First/Last.
For some reason, the URLs created by the First/Next/Prev/Last buttons unescape the escaped %3B back to ; and break everything. Which definitely shouldn’t happen, because there’s no reason to touch the first part of the url after adding/removing the ?page=x…
Interested in advertising on Derpibooru? Click here for information!
Help fund the $15 daily operational cost of Derpibooru - support us financially!