Wedge

It's nice to see loadLanguage using arrays :)Actually it could be better to use an array like that. The thing is, the sprintf does actually inject the value in, so even on _n cases you'd still have to always inject it, no?


Regarding 5.4's inclusion of array syntax... it's an interesting choice but one that I personally would have put into PHP sooner if given a choice, putting it at a .x release makes that quite hard for a language construct; things like namespaces in 5.3 is a feature not a language construct and it's not so hard to get your head around that as a requirement. But as a language construct, I think it should have been pushed into the next major release, not a minor one, personally.

Liking your own post, it's something the code never cares about, but since there's no configuration for it at present, that's the sort of thing that would typically be configurable ;)

You're right about session variables, and IIRC they expire after 20 minutes in SMF/Wedge by default. Though I should note I have made distinct noises about removing sessions for guests across the board (because I don't think you really need much in the way of sessions for guests for the most part, and the rest is just for snapshots of analytical information, rather than meaningful information, IMHO)

I'd rather avoid cookies for that sort of thing, laws aside, just because they have a habit of living longer than expected, and carry an overhead per request.

That's mostly a UI matter rather than code, since the code level can pretty much already handle that.

I guess you don't go around WordPress blogs much?

OK, so let's back up a minute.

The PHPSESSID cookie, left alone and untouched by logins, will be removed properly. When logging in, though, SMF and Wedge both make that a persistent cookie. There's no argument on that score: it's a persistent cookie that is not being handled nicely and certainly flies in the face of any argument we can make that PHPSESSID is a valid session cookie when it stops being one.

@nend, why should you bother? That's a good question, and for now I don't think you have to be too concerned if you're based entirely outside the EU. That assumes the US do not introduce any forms of sanction, and I wouldn't put it past them, because then a user in the EU could complain to their national body and they can take it forward on that user's behalf. So in that respect, you don't have to be too bothered - for now.


Assuming the ECL cookie is set, there is nothing in the guidance about it being a session cookie from what I remember, and it does seem overly onerous to make it such, particularly if there is a persistent cookie of any form present.

My take on it is that if cookies are provided that the site is expecting (e.g. the member cookie or PHPSESSID), we can assume that consent must have been provided in the past and not require that extra cookie.

I just figured that Gravatar was one of those things that isn't a lot of effort to support, and does allow for avatars that are uniquely tied to an account - so there's an element of consistency everywhere, especially for blog type support.

That unease is common to both myself and Nao, as it happens, I'm wary of poking at Aeva code for that reason.

I had a feeling it was broken for a while (because WedgeDesk uses/used it and it didn't work) but I never got round to digging into why.

Good to know it's fixed though.

First up, search engines often send multiple separate bots to visit the pages at once. Then you have Google Preview which will view pages without the user going there (which is also logged)

Also note that you can't really use IP address to identify users that are using (non-Wifi) mobiles because they're pushed behind proxies at the ISP level in the cell towers, meaning that you're only tracking a more limited number of users at the ISP level, not the user level.The only reason I'm so pissed off with you is because I'm that fed up of having to wade through your posts where you provide your opinions that I demonstrate are wrong, and you keep dredging up the same misinformation, and you keep disrespecting me by not reading what I've written over and over and over.

Take the discussion over the Cookie Law, most of the points you raised (repeatedly) I'd already raised for discussion with the ICO, as I pointed out to you many times and you still kept trying to make your point. I heard you the first time, I told you why I disagreed with your view and said I'd referred it to the ICO for discussion, yet you kept rambling on.

I have no constructive issues with people that are constructive in themselves, which you are not at this time. Do you see me railing at Nao? Or at live? Or at anyone else who can actually read what's been said and not keep dredging up the same things over and over?No, I can handle a debate just fine. What I can't handle is people who think they know what they're talking about, who don't understand the question being asked, as evidenced by their post that is misleading and confusing, and for them to keep going over and over and over the same points without actually understanding what's been said to them. In other words, it's not the debate I can't handle, it's basically your attitude.I don't appreciate you posting the same misinformed diatribes, nor do I appreciate you replying to what you think I've said rather than what I've actually said, nor do I appreciate you trying to tell me how to do my job. If you want to prove me wrong, prove me wrong with evidence.I go around taking the view that people are muppets and then I get to be pleasantly surprised when they're not, as opposed to thinking the best of people and being proven wrong. I had years of thinking the best in people and years of continual let-downs. These days I don't have continual let-downs, I have the occasional flash of being pleasantly surprised. Not a surprise here though.I'd love to see where that's true.If you noticed, I actually acknowledged that fact. But the resources used in processing the log are still fewer than the resources that will be used in handling the guest log in Wedge.

It also depends on your definition of resources. In the case of awstats, it consumes space on the host that does not come out of your allocation if you're on a shared host, and its processing is not counted towards your use of the server, so on shared hosts it consumes no resources that you have to account for. Of course on a VPS or better it will make a difference but then, it's up to you if you install it and if you don't (like I don't) it's not consuming any resources.

Also note that disabling logging of CSS or JS files actually improves the ability to identify users in the action log, not decreases it, but thanks for pointing out something that for the sake of this argument is irrelevant.Except that it wasn't. I'm fed up of wading through your points trying to find the parts where you're actually correct, because for the most part you're at best half correct.You're right, I don't know you. Odds are I'd probably think slightly better of you if I did. But since I don't know you, I can only rely on the things you post. And given that pretty much every post of the last day or so has been regurgitating what people have said and adding your own misinformed view onto it, without considering what's been said, I can only conclude that you shouldn't really be operating a website and certainly not a discussion forum, because you show me more disrespect than you claim to have gotten back from me.

But on the other hand, you don't even know me. You are also pretty fast on the trigger of calling me out, but consistently you do so without anything correct to back it up. What I do will, and has, come back to me in the past. That's something I'm more than prepared to deal with. I doubt you can say the same.I allowed you to keep posting, which is showing you more respect than I think you deserve. When you start showing me respect, I'll start showing you some.


But maybe you are right, that I have some constructive issues. Maybe I'm projecting my faults onto you (doubtful, but it is possible), and for the second time in the last 18 months, I've considered resigning from my position here at Wedge. I've had to give up a considerable amount of things in that 18 months in order to work on Wedge, and in that 18 months I never regretted it, not for one moment, because I believed in what I was doing, but last year I considered resigning because I had enough stuff going on in real life that I couldn't give Wedge what it deserved.

Now, I'm in a similar boat, that I don't feel I can give it what it deserves, but at the same time I'm also for the first time in 18 months regretting every working on Wedge. I've met some awesome and fantastic people, and I'm proud of what has thus far been produced, and what has been achieved, but at the same time if the price I have to pay is dealing with disrespectful, misinformed people (who, frankly, have done nothing to vindicate themselves of the designation of idiot), that's perhaps a price too high for me to pay.

I had hoped that after I had a drink and a sleep that I might feel better about things, but whatever motivation I had is fast disappearing, and I can very quickly and readily go elsewhere and do what I do, for money and in all likelihood almost as much satisfaction - and none of the crap to put up with.