Subtle changes, bugs and feedback

Also would it be possible to make the following page less cluttered / more usable with just a few tweaks?
Especially the double entries are dumb (when there's new activity there's an entry, when someone's "mentioned" you there's another - one would shurely be enough as if one is following the thing one just goes to the first new post and takes it from there).

the double entries are dumb

Triple entries are dumber, when somebody replies to your post in a thread you're following and mentions @Franz Beckenbauer

Interesting you should say that, I got this when I was replied to in the spotted thread:

As you can see one is the top of following, with the comment seven minutes ago, but the spotted thread was actually several entries down (although still with "7 mins ago") after several entries that were later?

Ps isn't Tripplechickle entry the fault of the poster (triple entry is perverse)

2 Attachments

Triple entries are dumber

Indeed, was about to mention this @mdcc_tester !

Where possible, anything we embed will now be served over https.

I've contacted the few providers for whom this isn't the case, and hopefully they will add https soon.

What about having a separate sales bit for London sales. It would be nice to browse sales threads in the knowledge it can be collected from the London Fixed Gear and Single Speed community rather than posted from miles away.

You mean a local shop for local people?

If we are going to do that, can we have North London and South sections, I ain't riding to Essex, because someone thinks just because it's the london borough of havering that's an acceptible place to meet.

;)

Ok, who broke the forum? I don't even know where the hell I'm even posting.

I broke the forum momentarily by enabling HEAD requests.

The second part I cannot help with.

At least I have not broken the forum.

And if you're wondering why the HEAD requests...

I'm scanning the forum for malware and links to bad places.

The scan works by crawling from the root page, and indexing all links on a page, and ignoring /search /huddles and /comments. It then queues those links as HEAD requests, and if the HEAD returns a content-type of text/html it knows it can then GET those pages and index more links. On every page it crawls, it then finds every link to anything at all and checks them against various blacklists.

{"fqdn":"http://www.lfgss.com","started":"2015-06-20T19:28:08.645145731+01:00","inProgress":true,"scannedURLs":6388,"headReqs":263,"getReqs":120}

So 263 links within the site I've made HEAD requests which identified 120 web pages, and on those 120 pages I've found 6,388 URLs that I've scanned.

I've not yet turned up a single piece of malware.

I gotta do something on a Saturday evening.

Thats good.
Thought it may have been the weather.

Wasnt there once a page telling user to have a cup of tea?
Did it anyway.

There... all fixed.

Ooh, now it's faster too.

Should've perhaps turned off dev mode ages ago.

Does disabling dev mode involve enabling SPDY? I'm getting strange errors when displaying content. Images hosted on lfgss are being displayed intermittently in FF 38.0/Ubuntu 14.0, Chromium 43.0/Ubuntu 14.04 and Chrome 43.0/Android 5.1.1.

For example, on this page, HoKe posts an image of the final build and although the image appears to download, it isn't displayed. If I load the image in a new tab it will display correctly.

FF gives no error messages, Chromium says:

GET https://lfgss.microcosm.app/api/v1/files/069a24eb5ceb4edf0792cce4fa049c8909934284.jpg net::ERR_SPDY_PROTOCOL_ERROR

Disabling SPDY in FF fixes the problem.

SPDY has been enabled since it was available in nginx and no change was made to that yesterday.

I use Chrome (not Chromium) on Ubuntu and see no issue with the image above.

Perhaps something on your network is interfering with the traffic?

Possibly. I had the problem on both 4G and my home broadband, but no one else seems to have the issue. I'm in Australia, which shouldn't make any difference, but you never know...

I'll check at work tomorrow.

Actually, does it work now?

I'd enabled gzip on all API requests and that may have broken some images for some clients.

Yes, that seems to have fixed it across the board. Strange.

And it was just some images that broke, right?

That's all I noticed, yeah. Some (but not all) images served from lfgss; and always the same ones failing to load.

Strangely, loading an individual image url caused the image to display.

This has made a difference for me. Some pictures weren't displaying on my android phone, but they are now.