Subtle changes, bugs and feedback

Hi David,
Quick heads up but in a recent change it seems that it isn't working on my work PC so the old IE version. It was fine last week so something you did over the weekend perhaps has put the formatting off kilter

Nexus 4?

Yup - looks like its down to filesize - it was >3mb
A friendlier error might be handy :)
If I try a smaller one then its fine.

on my work PC so the old IE version.

There are 3 positions in this dilemma

1. "do some work"
   
2. "get a modern browser"
   
3. Other opinion held by people who don't run websites.
   

I've just recreated that.

Weird indeed.

It seems to happen if you send consecutive messages using the same title within a short space of time.

bookmark icon on chrome browser is now a..... 'SPOK!!!!

the horror ;-)

1 Attachment

Yes, it isn't very helpful.

The whole process of uploading images needs a bit of an overhaul to be simpler and do things like process the orientation info correctly.

I have an odd error in the search box sometimes. It happens if I add special fields to my query in nonstandard locations. Like this search for party with my authorID: https://www.lfgss.com/search/?q=party+inTitle%3Atrue+sort%3Adate+authorID%3A58270

If I then click on one of the boxes to modify the query it loses the author id.

I've just had weird thing, I tried sending separate messages to two people about a classifieds ad, and it ended up making a group conversation with all 3 of us with both messages, one after the other. How??

Fixed.

We have a de-duplication checker, and it thought the two messages were duplicates.

When it encounters duplicates, it gives back the original one.

What this really means in terms of HTTP requests:

1. Create message, get given ID = 1
   
2. Add recipient to message 1, get given OK
   
3. Add comment to message 1, get given OK
   
   

Then the second message goes like this:

1. Create message, see that it's the same title and author as message 1, get given ID = 1
   
2. Add recipient to message 1, get given OK
   
3. Add comment to message 1, get given OK
   
   

The problem was that dupe checking is too aggressive. It doesn't consider different recipients or comment, at the point it does the checking it's looking at title + author. It also looks for dupes within the last 5 minutes on this basis.

The dupe checking is there to handle people hitting submit multiple times, or people cross-posting an advert on multiple forums. 5 minutes is probably reasonable to handle both those scenarios for forums, or comments in conversations... but is unreasonable for messages.

Fix: Reduce dupe checking to only look for dupes in the last 5 seconds.

It will still de-dupe if you submit multiple times, but won't if they are 5 seconds apart, or have a different title.

I do keep falling into the trap of trying to work out how to use this new forum in the same way I used to use the old one.

Boo!

FYI, just noticed in the CC thread, the list for jerseys in a post before the move has inadvertently tagged a member called "jersey"

http://www.lfgss.com/comments/10209212/

None of which really appeal and the issue is when I do this on my phone it just looks like I'm texting

That's funny.

Not a bug though.

Yeah, guess so. Thought you'd want to see it though.

When the page is requested, we update the read entry for your user. It's possible (but unlikely) that failed, so will check the logs.

@Velocio

I am now wondering about what I was seeing, as it doesn't seem to have happened again.

I do notice that when clicking on some links: https://www.lfgss.com/conversations/242376/?offset=525#comment11776451 for example, the anchor seems to be at the bottom of the page, rather than the top. i.e. it took me to the posts just preceding comment11776451 rather than to that comment and those after it....

edit When I then go and click on that link in this post it takes me to comment11776451 at the top of the page...

Other threads I click on (all from "today") seem to be anchoring at the top rather than bottom.

it took me to the posts just preceding comment11776451 rather than to that comment and those after it....

That might happen if, in the posts preceding the anchor point, images that have not yet loaded then load and move the page after the browser has already anchored.

There is no elegant fix for this.

In an ideal world I'd rewrite all IMG tags to include the height and width... but when images are third party, that is totally infeasible.

I dont think that this was the case here though, I know what you are describing - it taking you to one point, then images rendering and then moving - this was not it - images had rendered and I didn't get moved - see the images attached - 1st one is what it took me to, rather than the 2nd (which is what it now takes me to and what it should have taken me to originally)

It was just like it was pictured in the first attachement - with DJ's post being slightly cut off - as if it had anchored the post #544 just below the bottom of the page...

I will keep an eye out to see if I can spot it happen on pages that don't have any images on.

2 Attachments

Speedy work, cheers!

Hah! I tend to drop things and jump to it when it's something to do with private messaging.

Can we have a "next" button please. A big one so it's easy to hit.

Also it's not 1994 anymore. Half my screen is grey emptiness. Please use the whole screen: particularly when it is wide.

It may not be 1994 anymore, so why is your browser taking up your whole screen? You could be running so many more programs (or apps as we call them these days) in the space next to your browser window.

Please also integrate the login process to the current page of the website. Pop-up windows are difficult for anyone with a disability. I use software to automate logins, and it doesn't work with your site. I also use automatic software for clicking "next". Opera does this automatically on many websites so one can just page through forums with the spacebar.

Microcosm runs as an API, in which the frontend client (the website you see) talks to the API.

There is nothing at all that prevents other clients talking to our API. That could be 3rd party mobile apps, forks of this website that have been highly customised, whatever it is... you should be able to sign-in.

And those different clients should never have access to your password.

What I am saying is that we who run Microcosm trust you who sign-in, but we don't trust the client that you sign in to.

That is the big reason why sign-in is not a deeply integrated part of the main web page, and isn't just a couple of form fields. It allows us to support different clients in a way that will always protect your account.

Even if we did not use Persona, we would need to build something very close to what Persona is. It would have to be on a different domain (one that we trust), and it would have to be served as a popup or new window (the client should never have access to the password, so it cannot be a form field on this page), and once you have signed in an access token or some grant of permission to now act as if the site is you needs to be granted to the client.

With all of that in mind, knowing we're roughly going to stay with this model even if we change individual bits to solve problems... could you share what software you use, how you use it, what the limitations are, and how it proves to be inaccessible for you.

We may be able to solve those things, even without changing the way the fundamental process works.

I wish it was 1994. Don't do it Kurt!

It was clearly his wife.