Introducing evoSkins

b2evolution 0.8 will come with blog skins (evoSkins).

What are blog skins?

Well basically if you've used any skin-enabled software (like WinAMP) you probably have an idea. ;)

Bloggers using b2evo will be able to select a complete look & feel for their blog by just clicking on the "skin" they like the most.

b2evo will come with a few selected blog skins from cool people who already allowed their design to be included in the release package. B) Hopefully, new skins will be made available in the community so bloggers not knowing or willing to design their own will have a great choice available... :D

The other benefit of evoSkins is that your readers can also choose, from a selection of skins you provide, which one they like the most! :D

(Of course, this is optional... in case you don't like the idea! ;) )

What about my current blog template? :?:

If you already have a b2 blog template and just want to upgrade, you can just reuse it without worrying about skins.

Alternatively, you can turn your existing template into an evoSkin (instructions provided) and take full advantage of the evoSkins skinning system.

What's the difference between evoSkins and a CSS style switcher? :?:

Good question! Why do we need evoSkins when we already have CSS? :)

As a matter of fact, a blog skin can be as simple as a custom CSS design. But evoSkins can also provide more variations than what you can do with CSS. Here are a few examples:

  • Some evoSkins may have popups for comments while others display them inline
  • Some evoSkins may have a very light HTML footprint for use on Palm and mobile devices and others may have a full-featured output
  • Somes evoSkins may use plain standard HTML/XHTML, others XML, others WML, others cHTML, and others even FLASH! (=> BTW, if you are a Flash designer and want to work on accessibility compliant Flash Blogging, please contact me! :) )

I'll put up a demo as soon as I have a minute. I'm a little overloaded by the upcomming week-end right now... :roll:

Unsubscribring from spam *NOT*

Cédric [site gone] posted some interesting thoughts about whether or not to unsubscribe from spam.

Cédric advocates that unsubscribing has become less a trap than it used to be, basically because spammers are better off collecting new masses of addresses than preventing their mailers to automatically unsubsribe people who'll never buy from them anyway. And also, because there are legal risks in spamming twice someone who asked to be removed.

Cédric also says:

Another thing I can see coming in the near future is that these "do not spam" lists will one day be forced to be shared among spammers. In other words, any "do not spam" list you are a member of right now might end up in having your email address removed from others as well.

=> Well actually... this is precisely the point: some day spammers will have to share their "do not spam" lists...

Oh... actually they do it already! It's just that they do not share, they resell... and they donto not call them "do not spam" addresses, they call them "qualified" addresses!

The buyer can spam you without worrying too much... after all you haven't yet asked to be removed from this one!

The problem with spammers is that they are dumb and smart at the same time!

Who said we didn't need wireless? (Reloaded)

Who said we didn't need wireless? (Reloaded)

At first this looks plain stupid.

However, one would hope there was actually careful planing in building the new road AND in moving the pylons but that they were just not executed in the right order... and it was probably better for the road contractor de build the road anyways, letting the electric people deal with removing the pylon later and leaving only -- maybe -- a small pothole in the road... And fixing the "pothole" later is only a small job/problem compared to building the whole road later.

Trendspotting: mobile SPAM :(

It's already making me sick... and it's only the beginning :(

Mobile SPAM is coming in all flavours! First there is SMS spam. Your phone beeps in the middle of a meeting as if you just received an alert, you check what's going wrong... but no, it's just an ad from your carrier!

Then there is voicemail spam. This is even worse. You are driving and suddenly your phone beeps as if you just missed a call and got a message. You actually try and find a place to pull aside and listen to the message... but that was a worthless effort: you just got another f*ing ad from you carrier!

Right now, carriers can afford this because it's virtually free for them. But sooner or later, more companies will be willing to pay for that kind of mass messaging! And this is far worse than e-mail spam: it really interrupts you in whatever you are doing! (Something like instant messaging spam!)

I have called my carrier (Bouygues Telecom, France) numerous times demanding they stop it. Nah! Everytime, after a month or so, spam comes back! I am wondering what kind of bozo there just makes that stupid decision to reset the opt-out flags! So eventually I cancelled my contract! (With the added benefit of being able to get a new (smart)phone cheaper when I sign up for my new contract... but I would not have gone this way if those guys had been a "little" more customer respectful!)

Anyway, I guess we'll be able to install SMS/MMS spam filters on future "programmable" (smart)phones... but I wonder how we'll be able to handle the voicemail issue... :-/

PHP oddities :(

Actually I had not really looked into PHP since early version 3 betas... I knew it had gotten better, but sometimes I wonder if I didn't overestimate this... :-/

Looks like PHP 4.3 still requires that you name a collection of checkboxes or a select multiple with a name ending with "[]" such as <input type="checkbox" name="collect[]" value="3" />. That [] makes it impossible to DOM-handle the objects with javascript... but if you don't include the [], you just won't get all the checked values, neither as a table nor as a list... only the last one! :!:

What year is this? 1995? :'(

As far as I remember, ColdFusion and ASP have been handling this elegantly since version 1.0!