Subtle changes, bugs and feedback

Some kind of error this morning?

Hosting company decided to restart machines for some reason. One of the services didn't come back up, which caused it to overload immediately.

I've tidied up after them.

Cheers bossman

There would seem to be a bug- I'm not able to make searches in, or view my past threads in the classifieds parts forum. I can log into a second account and do searches as normal.

Did you ignore it?

Have a look on this page: https://www.lfgss.com/ignored/

Yeah, that was it. I'm glad that's sorted out, so thanks.

Yes it was the ordering, its a minor thing but gets me every time.

Note to self... the API is doing the right thing: https://lfgss.microcosm.app/api/v1/microcosms

i.e. for Cities & Places: Manchester > Birmingham > Cambridge > Norwich, etc which is correct.

It is the Python web front end that is doing the wrong thing.

a python dict by any chance?

The ordering (or lack of) has bitten me a few time when using saltstack...

Yup, I think it is.

Will not fix in the near future... will just wait until I replace all of the Python with Go.

For some reason the Any question answered... thread has disappeared from my 'Following ' list. It also doesn't appear when I search for question ( I get other hits). I'm not sure if this is only a work issue - I'm using Chrome Version 43.0.2357.124. Is it simply a shit browser? Everything else seems to be working.

Did you ignore it?

Have a look on this page: https://www.lfgss.com/ignored/

Did you ignore it by mistake?

Bah! Refresh fail

Thanks - it turns out I did. I didn't actively do it - but that's now solved the issue. Weird. I'll know what to check for in future. Thanks!

I wrote a comment containing text between a "<" and ">"character, when it posted only the text preceeding the first "<" character displayed. Editing the "<" and ">" characters to

< ... >

Resolved the issue.

Everything is working fine.

Our comment format is Markdown, which includes HTML, and your use of > & < look like invalid HTML, which is then stripped from the response for safety/security.

Yeah I thought you'd be sanitising the input, but wouldn't it be nicer to HTML encode "special" characters like that? Not a massive issue though tbh, the whole comment was there when I edited the post.

If I did that too early then you could never put HTML into a comment, and if I do it too late then I break all of the HTML that is in a comment.

When I currently do it is the best time, but has the edge case that including both > and < (in the other order) may break the post. But then... I show you your post immediately after you make it, so figured that this edge case is minor, and you're shown when it occurs and can edit accordingly.

HTML escaping does work if > precedes < and isn't then followed by an >

Note I had to write that like this:

HTML escaping does work if > precedes < and isn't then followed by an &gt;

Fair enough, and that explains why people can use > (as below) without falling foul of it like I did. Keep up the good work!

People complaining about things that aren't issues>>>>>>>>

Didn't know where to put this, but I had this thought about making more efficient use of the top of the mobile version of the website:

Don't know how much control you have over this, but it would free up enough space for a whole nother thread/row.

^ that's nicer to my untrained eyes.

Now try that with this URL: https://www.lfgss.com/microcosms/548/?offset=50

1 Attachment

I knew there was something I missed! Good design.

It's also the same component that shows within a thread, and works even on the Bike Porn thread where the page numbers are ridiculously large.

Just a shame the default view is either the first or last page, and it then looks like it is wasting space.

I wish I could easily, and accurately, detect collision in CSS and then do avoidance based on some set of rules.

When I click on 'in reply to @xxxx' it used to take me to the original post right? Seems to be broken.