So as the topic thread says, I'm noticing that images are broken in the forum as of late.
At least on both my desktop and laptop. My phone still shows them just fine.
It seems to be the images that people have uploaded onto Comic Fury itself that are the ones showing as broken despite when you click to see the images on a separate tab/page, they will show up.. Images from other places seem to show up fine.
Well, right away my at the bottom of my posts is supposed to be my comic's banner image/link to the comic and all that's there is the broken image symbol with thw word 'image' next to it. A lot of peoples' signatures are showing like this to me. The ones that aren't, aren't using Comic Fury as their image host.
Looks fine to me in 3 browser environments: Firefox/Windows where I'm logged in, and two which are completely fresh: Chrome/Knoppix and Firefox/Knoppix. What I have seen in the past is porn blockers blocking some innocent comic material. I don't remember if that applied to anything on Comic Fury or not.
Using this very thread as an example, here's what I see looking at some peoples' comments. Almost all broken images...as I'm sure this will be to many people it sounds like unless you click to see it in another tab or page.
okay so I figured it out, it looks like the latest chrome update may block mixed content, i.e. HTTP images embedded in HTTPS pages. This isn't a problem on the webcomic sites themselves, but if the images are embedded elsewhere, chrome may block it. The webcomic sites are still on http, because dreamhost, our hosting company, doesn't support wildcard ssl certificates, this is one of the reasons we're planning to move servers. I was actually going to work on some monetization stuff next, to increase our server budget a bit more before we make the move, but this kind of throws a spanner into that plan a little bit.
So I think there is actually a way to get https on webcomic sites to work now that we're on a private server, but it involves doing the dreamhost equivalent of voiding the warranty, which means they may be more hesitant to admit fault if anything goes wrong on the server in the future. I'll also have to figure out exactly how to do it and make sure that I won't accidentally break anything. So uh, I'll do some research. I think if you click on the little i next to the URL bar, you may be able to allow mixed content in the interim