Jump to content


Dll

Member Since 01 Nov 2004
Offline Last Active Yesterday, 05:14 PM
***--

Topics I've Started

All IPB forums breaching EU law

Yesterday, 08:44 AM

Further to the thread in the customer lounge, it's seriously disappointing to see that IPB have backtracked on their published plans to comply with EU cookie legislation without any notice or announcement.

What this effectively means is that every single IPB site who have visitors from the EU are now in breach of the new cookie directive from tomorrow unless they take action to remedy it. Having been lead to believe upgrading to 3.3.2 would be all the action that was required, it's a serious problem.

When you look at what many of the major UK based websites have done, they're taking the new law seriously, and I'm shocked that IPB have decided neither to take any action or offer any guidance to their customers on what they need to do, particularly when taken in context with what Matt said in late April:

View PostMatt, on 19 April 2012 - 07:53 AM, said:

It technically doesn't matter where you are in the world. The EU would like for you to offer EU visitors the opt in/opt out/info regardless of where you are hosted.

I agree that it's all really dumb but as a software vendor we have a responsibly to ensure our software complies with these things.

I've done a lot of research into this and there are many exemptions where you don't have to ask for opt in permission and that's when the cookie is used in such a way that makes it vital to the application.

Really this is a browser level problem and it's utterly ridiculous to expect internet apps to 'fix' this but there you are. At some point browsers will have to include these rules and we can stop messing about with pointless javascript.

However, here's what I've done for IP.Board

Guests only get served a session cookie which is essential for the application and contains no identifiable information unless they decide to change themes or languages, etc. This means there isn't a need for pop-ups, overlays, banners, swooshing nag panels or any other of the head slappingly stupid suggestions the ICO offer.

When you log in, you make the user aware that doing so will set cookies and there is a link to the cookie policy. Same when registering.

At the bottom of the board there is a message "This site uses cookies: Cookie policy". Upon clicking this you're taken to a description of every cookie IP.Board will try and set along with a 'show contents' button if the cookie is set so you can review what is stored.

This barely scrapes in above the bare minimum needed to comply but lets be honest. The internet is a massive place and there are millions of websites. The EU law is almost impossible to police let alone effectively punish offenders. In addition, the ICO has said that it will not target sites that make an effort and have a clear cookie policy. Indeed, almost all the cookies IP.Board sets are exempt and contain zero tracking data and aren't shared with other sites so our software is very low risk.

My hope is that either the EU forces browsers to implement something or the whole thing is discarded as unworkable.

Profile photos - caching & CDN unfriendly

17 January 2012 - 04:39 AM

Profile photos are currently very difficult to cache or use on a cdn because they're over-writing newly uploaded photos with the same file name. If you set a long cache expiration then users don't see a newly updated photo unless they clear cache etc (or in the case of a site using a cdn, until the cdn is purged), you set a short cache and you end up making a lot of un-needed calls to the server for content which could be cached.

Ideally it would be good to see profile photos using a unique file name which would solve this problem. Any chance?

Blog 2.5 - What went wrong? Was it tested?

07 December 2011 - 09:31 AM

Sorry to be posting this really but I have to say that the 2.5 version of the blog is a bit of a mess, and seems to be that it couldn't have gone through any testing prior to release.

New features such as the blog post view count simply don't work - how can a brand new feature which counts views on entries make it to a final (apparently stable) release and not actually count views?

Creating blogs is broken if you don't allow linked blogs on your site as it removes the drop down menu in the create blog form and stops it submitting properly.

The tagging system doesn't work properly, and if you're using sphinx actually breaks the tag search system across the entire suite.

The dynamic header system was removed without a single mention about it in any release notes, and I could go on - the number of pretty major bugs in the tracker says it all.

So does anyone at Invision want to come clean? Was it released in error (that may explain why it didn't appear on the company forums for 2 weeks after release)? Was it tested at all? What went wrong?

I'd really like to know as there's something really not right about the release of a commercial product to paying customers in the state it's in right now..