Wedge

For years, I've held an account at my first proper paid webhosting service, and they've run my email ever since - that's since 2003.

When I joined them, everything was fantastic, service was prompt and I couldn't recommend them enough. But over the last couple of years they've really gone downhill, and today was the final straw.

For 24 hours straight, the email server's been down, the web-mail login is broken because they didn't set it up properly, that is assuming I'm willing to overlook the fact that they're using self-signed certificates for all their servers... I say servers, but I think they only have one server these days.

Since my old old old site is virtually non existent anyway, I'm now in the process of migrating the email to another provider, and moving the website to my VPS. Given the hoops I've had to jump through to get my old email archive given that their mail service is broken, I can see today is going to be a very, very long day :(

Funnily enough, I did virtually the same ;)

Anyway. DW S6E10.

Haven't seen TW EP 9 yet, but I'm hearing that it's an RTD cliffhanger which means that it's probably going to suck because he's not really a story person, he's a characters person.

topicseen is mostly a legacy item IIRC, if it doesn't affec behaviour, ditch it.

As for new, that one's required. #new anchors the page in the browser, but it won't get you to the right page of a multipage thread, while topic=x.new will get you to the right page.

I don't know if that's the case for sure, but that's the only explanation I can come up with. Benchmark it :P

Remember, certain operations apply in certain ways under certain circumstances. This is about the worse possible circumstance to deal with where the odds are stacked against you: you're doing everything on disk, drawing more file I/O that's blocking other requests and so on.

I can only surmise that it's a performance thing, because if it wasn't, MIN would be much more logical.I'm not trying to worry about it as a regular user. You want to know why it's misbehaving. If you tweak those settings, does it behave as expected?

I'm not disputing that it's needed, simply explaining why it wasn't done before ;) The plan is to make it so the list of columns displayed, and their order, is configurable in each grid, from a set list. Of course, that's not going to happen for a bit but that's the general plan.Again, it's the sort of thing I can fully understand needing, and I have an idea how it could be done without too much fuss, but I'm thinking a general reporting facility would be more useful than trying to wedge that in, so to speak.

Right now, though, it's totally broken because I've removed the old install process and been converting it to Wedge's add-on format, which is no small job - in between writing the new installer ;)

There is a part of me that wants to go set up wedgedesk.com right now and start laying out all the plans I have for the future, but I'd rather wait until 1) WedgeDesk actually installs on Wedge cleanly (i.e. that Wedge can support it natively rather than how it's been done so far) and that 2) the permissions overhaul is complete so I have a single permissions area that everything's managed by.

Well, any place it's accessible from the script is a problem, of course, and making it directly more accessible from the page if it's compromised isn't particularly clever - but at the same time, it's really not an issue because any place that it's *currently* actually used, you can query for the session ID anyway.

All the objects that currently require a session ID are all fed it, they're passed an object going in, which is stored into the object itself - like when a new instance of weToggle is created, one of the parameters given to it is the session, but it's then stored in this.opt. So when you create a new instance of it, you can refer to that object's .opt and get the session, and since there's a weToggle that uses the session on every page for the header...

There isn't really a good method of avoiding it, unfortunately. Either we don't have it and open ourselves up to CSRF type deals, or we do and risk session stealing.