From Slashdot: “Pidgin Controversy Triggers Fork“:
Pidgin, the premier multi-protocol instant messaging client, has been forked.
And this is not the first controversy either – the other one I remember was with protocol icons. Did not end up like that, patch was accepted as an option. This time – no such luck.
I’ve blogged 3 days ago about WordPress.com blog being hacked and rogue post appearing in the feed.
The post contained screenshot from my Google Reader page showing that rogue post.
Today I find this screenshot missing on my blog:
I do have a backup of the original screenshot, of course. But the the question is why it is missing?
Did WordPress delete it? Do not know, I’ve sent email to support and will post if I receive reply!
Spent time today trying to cleanup this blog a bit.
I love wordpress, but there are some usability issues. handling templates is one of them. No preview available. No conformation when selecting new template.
As a result – screwed blog by accident. Of course did not have any notes on how it was formatted – had to reinvent the wheel.
Would be nice to be able to define couple customized layouts – one default for example, and test one – to try different templates, colors and widgets. Oh, well.
So much for tags – love that idea, but it does not translate to Categories logically all the time. Example – I had “Computers and Internet” category. All good, but this name is too long for a tag, which should be simple one-work label. Converted to just “computers”.
Another issue is a layout. That’s more my personal quest for the best. I’d like to use full width of the screen – to be able to post wider items. On another hand – wide text is hard to read, better to limit the width. But with 3-column design, middle column isn’t too wide. On the other hand – 3-column layout may look too cluttered (and it probably does!).
Decided to keep current layout anyway…
You would think that Open Source projects would excel in several areas, including listening to user’s feedback…
Not really true overall, but big projects with large customers base usually good in implementing feature requests.
Unfortunately, there is one exception from this rule – Pidgin Purple (formerly GAIM).
I’m still on last beta version of GAIM and was looking into upgrading to the most recent version of Pidgin, hoping it will bring enhanced stability and new features. Since I usually use applications in their portable incarnations (from PortableApps for example), I couldn’t test Pidgin before – there was no portable package for it and I did not have time to make one myself.
Just today I found some unofficial packages on PortableApps forum and decided to give Pidgin a try.
To my biggest surprise, I found one missing feature – there are no protocol-specific icons in the buddy list anymore…
You can see what protocol contact is by holding mouse over it – tool tip will have protocol icon, but you are out of lack if you just glance over contact list…
Hoping that I’m missing something, I checked all possible options – nothing. Finally, when to their bug tracker to find some interesting and worrisome discussions..
Judge for yourself. There is a very long discussion in ticket 414. Ticket itself is closed with status “wontfix”.
And the most interesting is this paragraph (left by user “elb”, someone from Pidgin team, I presume):
Adding a “me too” to this ticket is NOT USEFUL. If you do not have a solid use case that is NOT discussed above or on the thread on this topic on email@example.com, save your time and ours by not replying. If you DO have new information, please send it to firstname.lastname@example.org, do not comment on this bug.
Ok, you do not want me to even vote on this feature? You are not allowing me to even comment about it on your public site?
Why then, in another (although, duplicate) ticket 1863, the same user comments this:
There is no indication that there are “thousands upon thousands” of users “just like you”; there have been a dozen or so users requesting protocol icons in the buddy list, compared to the *millions* of Pidgin users out there.
Well, I find this quite arrogant. And this is really disturbing to hear such things from advanced, long standing Open Source project…
I will probably pass on migrating to Pidgin this time. Wonder how many others will do the same. Oh, sure, I understand that it is possible to create plug-in to make protocol-specific icons come back, but WHY? Why would this standard feature in current GAIM or any other multi-protocol client should magically disappear from project?
There is an explanation on why this step was taken in Pidgin Design Guidelines. But I don’t buy it – that “uniformity” is good in theory (or can simplify life of the developer), but in practice… In practice you should care of your customer base need or want, and let them raise their voice, and listen to it!
Technorati tags: computers
Technorati tags: computers
After upgrading ISA server to 2006 version, I was surprised to find that my FTP behind it stopped working in passive mode. Having quite smart FTP server installed I blamed MS ISA for this and did not have time to look at this deeper… until I found a need for this – had to move my Blogger blog from 1and1 hosting (expired free one) to my own server. And Blogger refused to publish the blog unless I have passive FTP working.
FTP client was getting 500 response – that FTP server sent bad response. Quick capture on ISA server showed that my FTP server was too smart – it actually was configured to return correct IP address in PORT command (the external IP, not default internal one). This, turns out, is “bad” thing from ISA server FTP filter prospective. Turning advanced NAT support on FTP server, making him return internal IP, fixed this – now ISA server could replace that IP with the external one it knows about.
But that got me thinking – software gets smarter, you try make it better and as end result – there is some stupid “simplification” (or “assumption”) made by other developer broke functionality.
Granted, if I’d read the docs for ISA server, I might have caught this, but sorry, RTFM is the last thing I’d do.