Wedge

What, the day after Windows 8 is scheduled?

(Yes, that's right, Windows 8's scheduled ship date is the day 'before the Apocalypse'. Now you know what causes it.)

LSBs are kind of voodoo, it doesn't surprise me that Zend would be the only one to support it.

I have no doubt he would, but I get the impression that no-one asked him.More expenses: fair enough, though at the end of the day as far as the form is concerned it should be a total at the bottom of the balance sheet, as it would be for other companies.

More domain names: should be irrelevant. As far as I know, only two domains are held by SM NPO, but that's ultimately a justified organisational expense, and so goes into the above as another line on the balance sheet.

More stuff: certainly. The problem I'm having is that the more I look at it, the more I'm thinking 'more stuff to find excuses for'. This is the part that's an issue: for an organisation that swore it would have more transparency, it isn't doing a good job of this.

More moving parts: wouldn't have thought it would have made that much difference. At the end of the day, if there is a problem with filing the document, either it should be handed over to a suitably qualified accountant to arrange, or someone should be contacting the IRS for advice. Right now I get the impression, however accurately or not, that it's being sat on because it's 'too hard'.

OK, just as a heads-up, I've rewritten it as a plugin to use 2/3 queries (there's one query to get message ids in recent posts, one to get message ids in recent topics, and one to get the actual data, and it seems to be faster now, too) so I've also committed the removal of the rest of it and will drop the plugin into the repo shortly.

Not sure exactly what I want to do with it just yet but the fact it's a plugin makes it much easier to do magicalness with.

OK, so I've pulled out the recent posts into its own little plugin and given it, sort of, the ability to order by topic except it's currently doing it wrong, gah.

It's not just as simple as shoving a group-by in there :(

It means that they won't be paying taxes on the income generated from Charter memberships and advertising. It was at least enough to cover the hosting costs (which, remember, is on a collection of servers that they own and that reside in a datacenter, which means it ain't cheap)

You said that if it were tied to posts, users wouldn't be able to repost it... whereas specifically I'm saying they should be able to do so. They just don't need to worry about the other details.OK, here's the problem.

There's the Content-Disposition header, which is supposed to indicate what the browser is supposed to do with the content that follows, except the specification pretty much states it should be ASCII characters only. Which is fine, right up until you have high bit characters in the name, which in non English forums is more common than you'd think. So there is a quasi-extension that's now pretty much standardised which allows a content provider to state that the data is really UTF-8, except browser support is quirky for it.

The original code in SMF issues separate different headers for IE, Firefox and Opera, I changed that a year ago to IE and everyone else.

Now, the problem is that IE9 got its act together and doesn't like the header being used for IE because it's special, ugly and it wants to conform with the in-crowd. Trouble is, Wedge recognises IE9 as IE (and SMF does not), so it was given the IE specific codepath which spits out the wrong filename on IE9. So the first change was to make the IE-only code path into IE8 and down.

The second change is that FF8 stopped accepting the otherwise-standard header, it would ignore the filename entirely because it didn't like the quote in the name. So the quote has to be changed for another delimiter, which caused it to start choking on spaces and other things, so the entire thing has to be urlencoded and it must also include spaces in that to be %20, rather than +, hence the rawurlencode call.

As far as I can tell, this works properly on all the big browsers. I'm not so sure it would work so well for SMF even though I gave the few lines in question to be reposted; there was a rather curt "this is the same fix I posted" note, except that it isn't, for several reasons (my fix doesn't bother to differentiate ISO and UTF-8, and I don't have a special case for FF, merely IE8 and down - when they get round to listing IE9, they'll have to fix it again, but hey, what do I know?)