Subtle changes, bugs and feedback

I had also ticked Follow on that Montpellier thread but it was not listed in my Following threads - until I posted in it just now.
One of the reasons I don't like the @ reply thing and really, really want to opt out of it is that it lengthens my list of 'followed' threads and makes scrolling through them to find one a bit of a pain. A good thing about sticky threads being in yellow is that they are easier to find, though.

@wil.....

just kidding.

@willmellin.....

so close...

Pah, his best stuff was posted by @deleted

I don't know if this has been mentioned.. in the 'Today' page it lists new users as well as new threads, bit weird?

But for today, the dedicated security and ops people that Persona has beats a single me, needing to sleep, and not being available 24/7.

Mozilla is no longer developing Persona, has moved staff away from the project and while it is still providing minimal support, this is for the existing hosted service (downtime, critical bugs and the like). Mozilla has promised not do decommission Persona this year.

I know people who work for Mozilla. Persona is a dead duck. Now is a good time to be planning alternatives for the near future.

This I know.

Yet their "minimal support" still beats what Microcosm has today. We are 2 and, whilst Persona may not have achieved the original goals Mozilla have, they are providing support (and have been very fast to react whenever we've needed them to) and are actually still improving the product.

Yes we need a long-term plan. Yes we're likely to have to build our own.

But the very basic fact remains: If we spent months building an identity provider, Microcosm would already be dead as a company and product. It would have been the wrong decision by a country mile.

If our resources remain tight, then our future path may be a self-hosted instance of Persona, with the email bridges disabled (for our use-case that would suit us better anyway). But if we have the resources we would build our own identity provider... it would look very much like Persona, but we'd obviously be better placed to maintain it and to integrate it more deeply and invisibly.

Finding it a bit annoying that when somebody replies to my posts with loads of pictures in their post it fills up so much of the following page that I miss things, is there any way for me to hide that? I think it's going to get very annoying because I'm following loads of picture based conversations.

If not is there any way to add a 'keep reading' option to long posts, or will I just have to get over it and use the forum differently?

wow the red border to the black logo is quite macabre...

Its awful. Sorry. Really bad.

The darker grey is sufficiently dark that you shouldn't need to stroke the text.

Plain black it is then.

I do wonder about devices that cannot really show that type of contrast though.

Plain black works well. You could lighten up the grey of you're worried about visibilty on different devices.

The grey stays.

Though I did wonder about SVG drop shadows behind the LFGSS to give a white halo to it.

It certainly doesn't pass WCAG guidelines at a contrast ratio of 2.07:1... (needs to be at least 4.5:1 for normal text and at least 3:1 for large text), but the guidelines do also say that logos - which it of course it is - aren't subject to the minimum contrast rules.

So as far as accessibility goes, if you regard that as a logo rather than text, it does meet all relevant standards. Through a loophole, yes, but it meets them.

Finding it a bit annoying that when somebody replies to my posts it fills up so much of the following page

This. Do I really need 3 separate items in 'Following' when somebody replies to my post, @ mentions me in that reply, and in so doing adds a new post to a thread to which I'm subscribed? Some kind of filter would be good, so that I don't get 3 notifications for one post.

Which of those things is more important?

Does a @mention trump a reply? i.e. should a mention mean that the reply doesn't show up in the following?

Priority is probably "Which is more personal?", so @mention highest down to new post in thread lowest, and then fall back to the next lower priority if the user has disabled notification of the higher priority case, assuming that function is eventually going to be made available.

Well I would consider removing the dupe of @mention and reply.

But if I removed the "new post in thread" then the prior comment in the thread would place the thread in the list anyway... and at the same position because it uses the last modified date for the thread, which is when the comment count change... the post we're ignoring.

There's no practical way for me to remove "new post in thread"... but the dupe of @mention and reply can be done.

black logo on grey looks good, way better. I think because it isn't permanent, the low contrast is ok.

definitely no glow or drop shadow.

Oh, Dan...

What about a glow shadow?

I've had this error three times: twice trying to "@" someone in a reply and once trying to post a "plain" link.

I got around it by posting without "@" then editing the post and just tried posting the link again.

3 Attachments

Had you opened lots of tabs, read them, and then returned to the first one to read it?

The CSRF token it speaks of is a measure to prevent hacking: http://en.wikipedia.org/wiki/Cross-site_request_forgery#Synchronizer_Token_Pattern

Whilst this works really well, it also introduces some constraints. Namely that the sequence of actions must roughly follow each other, and so any creation of content must follow the reading of the prior stuff.

If you take too long (i.e. leave a comment window open for a good while, make a cup of tea and return) it will delete the older tokens and cause that error.

And if you do lots of other things between reading and replying (i.e. open lots of other tabs and read those first) then as it will only store the last few tokens for a user, the newer ones from other tabs will cause the deletion of these older ones.

Basically... do you see this error immediately when you view a single page and reply... or do you do anything else between viewing the page and replying?

Again, not sure if already raised- I miss the hover over thread title function which would show you the first few lines of the post, it was useful when titles were a little ambiguous.