Sorry, I meant to address this a while ago. This is just how phpBB does tags — if you click any other bbcode button, it wraps the entire paragraph as well. It's weird, and I can look into fixing it, but it's not a priority right now.

Just curious, does anyone know what was up with the downtime earlier today? I don't think it's worth creating a thread about, so I'm asking here instead.

We're not exactly sure and looking into it.

I have no bugs to report

your "email a user when they are banned system" worked perfectly

good job whoever did it

There isn't such a system right now; it's being done manually.

well thanks for putting in the effort then

[/spoiler]

[spoiler] [/spoiler]

Yeah i've mentioned this a few times. It was wrecking my guides and such.

Just name them spoiler if you have no name for them. Works for me.

Noted. Thanks for pointing this out, guys.

Nice workaround. Thanks!

The [img] tag seems to have a bug. When I posted here, most of the pictures I included loaded fine, but the OOTS and Erfworld pictures (both from Giantitp.com) didn't; though when I take the image location and load it in a separate tab, the OOTS picture loads fine (the Erfworld one still won't).

I don't actually what the problem is, the preview worked fine last night but then this morning I found it to be a problem. Maybe it's the way the website in question handles data?

I was on my home laptop, Windows XP (I believe SP2); using Firefox *checks version* 24.0; using the now-default dark red theme.

TPManW is who brought my attention to the issue, and I don't know what he's using.



Separate issue: there may or may not be an issue with the quote system redirecting straight to the user. Barnellos had an issue quoting me in this post and removed my name with my old nickname after he


I don't know what exactly he had issue with, but I thought I'd bring it to your attention.

Weird. I'll check it out.


Thanks for doing so. I have had no problems with it (as you can see, quoting you works fine in this post) but there may be an issue somewhere...

The img tag thing might be a block on the GitP / Erfworld side to prevent hot linking of images.

Thanks for doing so. I have had no problems with it (as you can see, quoting you works fine in this post) but there may be an issue somewhere...[/quote]I haven't had any issues with it, either; but it may just be a small bug that my post somehow induced (maybe because I autocarded as well?).


I thought that may be why, but I don't know how to check. I thought maybe someone else might have experience with GitP and would know, since both images come from that website.

This is indeed what is happening: the server is returning "403 — Forbidden" errors when images are requested from sites other than giantitp.com.

Fun fact: if you manually set the Referer: header to "http://www.giantitp.com/" it lets you get the images. The trailing / is important!

I'm not sure I follow. This is exactly how I tried posting an image of OOTS:



As you can see, I copied and pasted what was in my address bar, which included http:// and the last / after the .com. As far as I can tell, it should work, though I do not know the ins and outs of coding like you do. I'm probably misunderstanding something -- you know how to change the address to fix it, yes?

Well, I have tried quoting that exact post, from both the main thread view and the 'review topic' panel in the post editor, on every browser I have access to, and it has worked properly every time, and looking over the code doesn't show anything wrong. I believe Barinellos when he says he was having problems, but if I can't reproduce it I can't fix it.


Oh, sorry, that wasn't actually meant to be helpful, just something I found amusing. My bad for being unclear.

tl;dr: Unfortunately, referencing images from sites like GitP that block hotlinking will not work no matter what we do.

The long version:
The usual way for sites to block hotlinking is to add a filter that looks at the Referer: header in the HTTP request[1]. The value of this header generally corresponds to the site on which resides the page requesting that image. So, for the image in your post, the referrer would be "http://www.nogoblinsallowed.com/". The GitP server looks at that header, notices that it's not "http://www.giantitp.com/", and says, "No, you can't have that file!" Hence the error.

There is not anything we/I can do on this end to change the value of that header; the browser handles all that. So there's not anything we/I can do to make those hotlinked images work. And, honestly, maybe that's for the best — GitP forbids hotlinking because it costs them bandwidth and server load (and thus money) when people hotlink images from their site, and they get nothing in return (ad revenue, etc.).

That said, there are some tools that let you send out requests with arbitrary headers. So if I run

it can go out and get the image, because the header value is right. However, if instead I do

it gives me a "forbidden" error instead.

Oh, okay. Thanks, Welder.

I think what I'll do then is just edit the links directly to the pages instead of trying to post an image.

I was afraid that the problem wouldn't be reproducible, but I'll report any other quote problems I catch wind of. Thanks very much for trying!

So apparently my drunk message got set to a bunch of people I did not intend
I checked and the send to list it wasn't wrong
What happened