Re: Proposal to Use LucidChart

[Robert Vehse]

I find it hard to tell how useful the software can be for us.

We could ask them whether they would consider a free option for open source 
projects.

Robbie

Re: Adium needs your help

[Robert Vehse]

Hi,

> […] Asher is in the process of writing up issues which apply to 1.6 and a 
> subsequent 1.7 release. 

Adium Trac’s list of tickets scheduled for the 1.6 milestone covered pretty 
much all known issues. Do we have a Trac backup we could look at? Jordan?

Cheers,
Robbie

Re: NetworkRedux hosting going away

[Robert Vehse]

Hi folks,

I just remembered that we are not the only ones using Cocoaforge. There is also 
a decent amount of activity in the subforum for the Vienna RSS reader. The 
Prowl subforum is also active but has not seen any posts for a while.

Robbie

Re: rackspace and sourceforge

[Robert Vehse]

> Am 05.12.2020 um 16:02 schrieb Jordan :
> 
> Probably a good idea to be rid of the sourceforge page as it appears to have 
> an outdated version hosted anyway.
> 
> Can/should we get the dmg for 1.5.10.4 added as a release on GitHub and use 
> that to host future releases (should they come to fruition)?

Sounds good to me!

Re: rackspace and sourceforge

[Robert Vehse]

Hi Matthew,

Thanks for looking into this.

> I think nightlies.adium.im used to serve files hosted on Rackspace. Nightlies 
> is gone, but is rackspace still serving files somewhere?

I don’t know.

> Also, https://sourceforge.net/projects/adium/ is still going, and reports 39 
> downloads this week! Can we kill that?

Didn’t we use SourceForge to lessen the burden on Cachefly? In Adium’s current 
situation I can’t imagine there are enough downloads for this to be an issue…

Kind regards,
Robbie

NetworkRedux hosting going away

[Robert Vehse]

Hi folks,

NetworkRedux is retiring from the hosting business on
1 December 2020. This means we will need to migrate our entire infrastructure.

Matthew said he wouldn't be able to help with that before November, if at all.

Kind regards,
Robbie

Re: Leadership, an apology, and important questions

[Robert Vehse]

Thanks for this, Evan. 

> This is, of course, separate and distinct from documentation, AdiumXtras, 
> user support, and website infrastructure, the status of which I did not 
> assess in detail (but recall that the last message about it that I was privy 
> to was on 4/13/19, when Colin wrote that:
> 
>> A few of us are working to get the behind-the-scenes infrastructure repaired 
>> and restored so we can proceed with development and releases

I'd like to take this opportunity to (belatedly) acknowledge that in recent 
months Gary has been putting a huge amount of work into restoring and improving 
Adium's broken infrastructure. The items listed at 
https://trello.com/b/nhz2JwDw/adium only show some of the work done but not all 
of it.

> I stepped up to try to resume a leadership role to bring this back to a level 
> that someone without nearly 20 years of experience in the Adium codebase 
> could work on it.

Thank you! :-)

> With extremely limited time resources, I felt the best move for Adium was to 
> provide Asher, who offered to help and who I trust as much as I trust myself, 
> with commit access to help directly after he offered to do so.I felt that 
> “unilateral decisions” were the only decisions likely to move forward in a 
> timely fashion given the apparent radio silence.  We’re all the heroes of our 
> own stories, right?
> 
> It is clear that regardless of the radio silence at the code level, Robbie 
> and Mathew should have been involved in this discussion.  That was an error, 
> and it was my error.  Gentlemen, please accept my apologies.  The most I can 
> protest is that I haven’t done this in a long time. Small excuse.

Apology accepted. I know you meant well, Evan.

Asher's "i just moved adium off hg" on IRC sounded very definitive and I can 
understand how that would have irked Gary, who, as part of his work on our 
infrastructure, has been busy researching Mercurial alternatives to Bitbucket.

I regret not having informed the community on the mailing list of the work Gary 
has been doing and in this sense I feel partly responsible for the conflict 
that occurred between Asher and Gary. If Evan and Asher had known that there 
was work going on, they might have felt more confident about getting a response 
on the mailing list.

I am fine with the move to Github as long as we make sure the migration works 
well and we don't lose any important information in the process. Asher and I 
have been working on that. I think there are a lot of benefits to Github 
compared to what we have.

Asher has already done a lot of work towards bringing "Adium's code into 2019" 
and that's great. I'm glad to contribute my help and enthusiasm. :-)

-Robbie

Re: Introduction: Asher Haig (Asher-)

[Robert Vehse]

Hi folks, and welcome, Asher. :-)

I'm excited to see someone willing to work on Adium!

I'd very much like to participate. Even in recent years with little to zero 
development activity, I've thought about Adium a lot and I've been working on a 
proposal on how to move forward once we have a release out with the Catalina 
auto-scrolling fix. I'd be happy to talk about it here soon.

I'd also like to offer guidance to Asher (or any other new contributor). Even 
though I cannot read or write code, I think I am quite familiar with many, many 
things relating to the Adium Project that are important to know, for example 
what the different development branches contain and what state they are in.

Speaking of branches: Asher started development on Adium's Github account. 
While it's great to see him being eager to get to work, I too think it would 
have been good to get feedback for a move to Github here – even with the lack 
of activity on this very list. It's just quite a fundamental change. With its 
popularity Github lowers the barrier not just for Asher but also other 
potential contributors which is obviously a good thing. But I wonder whether 
are other questions to consider: Will it make updating libpurple harder? What 
happens to commit history?

Onwards and upwards!

Kind regards,
Robbie

Re: Releasing 1.5.10.5 to fix Catalina auto-scrolling

[Robert Vehse]

Hey Evan,

Any progress? I recently exchanged emails with Asher Haig and he said he was 
able to get Adium building on recent Xcode.

Kind regards,
Robbie

Releasing 1.5.10.5 to fix Catalina auto-scrolling

[Robert Vehse]

Hi everyone,

I've merged https://bitbucket.org/adium/adium/pull-requests/11 and 
https://bitbucket.org/adium/adium/pull-requests/12. The former fixes a build 
issue and the latter fixes auto-scrolling on Catalina.

Could someone please help with cutting a release? It would great to keep Adium 
usable for folks who have updated to Catalina.

Also, for a few weeks now, I've been preparing a call for developers to get 
Adium development up and running again. If someone would like to help with 
that, please contact me. I will send out an email with details in the coming 
weeks.

Kind regards,
Robbie

Re: Auto-scrolling fix for Catalina - pull request review

[Robert Vehse]

Hello,

I merged PR 11

 I've been testing PR 12 and it works well. I'll merge it today if nobody 
objects.

Cheers,
Robbie


> Am 20.10.2019 um 02:11 schrieb Robert Vehse :
> 
> Hi everyone,
> 
> In my email regarding codesigning from two days ago I mentioned work being 
> done to fix an issue with auto-scrolling on Catalina.
> 
> Pull requests have now been created:
> - https://bitbucket.org/adium/adium/pull-requests/11 "Update JVMarkedScroller 
> to use public APIs to determine scroller direction"
> - https://bitbucket.org/adium/adium/pull-requests/12 "Adjust auto-scroll code 
> to use more compatible APIs, adding support for macOS Catalina"
> 
> It would be great if someone could review the changes.
> 
> Cheers,
> Robbie

Auto-scrolling fix for Catalina - pull request review

[Robert Vehse]

Hi everyone,

In my email regarding codesigning from two days ago I mentioned work being done 
to fix an issue with auto-scrolling on Catalina.

Pull requests have now been created:
- https://bitbucket.org/adium/adium/pull-requests/11 "Update JVMarkedScroller 
to use public APIs to determine scroller direction"
- https://bitbucket.org/adium/adium/pull-requests/12 "Adjust auto-scroll code 
to use more compatible APIs, adding support for macOS Catalina"

It would be great if someone could review the changes.

Cheers,
Robbie

Codesigning

[Robert Vehse]

Hi everyone,

People who have updated to macOS Catalina have found that auto-scrolling no 
longer works there: https://trac.adium.im/ticket/16744

Some users on Cocoaforge have managed to get Adium to build on Catalina and 
found a fix for the issue.

So with that sorted we'd need code signing for a release. Has anyone got a 
suggestion how to go about that?

Cheers,
Robbie

Re: Build is working on Muscovy with modern codesigning

[Robert Vehse]

Hi,

https://trac.adium.im/ticket/17097#comment:8 reports AIM as broken with 
1.5.10.2.

How do we proceed?

Cheers,
Robbie

Re: Build is working on Muscovy with modern codesigning

[Robert Vehse]

Hi,

Quick update. These two regressions were reported today
- https://trac.adium.im/ticket/17104, "crash on libpurple or resolver memory 
error": I have seen similar crashes with 1.5.10.3b1. But I think there have 
also been some with previous versions so probably not strictly a regression…
- https://trac.adium.im/ticket/17105, "text jammed together in windows too 
narrow": That's an odd one. I cannot think of any changes in 1.5.10.3b1 that 
could account for that regression.

Ideas?

Cheers,
Robbie


> Am 31.03.2017 um 01:10 schrieb Robert Vehse :
> 
> Hi,
> 
> Feedback on Cocoaforge and Twitter suggests people seem to be happy about 
> seeing a new Adium version. :-)
> 
> As far as I can tell there haven't been any reports of regressions for 
> 1.5.10.3b1 whatsoever so I suppose we can consider releasing 1.5.10.3 
> tomorrow, one week after the beta.
> 
> Regards,
> Robbie

Re: Build is working on Muscovy with modern codesigning

[Robert Vehse]

Hi,

Feedback on Cocoaforge and Twitter suggests people seem to be happy about 
seeing a new Adium version. :-)

As far as I can tell there haven't been any reports of regressions for 
1.5.10.3b1 whatsoever so I suppose we can consider releasing 1.5.10.3 tomorrow, 
one week after the beta.

Regards,
Robbie

Re: Unique users over time

[Robert Vehse]

Hi Evan,

2% of the user base Adium once had?

-Robbie

Re: Build is working on Muscovy with modern codesigning

[Robert Vehse]

Fantastic! :-)

Thanks,
Robbie

Re: New Adium release for continued AIM support – updated certificate needed

[Robert Vehse]

JSONKit's back in.

-Robbie

Re: New Adium release for continued AIM support – updated certificate needed

[Robert Vehse]

> By the way, has anyone tried to build tip? I'm having trouble figuring out 
> how to build Adium as a whole and not just frameworks, heh. :-D

I went ahead and ran "make latest" from Terminal. The build failed due to 
Twitter missing JSONKit which I removed earlier with the Facebook Chat code.

Should we re-add JSONKit? Reports on Trac suggest Twitter no longer works in 
Adium so maybe we should disable Twitter or even scrap it altogether?

-Robbie

Re: New Adium release for continued AIM support – updated certificate needed

[Robert Vehse]

Hi everyone,

Here's a tentative changelog for 1.5.10.3: 
https://hg.adium.im/adium/file/a80d051c4014/ChangeLogs/Changes.txt

We have removed Facebook Chat, MSN; Yahoo!, and MySpaceIM which means they show 
up nowhere in the UI. However, associated data such as passwords in the OS X 
Keychain, contact list, transcripts and the like remain if I'm not mistaken. I 
intend to explain this in a blog post. Do you think that would suffice?

By the way, has anyone tried to build tip? I'm having trouble figuring out how 
to build Adium as a whole and not just frameworks, heh. :-D

-Robbie

Re: New Adium release for continued AIM support – updated certificate needed

[Robert Vehse]

Hi folks,

A quick update: Thijs put in a shift earlier and we're almost there: 
https://hg.adium.im/adium/

Next, we need the certificate. Evan? :-)

Cheers,
Robbie

Re: New Adium release for continued AIM support – updated certificate needed

[Robert Vehse]

> I can try to help.  

Thanks. :-)

> It looks like next release should be 1.5.11.  Is 
> https://hg.adium.im/adium/rev/307f53385811 the tip of that?  

The branch 1.5.11 has unfixed issues, I believe. Thijs confirmed to me that we 
should branch off 1.5.10.2 (https://hg.adium.im/adium/rev/a23057ce854d, I 
think).

> I don’t see a libpurple commit yet. Is that still pending?

Yep.

Regards,
Robbie

New Adium release for continued AIM support – updated certificate needed

[Robert Vehse]

Hi everyone,

Eric managed so get updated IDs from an AOL representative for continued AIM 
support. For anyone who's missed this episode, here's some context: 
https://arstechnica.com/business/2017/02/aol-will-cut-off-third-party-app-access-to-aim/
 (Yes, the Ars Technica title is misleading.)

So now we're looking to get a new Adium release out with the updated IDs. This 
release should also address a recent security issue 
(https://pidgin.im/news/security/?id=109) which was mentioned a few days ago in 
an email to this list.

On top of that of that, we'd like to update Adium's codesigning signature to a 
version trusted by Gatekeeper on 10.9.5+ (https://trac.adium.im/ticket/16983). 
In September, Evan updated the "Muscovy" build machine to OS X 10.11. Provided 
Xcode has also been updated on Muscovy, the only thing we are missing now is an 
updated certificate. Would someone be able to obtain it?

Regards,
Robbie

Re: Xtras

[Robert Vehse]

Hi,

Xtras downloads should be back now.

Regards,
Robbie

Re: Adium has a v1 code signing signature

[Robert Vehse]

So how can move on from here?

Cheers,
Robbie

Re: Cloning the Adium repo

[Robert Vehse]

I reckon your bandwidth is a lot higher than mine? I'd been downloading for 20 
to 30 minutes when it failed.

Cloning the Adium repo

[Robert Vehse]

Hi everyone,

Recently, I twice tried to download Adium source from our repo and each time 
the download timed out. Yesterday, a user reported cloning didn’t work for them 
either 
(https://www.facebook.com/permalink.php?story_fbid=10153957981491819&id=6521951818&comment_id=10153987753641819&reply_comment_id=10153987939626819&comment_tracking=%7B%22tn%22%3A%22R5%22%7D).

For now, should we perhaps only point to Bitbucket at 
https://trac.adium.im/wiki/GettingNewestAdiumSource (and possibly other places)?

Regards,
Robbie

Re: Adium has a v1 code signing signature

[Robert Vehse]

Hi Adrian, you perhaps?


> Am 07.09.2016 um 04:31 schrieb Evan Schoenberg :
> 
> Muscovy has now been updated to OS X 10.11.
> 
> Who controls the email address ‘ad...@imfreemdom.org 
> <mailto:ad...@imfreemdom.org>’?  That’s the Apple ID in use there, and the 
> password is needed to run the App Store updates including updating Xcode.
> 
> I’m not familiar with the automatic build system — I’ve done the part I can 
> help with.  Xcode definitely needs to be updated first, though/
> 
> -Evan
> 
>> On Sep 6, 2016, at 10:46 AM, Chris Forsythe > <mailto:ch...@growl.info>> wrote:
>> 
>> Or ship an installer up and ask them to perform the necessary clicks?
>> 
>> Or ship a new build box up if there is enough in the coffers? Have devs sign 
>> the old one and auction it for charity?
>> 
>> On Sep 6, 2016, at 5:03 AM, Robert Vehse > <mailto:robertve...@fastmail.fm>> wrote:
>> 
>>> 
>>>> Muscovy is a late 2009 Mac Mini Core 2 Duo which supports 10.11.
>>> 
>>> That’s good news. :-)
>>> 
>>>> https://github.com/munki/createOSXinstallPkg 
>>>> <https://github.com/munki/createOSXinstallPkg> appears to allow setting up 
>>>> a no-intervention upgrade installation.  I don’t have experience with it — 
>>>> does anyone on the list, with this or any other approach for upgrading OS 
>>>> X on a remote headless machine?
>>> 
>>> Not me, I’m afraid.
>>> 
>>> Thanks,
>>> Robbie
> 

Re: Adium has a v1 code signing signature

[Robert Vehse]

> Muscovy is a late 2009 Mac Mini Core 2 Duo which supports 10.11.

That’s good news. :-)

> https://github.com/munki/createOSXinstallPkg 
>  appears to allow setting up a 
> no-intervention upgrade installation.  I don’t have experience with it — does 
> anyone on the list, with this or any other approach for upgrading OS X on a 
> remote headless machine?

Not me, I’m afraid.

Thanks,
Robbie

Adium has a v1 code signing signature

[Robert Vehse]

Hi folks,

It has been reported (https://trac.adium.im/ticket/16983 
) that Adium currently  has version 1 
signature which is not trusted by Gatekeeper on 10.9.5+. To be able to sign 
Adium properly, we’d need a build machine running OS X 10.9, however, our build 
machine runs on 10.7.

Who has access to the build machine? Would we need a newer machine to update to 
10.9 or could the current one be updated? If so, how much effort would it 
require to update to 10.9?

Regards,
Robbie

Re: Certificate expired

[Robert Vehse]

Hi Evan,

any idea when the fix may land? The issue was brought up again today: 
https://trac.adium.im/ticket/17071#comment:6 


Regards,
Robbie

Re: New Developer Alert for Adium

[Robert Vehse]

Am 16.04.2015 um 19:43 schrieb Christopher Forsythe :

> The problem is that there are things to do:
> 
> 1) Provide notice to existing users. - Blog post/twitter?

I can do that.

> […] At the end of the month they turn this off, then the 2500-3000 people 
> actively using it per sparkle are going to start filing tickets and hitting 
> up the support channels, things like that. It'd be nice to get ahead of that 
> is all.

Right.

> Does this sound reasonable or am I out on a limb here?

Nah, sounds fine.

Re: Fix for #16038 / Pull request

[Robert Vehse]

Hi Quentin,

Thanks for the patch. Frank ("wixardy") had a quick look so I’ve committed it. 
I took the liberty of modifying the commit message slightly to mark 
https://trac.adium.im/ticket/16038 as fixed and to reference 
https://trac.adium.im/ticket/16038, I hope that’s okay.

Sorry it took us so long.

Regards,
Robbie

Adium repository mirror on Bitbucket

[Robert Vehse]

Hi folks,

Some time ago Jesper Noehr kindly set up a mirror of the Adium repository on 
Bitbucket: https://bitbucket.org/adium/adium Unfortunately, it went out of sync 
in February. Would you be able to look into the issue?

Regards,
Robbie

Fwd: Programming XTras

[Robert Vehse]

Sorry, for the late response, Doug. I'm forwarding your email to the developers 
list.

-Robbie


Anfang der weitergeleiteten Nachricht:

> Von: Doug Young 
> Betreff: Programming XTras
> Datum: 27. August 2013 22:11:25 MESZ
> An: feedb...@adium.im
> 
> Greetings,
> 
> I've always wanted to look into programming, but never had a good project to 
> tackle. I constantly use Adium and wish there was a way to flip the message 
> box to have the input field at the top, and have new messages go from top to 
> bottom. This way I can place the Message Window at the bottom of my screen, 
> Always on Top of all windows, and have conversations flow off the bottom of 
> the screen.
> 
> It's a tall order, and I figure I'm probably the only one who wants this (as 
> searching your site doesn't show anyone else who's tackled anything similar), 
> so I thought I might try and program it myself. My question is: is this 
> possible? Does Adium allow this much modification of its appearance, or are 
> those controls locked off from Xtras modifying them? I thought it'd be better 
> to know now than go far into learning programming, only to discover what I 
> wanted to do wasn't possible in the first place.
> 
> Thanks!
> Doug Young
> 971.506.2470

Re: Adium defaults

[Robert Vehse]

Am 11.07.2013 um 16:14 schrieb Evan Schoenberg :

> I think the idea behind the new defaults and having Setup Wizard choices are 
> good, though on reflection I find it confusing that 'Visual Notifications' is 
> really 'Default Notifications' plus contact signed on/off notifications, 
> which are usually just noise for most users I think.  Also, since the user 
> will see 'Default' without knowing what it means and also see 'Visual' in the 
> same way, I think some will pick Visual having really *wanted* Default.
>  
> I suggest not calling anything 'Default'.  Instead, name each set, and pick 
> one set as the default.

Thanks!

Yes, that makes sense. It's not very smart to have two sets that hardly differ 
and I also agree on signed on/off notifications being noisy. Thanks for 
bringing this up.

> How about:
> Visual (renaming what is currently called Default)
> Audio
> Audio + Visual (merging the currently-Default and Audio sets)
> None

I think I'd scrap the "Audio + Visual" set. If we merge the two we again get a 
very noisy set. I think we're good with "Visual", "Audio" and "None".

I've updated the proposed defaults per your suggestions above: 
https://trac.adium.im/wiki/DefaultsReview2013/DefaultNotifications#Proposedfuturedefaultnotificationsets.

> Users can add the signed on/off notifications on a global or per-group or 
> per-user basis if desired.

Yep

Cheers,
Robbie

Re: Adium defaults

[Robert Vehse]

Hey everyone,

Here's an update:


> Default notifications

I've set up a table containing proposed updated notification presets 
("Default", "Audio", Visual", 
https://trac.adium.im/wiki/DefaultsReview2013/DefaultNotifications#ProposedfuturedefaultnotificationsetsJuly7th2013).
 You will notice the default preset is stripped of all sound notifications. You 
can find my reasoning in the "Discussion" section 
(https://trac.adium.im/wiki/DefaultsReview2013/DefaultNotifications#Proposalsforremovaldiscussion).

In an email reply to the email from Rick Fillion forwarded by Peter [1] , Colin 
pointed out the issue of discoverability when removing all sound notifications 
from the default set. I think we can solve it by having users select a preset 
(options: "Default", "Audio", "Visual" plus "Custom" – no notifications, set 
them up from scratch) in the Setup Wizard. Obviously, there's a always the 
danger of having too much stuff in a setup wizard but ours currently only has 
account setup in it so I don't think we have a problem here.


> Toolbar items

I've added a screenshot with a proposed updated default toolbar 
(https://trac.adium.im/wiki/DefaultsReview2013/DefaultToolbarItems#Proposeddefaulttoolbaritems).
 Again, you can find explanations in the "Discussion" section 
(https://trac.adium.im/wiki/DefaultsReview2013/DefaultToolbarItems#Proposalsforremovaldiscussion).


So, everyone interested in this please tell whether you can agree with what is 
being proposed and if you disagree with something, please say why. :-)


Regards,
Robbie

[1] http://markmail.org/message/pw4bkgejpa5j2tqu?q=default+list:im.adium.devel

Re: Adium defaults

[Robert Vehse]

Am 08.05.2013 um 18:39 schrieb Christopher Forsythe :

> My general recommendation with Growl is to only show notifications that are 
> actionable. The user sees it and then can do something with that information 
> is ideal. Personally when I use Adium, it's a very tuned down subset of 
> whatever the default is (I don't even know what it is), so I'd agree with 
> tuning it to be more friendly.
> 
> Good luck with whatever you end up with. :)

Thanks, Chris! I very much agree with that approach.

Re: Adium defaults

[Robert Vehse]

Hi folks,

With a beta of 1.6 on the horizon, I'd like to talk about some of Adium 
defaults. About a year ago Rick Fillion of Black Pixel (Kaleidoscope, Versions, 
NetNewsWire) went to the trouble of giving us detailed feedback via email on 
why he is unhappy with Adium's defaults and Peter Hosey forwarded the email to 
us for consideration: 
http://markmail.org/message/m3f777mmqu66tqaa?q=default+list:im.adium.devel#query:default
 list:im.adium.devel+page:1+mid:m3f777mmqu66tqaa+state:results. Nothing came of 
it back then but I think now is a good time to make substantial improvements 
that don't necessarily mean a lot of work.

> I just want to start by saying that I really truly do like Adium.  It's a 
> good app, and I use it heavily every day.


> I get a lot of people asking me what the best way to get MSN or AIM on a Mac. 
> The answer for this is very clear in my mind: Adium.  And so that's what I 
> recommend.  Basically everyone I recommend it to goes and tries it out.  But 
> very very few end up sticking with it.  Why? Cause the default install turns 
> just about everyone off except those of us who know that we can go and tweak 
> it to turn down the suck. 


Rick's critique touches very different aspects of Adium's defaults but one 
particularly struck a nerve with me: default notifications.


Default notifications

> - Sounds.  It's tacky.  Unless my Mac has something VERY important to tell 
> me, it better not make a peep.  Certainly not every time I get a message.  I 
> turn that off immediately.  All sounds.
> - Growl Messages.  Treat it like sound, only a smidge less severe.  It's not 
> cute, it's not flashy, it's annoying.  A growl alert takes my focus away from 
> whatever I was doing (usually something significantly more important than 
> IM). Tell me something important, something that warrants my attention.  
> Think _hard_ about that one […]


I really can relate to that criticism. From what I've gathered over the years, 
many users are unhappy with the high amount of default notifications (two 
examples from the last two days: 
https://twitter.com/steveklabnik/status/331848672918769665, 
https://twitter.com/kaelifa/status/332123768749178881). As far as I can tell, 
even most of us on the Team turn off many of the default notifications.

The number one reason for this default setup I've been given is 
"discoverability", that is pushing all options in the user's face so that they 
know about them. However, as Rick mentions above, only those who bother and are 
somewhat technically inclined will go and check out the events settings to make 
changes, many will just move on to the next piece of software if they are too 
pissed off. So in my opinion, we should choose "sane defaults", defaults that 
make sense. People shouldn't be forced to figure out our events preferences to 
make Adium fun to use. If people add more notifications or use a different type 
of notification, they can still go and discover the possibilities.


Toolbar items

> This is really just scratching the surface.


Rick Fillion didn't specifically comment on our current selection of default 
toolbar items in the chat window but I've seen it being criticised many times 
as well (Paul Wilde last brought this up: https://trac.adium.im/ticket/15400). 
The toolbar is definitely too crowded and crammed with some rarely-used 
functions. Arguably, only frequently-used functions should be given this much 
permanent space in the UI.


Let's review these two areas of defaults, notifications and toolbar items, for 
Adium 1.6. I've set up pages on our Wiki for discussion: 
https://trac.adium.im/wiki/DefaultsReview2013.


Cheers,
Robbie

Re: Adium Reborn - UI proposal

[Robert Vehse]

Hey everyone,

First of all, thanks a lot for your work, Oskar and Dawid.

Here are some thoughts I have on the proposal. I will pick aspects that I find 
most interesting.

Visual/aesthetic aspects
The presentation seems to suggest a completely custom-coded window. I'd venture 
to say it's unlikely for someone to come around and re-code the entire chat 
window. Also, in my opinion, customisability, especially in the visual 
department (contact list, message view), is one of Adium's strengths, I'd 
rather not lose that. As a result, my approach to realising some of what the 
concept envisions would be an evolutionary, pragmatic one. I'm thinking about 
how aspects could be implemented based on the current state of Adium as an app 
and as a project.

To me, the most visually striking aspect of the concept is its minimalism. The 
most prevalent colour is white. That way, relevant parts of the UI, its content 
(user names, status, messages etc.), are highlighted which is a good thing.

So the question is: how can we tone down Adium's UI to achieve this minimalism? 
Well, obviously the message view part wouldn't be too hard. A message style 
should easily accomplish this. I suspect styling the toolbar and the tabs is a 
lot more difficult. As of 10.8 the toolbar is still somewhat of a system 
standard in OS X so we would probably want to start with the styling of the 
tabs. I really do think the tabs could use some work.

Functional aspects
Chat window: message view
- emoticons in the input box: this idea has been around for some time 
(https://trac.adium.im/ticket/484) and its implementation isn't far from being 
done, I believe, Adrian just needs to finish the work he did in his branch 
(http://hg.adium.im/adium/shortlog/b06ab45b7b91)
- inline images: I believe the message view supports this, at least in theory?
- inline video: there's an outdated plugin for Youtube videos: 
http://www.adiumxtras.com/?a=xtras&xtra_id=6655. Would (message view) 
performance take a hit with inline videos? I think I wouldn't mind them if they 
are not displayed too large.
- message read/replied indication: I like that.
- setting status in the chat window: it's a good idea but I prefer the idea of 
implementing this in the toolbar the way George Lambrou suggested it with his 
"Me button" in his "Adium Next" concept 
(http://markmail.org/search/?q=lambrou&q=list%3Aim.adium.devel#query:lambrou%20list%3Aim.adium.devel+page:1+mid:b7sn4zfroaxy42mv+state:results,
 PDF attachment included)

Chat window: toolbar
- reducing the default amount of items in the toolbar has been suggested 
numerous times before (Paul Wilde last brought this up: 
https://trac.adium.im/ticket/15400) and rightly so. The default toolbar is way 
too crammed. In fact, I was going to address this here on the mailing list soon 
and I still intend to do so

Chat window: tabs
- service icons on user icons: I'm not fan of this idea, Adium tries to be 
service-agnostic.

Dropbox integration
I feel the message view isn't the most logical place for a drop zone, maybe a 
toolbar items would be suited for this? We could allow integration of other 
services such as Cloud.app or Droplr as plugins.

Menu bar item
- active input: maybe a bit too geeky for the average user

So much from now. I'd be interested in hearing the opinions of others, 
especially our active developers. :)

Cheers,
Robbie

Re: Akismet on Xtras comments

[Robert Vehse]

(Oops, only replied to the list by mistake the first time around.)


Hi Jeroen,

We spoke on Twitter. :) I'm glad you're interested in helping us out. Spam on 
the Xtras site has been pretty annoying.

I'm afraid I don't know anything about the code as I'm not a programmer of any 
kind. Someone will be able to comment on that.

> And the other thing is that I've never worked with Mercurial. I'm a git guy 
> but I thinks there's no git repo of the Xtras website. If somebody can help 
> me with that it should be easy and fast.

Mercurial isn't very different from Git from what I've gathered. Let us know if 
you run into any stumbling blocks. "hg 
clonehttp://hg.adium.im/www/adiumxtras.com/"; should get you the code for 
starters. Also seehttps://trac.adium.im/wiki/GettingMercurial.

Cheers,
Robbie

Re: Akismet on Xtras comments

[Robert Vehse]

Hi Jeroen,

We spoke on Twitter. :) I'm glad you're interested in helping us out. Spam on 
the Xtras site has been pretty annoying.

I'm afraid I don't know anything about the code as I'm not a programmer of any 
kind. Someone will be able to comment on that.

> And the other thing is that I've never worked with Mercurial. I'm a git guy 
> but I thinks there's no git repo of the Xtras website. If somebody can help 
> me with that it should be easy and fast.

Mercurial isn't very different from Git from what I've gathered. Let us know if 
you run into any stumbling blocks. "hg clone 
http://hg.adium.im/www/adiumxtras.com/"; should get you the code for starters. 
Also see https://trac.adium.im/wiki/GettingMercurial.

Cheers,
Robbie

Re: Twitter in Adium

[Robert Vehse]

Am 21.03.2013 um 05:08 schrieb Frank D :

> With Twitter switching to the 1.1 API and shutting down 1.0, I've
> upgraded Adium's support to work with it.

Yay! Thanks a lot.

> […]
> * I forked STTwitter on GitHub on my account, we could (and maybe
> should) fork it on the Adium account.

I can think of two reasons why it could be beneficial to fork it on the Adium 
account: 1. everyone on the team can easily modify it, 2. they might appreciate 
our official endorsement of the framework (especially with all the improvements 
you made).

> I've also disabled Laconica/StatusNet support as it doesn't look like
> many people use it in Adium and upgrading the framework to support it
> would be more work.

No objections

> I've got the changes committed in both 1.7 and 1.6 and will transplant
> back to 1.5.7 after a little testing has been done. Let's find those
> regressions!

Good idea! I'll try to help though I have to say I only use a very small part 
of the Twitter functionality.


Am 21.03.2013 um 13:14 schrieb Moses Lei :

> Why not keep MGTwitterEngine for StatusNet/Laconica? As far as I know, it 
> still works, yes, since they are still on some variant of API 1.0?
> 
> Moses

Seems like it's a bit large of a dependency for a service hardly anyone uses. 
Plus, someone would need to maintain it and I feel like we should ship services 
we are committed to maintaining (apart from those in lib purple).

Cheers,
Robbie

Re: Website

[Robert Vehse]

Am 17.02.2013 um 21:34 schrieb Paul Wilde :

> Done.

Here: http://hg.adium.im/www/adium.im/rev/9282bb299dea. ;)

Re: Website

[Robert Vehse]

Am 17.02.2013 um 21:12 schrieb Neustradamus :

> Hi guys,
> 
> Last year, I have requested you to change the link http://www.xmpp.org/
> to http://xmpp.org/.
> It will be possible to change?
> 
> Thanks in advance.
> 
> Regards,
> 
> -- 
> Neustradamus

Hi there,

Where would you like it changed specifically?

Regards,
Robbie

Re: BountySource

[Robert Vehse]

Am 17.02.2013 um 19:51 schrieb "Evan D. Schoenberg, M.D." :

> I recently got an email from BountySource, a site that I'd signed up for 
> years ago to check out, that they were alive again. (They'd been shut down 
> for a time, IIRC, due to issues with using PayPal to hold $ for bounties).  
> Might be worth checking out for Adium.  We do have several thousand dollars 
> in donated funds that could be initial funding for bounties if good projects 
> that need manpower were mapped out.
> 
> -Evan

Interesting!

On the topic of donated funds: I think there are donations waiting on Flattr 
(http://flattr.com/thing/425476/Adium-on-Twitter). I vaguely remember having 
tried to sign up in order for us to be able to collect them.

Cheers,
Robbie

Re: 1.5.4

[Robert Vehse]

Hey folks,

Adrian, Eric and I tried to release 1.5.4 yesterday but got stuck. We didn't 
have access to Sourceforge and there was an issue with the build Adrian knows 
more about - the MD5 was missing anyway.

I won't be able to help with it today because I'll be at a concert.

"Detmud", a nice fellow working on a patch for 
http://trac.adium.im/ticket/16221, alerted me to 
http://trac.adium.im/ticket/16203 yesterday. It might be caused by our 
inclusion of the updated "libotr" library. I wonder if the problem should hold 
up 1.5.4's release. Thijs?

Regards,
Robbie

Re: Adium 1.5.4 Release Date?

[Robert Vehse]

Am 04.11.2012 um 04:34 schrieb Neil :

> I was just wondering if 1.5.4 had an expected/scheduled release date, or if 
> it was of a "when it's done" sort of thing?
> 
> Thanks,
> Neil

Hi Neil,

I really cannot blame you for asking, it's been taking longer than intended.

In the last two weeks we have been accepting translations. Our plan was to 
release this weekend and I can see that happening tomorrow (Sunday).

Regards,
Robbie

Re: Cocoaforge spam

[Robert Vehse]

Thanks a lot for the feedback.

For now, I went with a modified version of my initial suggestion, "Which drink 
does this forum's name refer to?", with a case-insensitive "cocoa" being the 
answer and "This forum refers to several software products. Who makes the 
hardware they run on? (one word)" for which "Apple" is the solution (also 
case-insensitive).

Cheers,
Robbie

Re: Cocoaforge spam

[Robert Vehse]

I hate to say it but spam has really gotten out of hand recently.

I'm thinking of trying a Q&A Captcha 
(https://www.phpbb.com/community/viewtopic.php?f=46&t=2122696) with a question 
along the lines of "which drink does this forum refer to?".

Any objections? Any suggestions for a suitable question? (It should probably 
work for users of the whole forum, not just Adium users.)

Regards,
Robbie

Re: Cocoaforge spam

[Robert Vehse]

Am 08.10.2012 um 23:37 schrieb Evan Kinney:

> Forgot about this.
> 
> It's done now. I also stripped out all the phpBB Plus stuff, as it's a 
> defunct project.
> 
> /ek

Thank a lot. :) Let's hope it does the trick.

Cheers,
Robbie

Re: 1.5.4

[Robert Vehse]

Hey everyone,

as far as I can tell we haven't heard back from the Cisco folks yet but I'd 
suggest we go ahead with b2 all the same so localisation can get underway. I 
could help with b2's release tonight and I can prepare an email to the 
translators..

Regards,
Robbie

Re: 1.5.4

[Robert Vehse]

Am 02.10.2012 um 22:39 schrieb Jack Erwin:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Thanks, Evan.  I will get a couple of servers set up and get back to
> you soon.
> 
> Regards,
> Jack

Hello Jack,

have you been able to test the patch?

Regards,
Robbie

Re: 1.5.4

[Robert Vehse]

Am 02.10.2012 um 19:45 schrieb Evan Kinney:

> As soon as the patch gets committed, I'll shoot you a link to a build.
> 
> Thanks so much for your help!
> 
> Sent from my iPhone

I have committed the patch: http://hg.adium.im/adium/rev/61f9ea4acc88. :)

Re: 1.5.4

[Robert Vehse]

Am 01.10.2012 um 09:02 schrieb Joe Hildebrand (jhildebr):

> The WebEx Connect XMPP servers were generating the issue, but we've since
> upgraded TLS stacks so it doesn't happen anymore.  If you can't find a
> server to repro on, let me know, and I'll have someone try an old build in
> the lab.

So how should we proceed? Should the patch still be considered? Is this a 
server-side issue and if so, should it be worked around?


Am 02.10.2012 um 17:19 schrieb Evan Kinney:

> I do not, currently. :)
> 
> Sent from my iPhone

Shouldn't you? Eric? Evan?

Re: 1.5.4

[Robert Vehse]

Am 01.10.2012 um 01:53 schrieb Evan D. Schoenberg, M.D.:

> Since the new code path only happens in case of (err == errSSLBadRecordMac), 
> it seems harmless to commit -- at worst, it doesn't fix the connection error 
> which would have led to an unrecoverable connection failed anyways, and at 
> best it does fix it.
> 
> -Evan

I suppose that could be considered a review. ;)

Evan K, do you have commit access? Otherwise, I could commit your patch while 
your access is set up.

Regards,
Robbie

Re: Meeting Wed 9/5

[Robert Vehse]

Minutes and Cappuccino's log (with encoding issues fixed) are up: 
http://trac.adium.im/wiki/AdiumMeetings/2012-09-05. Please edit as needed.

Thanks to everyone who made it to the meeting!

Cheers,
Robbie

Re: Meeting Wed 9/5

[Robert Vehse]

Here's the obligatory Wiki page: 
http://trac.adium.im/wiki/AdiumMeetings/2012-09-05. Please add items. :)

Cheers,
Robbie

Re: Meeting Wed 9/5

[Robert Vehse]

Am 02.09.2012 um 00:23 schrieb Eric Richie:

> Hey guys,
> 
> I hope everyone had a good summer.
> 
> It sounds like most people are back from vacations and such now, so let's go 
> ahead and get this meeting train rolling.
> 
> Wednesday 9/5 at 7pm EDT (Thursday for some of you) on #adium-devl.
> 
> -Eric

Goodie! :)

This event should also show in everyone's "Adium Development Calendar 2" 
(webcal://p03-calendarws.icloud.com/ca/subscribe/1/aeHhCmJ0EjCq6En9wGQN2z177kxnlDD4lHWDV2NOoFzy5I2QoIX1P3aQPoW170i3q0I6EI9Z70emHdebdrk_HwtcQ7S8HLSJytcIfQ1ztAE).

- Robbie

Re: Cocoaforge spam

[Robert Vehse]

Am 30.08.2012 um 17:08 schrieb Evan Kinney:

> I can definitely update phpBB. I'll get on that this afternoon.
> 
> Sent from my iPhone

Thanks, Evan. We've been missing you on IRC. :)

Cocoaforge spam

[Robert Vehse]

Hey folks,

I see that Zac and I have been banning/deleting a couple of spammers on 
Cocoaforge every week in recent months (people with access see 
http://forums.cocoaforge.com/adm/index.php?i=logs&mode=admin).

Would someone be able to try and stop the spam? Maybe updating Cocoaforge's 
forum software, phpBBPlus, would help. For what it's worth, we are running 
3.0.5 which was released in May 2009, 3.0.11 is five days old. Plus, I found 
some suggested anti-spam measures: 
https://www.phpbb.com/community/viewtopic.php?f=46&t=2122696.

Thanks!

Cheers,
Robbie

Adding a new localisation to Adium

[Robert Vehse]

Hey folks,

Do we have a page that documents how to add a localisation to Adium? If so, it 
should probably mention this file would need to be adapted when adding a new 
one as well: http://hg.adium.im/libpurple/rev/15f40873cec2.

Regards,
Robbie

Re: New FB XMPP

[Robert Vehse]

Thanks, Adrian, looking at the comments it seems it might take them a while to 
get it running reliably.

- Robbie

Re: Adium Development Calendar

[Robert Vehse]

Am 08.08.2012 um 03:49 schrieb Eric Richie:

> While we're on the topic, we should probably schedule a meeting to regroup a 
> bit and further discuss our plans for 1.6 and moving forward.
> 
> What's the preference on meeting time? I know that before we tried to 
> alternate early and late. What are people's schedules looking like these days?

I would suggest holding the meeting after Adium 1.5.3 is released (currently 
planned for Sunday, 12th).

Next week, every evening starting 6pm (UTC) would be fine for me except Tuesday 
and Thursday.

- Robbie

Re: Status icons that ship with Adium

[Robert Vehse]

I'd like to see "Gems" go and be replaced by "Uwy". Sherif does bring up a 
couple of points I hadn't thought about previously which seem important.


Am 07.08.2012 um 11:06 schrieb Sherif S.:

> I like Uwy a lot (didn't know about it until this email), but I would propose 
> a couple of modifications if it will be the default:
> 
> - It does not discriminate between Away and Busy, they're both red. I changed 
> the plist in mine to make Away point to the Idle icon, which is yellow. I 
> think discriminating between the two is useful.

I inspected Uwy comparing it to our current default set, iBubble status. This 
is what I found:
- Uwy has an icon called "Online.png". It looks a wee bit different than 
"Available.png" but I don't really see a point in the differentiation.
- Uwy's NewMessage.png seems to equate to iBubble Status' content.png.
- Uwy lacks busy.png (as mentioned) as well as enteredtext.png and unknown.png.

> - It slightly breaks consistency of the circle-shape perhaps, but purple and 
> blue are not as intuitively relating to "writing" and "new message" like 
> green (available, go!), yellow (might be away), and red (busy, probably don't 
> message) are, and I recommend they be replaced by other more representative 
> ones, such as a pencil with ... after it, or speech bubble, etc. (for 
> example, Stockholm Status Icons: 
> http://www.adiumxtras.com/index.php?a=xtras&xtra_id=3014)

This might be something to consider, too.

> Those are just my humble recommendations, and I don't know how feasible it 
> would be to do this. (I know it can technically be done, but I mean getting 
> permission from original developer(s), potentially making new icons, etc). If 
> Uwy was used as it currently is, I still think it's preferable.

Agreed.

Cheers,
Robbie

Notification Center support

[Robert Vehse]

Hey everyone,

from what I've gathered across our different support venues (Twitter, forums 
etc.) Notification Center support (ticket on Adium Trac) is the most-requested 
feature currently. It also appears that most of you are interested in it as 
well.

However, we need to figure out how we want to go about adding NotificatioN 
Center support. Zac stated his opinion in reply to a pull request. Do you agree 
with that approach?

Regards,

Re: Trac down, Cappuccino down

[Robert Vehse]

I don't know what happened to the nightly build process but the latest .dmg 
weighs a mere 7.4MB and is corrupt.

Regards,
Robbie

Re: Trac down, Cappuccino down

[Robert Vehse]

That's all Greek to me but thanks a lot for sorting it out.

Cheers,
Robbie

Trac down, Cappuccino down

[Robert Vehse]

Hey folks,

it appears both Trac and Cappuccino are down. Cappuccino hasn't been recording 
any activity since the 26th (http://www.adium.im/~cappuccino/%23adium-devl/), 
Trac must have gone down sometime today.

Regards,
Robbie

Re: Plans for 10.8

[Robert Vehse]

Am 25.07.2012 um 21:59 schrieb Thijs Alkemade:

> 
> On 25 jul. 2012, at 17:41, Thijs Alkemade  wrote:
> 
>> 
>> As far as I know, the rule has always been supporting the current and 
>> previous version. Adium 1.5.x has supported 10.6.8 and up, and I propose to 
>> leave that this way. I think 1.5.x has been a pretty stable release, and 
>> with (*fingers crossed*) most of the transcript viewer related crashes and 
>> bugs fixed, I don't think it'll need much extra work.

http://trac.adium.im/wiki/SupportedOSPolicy has been more a rule of thumb than 
a strict rule. Now that Apple is targeting a yearly update cycle we might want 
to reconsider it.

>> From my recent commit on (http://hg.adium.im/adium/rev/a8fef30df88b), 
>> default will require 10.7 to build. This gives us two options for 1.6: 
>> branch from just before this, let it stabilize for a while and then release, 
>> with only the new preferences as a new major feature. Or make 1.6 require 
>> 10.7+, add some more new features with the shiny new APIs, and then release.
>> 
>> My preference would be the second. If we update the UI that much, it would 
>> be a lot nicer if we could use the new localization features of Lion. I also 
>> don't think it would work very well having to test on 3 different OS 
>> versions.
>> 
>> But I just know some people are going to disagree with me. :) Our Sparkle 
>> stats suggest the number of Lion users surpassed our number of SL users only 
>> a couple of weeks ago while it has been out for more than a year.
>> 
>> So, thoughts?

I'm torn.

The new localisation features of Lion really are a major plus from what I have 
been told. What other "shiny new APIs" do you have in mind that Adium can 
benefit from?

On the other hand, the Sparkle statistics also suggest that more than 50% of 
our current user base is using a version of OS X older  than 10.7 (36% on 10.6) 
which would miss out on 1.6.

I guess our decision should be based on the scoping of 1.6. In my mind a 
release of 1.6 consisting of the new preferences layout and updated graphics 
for retina display support would make it a good one and it doesn't look to me 
like it needs a whole lot of more work to get it ready for prime time. What do 
others think?

Regards,
Robbie

Re: Cappuccino died?

[Robert Vehse]

Am 15.07.2012 um 05:47 schrieb Robert Vehse:

> Hey folks,
> 
> It appears Cappuccino went down two days ago.
> 
> Regards,
> Robbie

Would someone be so kind to revive Cappuccino? It's really hard to follow 
what's going on IRC without the logs.

Regards,
Robbie

Cappuccino died?

[Robert Vehse]

Hey folks,

It appears Cappuccino went down two days ago.

Regards,
Robbie

Re: Twitter breakage

[Robert Vehse]

As Thijs and Paul noted in #adium-devl, it looks like Twitter fixed the issue 
on their end: https://twitter.com/tweetbot/status/218435038692392963.

-Robbie

Re: Twitter breakage

[Robert Vehse]

Right! For now I suppose it would be good if someone could just review that 
patch.

Regards,
Robbie

Re: Adium on the 15" MBP w/ Retina display!

[Robert Vehse]

Thanks for sharing! :)

-Robbie

Trac and hg.adium.im down

[Robert Vehse]

Hey folks,

Would someone be able to revive Trac and hg.adium.im? It appears both have been 
down for a while now.

Cheers,
Robbie

Re: Adium 1.5.1

[Robert Vehse]

Hey folks,
For anyone who's missed it: we released 1.5.1 a couple of hours ago.

Thanks to everyone involved!

Cheers,
Robbie

Re: Testing Adium 1.5.1

[Robert Vehse]

Am 07.06.2012 um 16:08 schrieb Eric Richie:

> Thanks guys. Has anyone tried a 10.6 machine?
> 
> -Eric

Yep, it's fine. :)

Cheers,
Robbie

What became of the SSL certificate?

[Robert Vehse]

Hey folks,

http://trac.adium.im/ticket/16014 reminds us of the fact that our SSL 
certificate is invalid (previously reported: 
http://trac.adium.im/ticket/14424). Frank remembers this was previously 
discussed but from the emails 
(http://markmail.org/search/?q=ssl+cert&q=list%3Aim.adium.devel) I haven't been 
able to understand what became of the certificates we acquired and what 
happened since.

Is anyone in the know?

Regards,
Robbie

Re: Adium 1.5.1

[Robert Vehse]

Am 13.05.2012 um 04:33 schrieb Evan Schoenberg:

> Sorry, Robbie; I misunderstood your email. I agree; let's revert that 
> versioning and make a historical branch   for 1.5.1. 
> 
> -Evan

No problem :)

> Thank God for a decent source control system. That was pretty painless. I 
> branched from a near-following revision (4768) as we had some compilation 
> fixes.
> 
> Here's what I did, for the record:
> => hg up -r 4768; hg branch adium-1.5.1; hg transplant 4795 4806 4807 4808 
> 4809 4810 4811; hg push

Cool! I hope the updated versions of FriBidi and ShortcutRecorder don't cause 
any issues.

Cheers,
Robbie

Re: Adium 1.5.1

[Robert Vehse]

Am 12.05.2012 um 00:59 schrieb Evan D. Schoenberg, M.D.:

> Where should 1.5.1 be built from? I see that trunk currently reports as 1.6hg.

I suggested a changeset to branch from. I see you just versioned Trunk as 
"1.5.1b1", I don't think we should include the changes after the aforementioned 
changeset.

-Robbie

Re: Adium 1.5.1

[Robert Vehse]

Am 07.05.2012 um 21:13 schrieb Evan Schoenberg:

> 
> On May 7, 2012, at 1:38 PM, Eric Richie  wrote:
> 
>> On Mon, May 7, 2012 at 2:31 PM, Evan Schoenberg  wrote:
>>> libpurple has been updated to 2.10.4 with 2 security fixes, and I'd also 
>>> like to have us distributing a Developer ID signed binary.
>>> 
>>> We may need to include some explicit parameters (the designated 
>>> requirement) in the codesign line used in the release script, but I'm not 
>>> positive with our current OS X targeting; we're ok on 10.7 without but 
>>> 10.6.8 may need
>>> it to behave properly.
>>> 
>>> Any objections to a beta in the next couple days?
>>> 
>>> -Evan
>> 
>> Nope. Let's do it.
>> 
>> Are you going to be looking into the parameters?
> 
> Yup. I'll take care of it. 
> 
> -Evan

Is http://hg.adium.im/adium/rev/c494bae9da94 a good point to branch from?

- Robbie

Re: Preferences Redesign

[Robert Vehse]

Am 24.04.2012 um 22:15 schrieb Frank D:

> I've just merged the new preferences 
> (http://trac.adium.im/wiki/PreferenceRedesign2011) into trunk. There's been a 
> nightly around for a while and only one ticket left 
> (http://trac.adium.im/ticket/15864) which I haven't been able to reproduce 
> again. I think it's now good enough for the regular nightly people to break 
> it.
> 
> Onward to 1.6!
> 
> 
> --
> Frank

Excellent! :)

Re: Dude, where's my plugin?

[Robert Vehse]

Am 26.03.2012 um 19:26 schrieb Jon Chambers:

> Howdy!
> 
> I recently updated (or so I thought) the sort-by-log-size plugin
> (http://www.adiumxtras.com/index.php?a=xtras&xtra_id=6059) to work
> with Adium 1.5. It appears that the plugin has been removed from the
> search listings, and I can only download the previous version from the
> plugin page. Is this expected behavior (awaiting moderator approval?),
> a bug, or a goof on my end?
> 
> Thanks!
> 
> -Jon

Hi Jon,

It is indeed expected behaviour / awaiting moderator approval. As a security 
precaution, Xtras are hidden from the site when they are waiting on review.

Regards, Robbie

Re: Update: Signing Adium for Gatekeeper

[Robert Vehse]

Am 21.03.2012 um 20:14 schrieb Evan D. Schoenberg, M.D.:

> Him: It doesn't help that there's some doctor with your same name who has 
> registered a bunch of different ways, too.
> Me: ...

Hahaha, that's mad stuff.

Adium 1.5.1

[Robert Vehse]

Hi,

Now that 1.5 is out, I think a branch for 1.5.1 would be in order. 1.6 and 
further releases need scoping but I reckon we can all agree that 1.5.1 should 
mostly cover regressions in 1.5. Objections?

Cheers,
Robbie

Re: 1.5 Release

[Robert Vehse]

Am 15.03.2012 um 22:51 schrieb Eric Richie:

> Awesome! Thanks for the help. Once I get home from work I can help
> with whatever is left to do.
> 
> -Eric

Sure!

I'm attaching here as it still needs some styling (note the  tags). I'm not 
sure whether Paul wanted to do it but I need to get to bed.

-Robbie



	Requires Mac OS X 10.6.8 or later.
	Requires an Intel Mac.
	Added 64-bit support.
	Updated to libpurple 2.10.0.
	
		Removed defunct QQ support.
		Fix double mail notifications on MSN. (#11199)
		Make disconnecting due to flooding on IRC less likely to occur. (#13920)
	
	Many user interface improvements, including updated look & feel for Mac OS X 10.7+


Address Book integration

	Made it easier to choose how names imported from the Address Book are displayed. (#7394)
	Added support for Facebook in Address Book contact cards. (#13755)


Authorisation Requests

	First entry in the list is now auto-selected.
	Toolbar items now behave properly when no request is selected.


Chat Window

	Rounded user icon in the chat window toolbar. (#3757)


Contact List

	Fixed the contact list appearing in a wrong position at startup on Mac OS X Lion. (#15341, #15480)
Improved the logic for the display of tooltips. (Matthew Plough) (#12774)
	Updated the menu for selecting your own picture to look natural on current versions of Mac OS X. (#11964)
	Added support for drag & drop of an image to your own picture to change it.
	Fixed positioning of selected icon in Recent Icons not being reapplied when icon is reselected. (#9908)
	Fixed the contact list shrinking when closing the search. (#14433)
	The contact list search now treats whitespace-separated words as keywords. (Paul Vet) (#14354)
	Added support for blocking/unblocking all contacts in a group. (Conor Branagan) (#2177)
	Added a "Deselect All" option to the "Edit" menu (based on a patch by Tyler Funnell). (#10208)


Dock icon

	Moved the dock badge to the top right to be consistent with other Mac OS X applications such as Mail. (#13439)
	Fixed dock badge text becoming too large. (#13088)
	Removed flashing of the contact name. (#14452)


Encryption (Off-The-Record)

	Made it easier to delete a fingerprint. (Aleksei Gorny) (#1654)
	The "Generate" button is now labelled "Regenerate" when a fingerprint already exists. (Tyler Funnell) (#1128)
	Disable Encryption → Initiate Encrypted OTR Chat menu item if encrypted chat is disabled from settings. (Tyler Funnell) (#7389)


Events and Notifications

	Added the ability to add timestamps to Growl notifications. (Stuart Connolly) (#9920)
	Added a "Do Nothing" event. (#3590)
	Added a "Message sent (Group chat)" event. (Will Bowling) (#12316)
	Added "Message received (Away)" and "Message received (Away Group Chat)" events. (Joshua Stein) (#13278)
	Added Regex support for mentions. (#12832)


"Get Info" window

	Various visual refinements. (Paul Wilde) (#14441)
	Removed the service icon from the top of the "Get Info" window's first pane (and from the contact list tooltip). (#14654)
	Fixed ghosting artifacts in Events tab. (#12237)


Group Chats

	Added support for in-line images, including custom emoticons, on supported protocols. (Peter Fung) (#15183)


iTunes integration

	Use same menu in menu bar, context menu and toolbar.
	Fix bug when replacing tokens with empty strings.
	Make tokens un-localizable.


Messaging

	Added a "Reopen Closed Tab" menu item to the File menu that will restore the most recently closed tab. (#12537)
	Clicking on a link whilst holding the Cmd key opens the link in the background. (Aaron Dodson) (#12129)
	Added Imgur as a supported image uploading service. (Shayne Sweeney) (#13186)
	Removed kl.am as a supported url shortener service. (Shawn Khan) (#14412)
	Fixed link insertion for NetNewsWire. (#11389)
	Added support for Google Chrome when inserting a link to the active webpage.


Message View

	New default message style: Smooth Operator.
Fixed message history only showing in the first tab/window on startup under certain circumstances. (#15377)
	Fixed "Recent messages" still showing with logging. (#12577)
	Added the "lastFocus" class for message styles to the latest message received while the chat didn't have focus, and "regainedFocus" for the first message received while the chat has regained focus after having previously lost it.
	Made emoticons between packs more consistent. (#11450)
Fixed the ":^)" emoticon being mistakenly interpreted the same as ":-\". (#13924)
	Disabled elastic scroll of the text input, in Lion.
	Added the generic menu items to the group chat cog button for XMPP groupchats.


Status

	Added ability to change which track information the "iTunes" status displays. (#6373)


Transcript Viewer

	Added "Next"/"Previous" buttons for highlighted search terms within a transcript (similar to Safari).
	Greatly improved reliability and speed of log indexing and search.
	Fixed a bug when writing inline images to chat logs. (Peter Fung) (#15186)


User Picture (Contact Icon)

	Added abil

Re: 1.5 Release

[Robert Vehse]

Am 15.03.2012 um 21:20 schrieb Eric Richie:

> If someone can get started on the html change log for sparkle
> it would be a big help.

Looks like nobody else is one so I'll take it on.

-Robbie

Re: Icon update proposal

[Robert Vehse]

Hey folks,
Here's a "person silhouette vs duck silhouette" comparison Paul made: 
http://cl.ly/Efq5. Opinions?

Cheers,
Robbie

Fwd: Icon update proposal

[Robert Vehse]

Some more choices to make, opinions to state...For the mention icon, I'd be fine with any of the last three. I prefer the new MessageAlerts icon.Cheers,RobbieAnfang der weitergeleiteten E-Mail:Von: Bogdan Mihaiciuc <bogd...@live.com>Datum: 27. Februar 2012 22:56:20 MEZAn: Robert Vehse <robert.ve...@gmail.com>Betreff: Re: Icon update proposalHelloI just noticed I forgot another icon: pref-mention.png. I think http://img.wixardy.net/Bogdan/Preferences/Advanced/pref-mention.png is too Twitter-centric. George came up with this: http://img.wixardy.net/Current/Preferences/Advanced/pref-mention.png. Something involving a chat bubble and person/duck silhouette would fit nicely, I think, but I think his icon does not blend well with your set.Did that. I thought an at-sign would work well too, since it's often used when mentioning someone. If going with an at-sign, I'd suggest going with the fourth icon.Also consider changing the message alerts icon in advanced preferences to that. -- Bogdan

Re: Icon update proposal

[Robert Vehse]

Hey Bogdan,

I just noticed I forgot another icon: pref-mention.png. I think 
http://img.wixardy.net/Bogdan/Preferences/Advanced/pref-mention.png is too 
Twitter-centric. George came up with this: 
http://img.wixardy.net/Current/Preferences/Advanced/pref-mention.png. Something 
involving a chat bubble and person/duck silhouette would fit nicely, I think, 
but I think his icon does not blend well with your set.

Cheers,
Robbie

Re: Icon update proposal

[Robert Vehse]

> I will use tiffs then.

Sounds good.

> These are the first icons, except notification.
> 
> 
> The badged Block, Add, Unblock all look like Account preferences, sans the 
> background silhouette.

I think you needn't bother about the ErrorAlert one anymore. DefaultClient, 
DockAlert, AnnouncerAlert are all good. And it looks like people can agree on 
the silhouette.

> I'm still not sure about notification, but this is what I have so far.
> 
> 

I like #2 and #4, #1 I find creepy, #3 isn't strong enough.

> I still need to do the smaller sizes for most of these.

Is that still required with tiffs?

Thanks!

-Robbie

Re: Icon update proposal

[Robert Vehse]

I am still not a fan of every second icon in Adium involving a duck and having ducks represent people but it appears the old guard insists...RobbieAnfang der weitergeleiteten E-Mail:Von: Bogdan Mihaiciuc <bogd...@live.com>Datum: 26. Februar 2012 17:44:07 MEZAn: Robert Vehse <robert.ve...@gmail.com>Betreff: Re: Adium icon updateI will use tiffs then.These are the first icons, except notification.The badged Block, Add, Unblock all look like Account preferences, sans the background silhouette.I'm still not sure about notification, but this is what I have so far.I still need to do the smaller sizes for most of these. -- BogdanAm 21.02.2012 um 19:33 schrieb Colin Barrett:I'm pretty much in agreement with Evan here -- eager to see the next round of icons.-Colin

Re: Status: 1.5

[Robert Vehse]

Am 26.02.2012 um 15:02 schrieb Adrian Godoroja:

> Hi,
> i need a few days to figure out a fix for a message view issue.
> 
> Thanks.
> - Adrian

What fix is that? How is it a blocker?

-Robbie

Re: Icon update proposal

[Robert Vehse]

Am 19.02.2012 um 17:23 schrieb Evan Schoenberg, M.D.:

> Looking back over this, I am fine with Bogdan's set overall with a few 
> notable exceptions:

Yay! To be honest I'd have preferred any of the three sets instead of the 
current mix.

>  - I dislike using generic people icons instead of the Adiumy outline.  The 
> two are equally understandable; the Adiumy outline is Adium personality.

I agree on the premise of keeping Adium's distinct personality and the duck 
definitely is an essential part of that.

However, in the case of the particular four icons involving a contact 
(AddContact.png, block.png, unblock.png, pref-accounts.png) I am in favour of 
using Bogdan's icons. Two reasons:
1. I don't like the idea of a duck representing a person.
2. Of the four icons, only two currently have the duck (AddContact.png) whereas 
the other two involve a chat bubble so that's not great with regards to 
consistency.

I can ask Bogdan whether he can come up renditions with the Adiumy outline if 
that is preferred regardless.

>  - I like George's Advanced Prefs icon a lot better for larger display in the 
> main preferences

My thoughts:
- Bogdan's icon is generic (boring?) but consistent with "Advanced" settings in 
other (Apple and non-Apple) apps in OS X.
- The old set's icon has the witty touch of the Einstein formula but George's 
looks sharper. Both do not really blend well with the other icons from Bogdan's 
set.

>  - I would prefer if pref-personal used an Adiumy outline for consistency

Again, I don't like the idea of a duck representing a person. It also doesn't 
match the other icons from Bogdan's set.

>  - The drawing style on pref-defaultclient for Adiumy isn't consistent with 
> his appearance elsewhere

Yeah, that's bad indeed. I will ask Bogdan to fix that up.

> I never saw Paul's detailed email. :\
> 
> 
> 
> I note that the Events section on the voting page is showing them larger than 
> they currently appear in Adium, making pixellation worse.  Paul's comparison 
> (http://cl.ly/4t6t) is more useful.  I think they are a small step forward.

I'd keep the old DockAlert.png until Bogdan fixes Adiumy in his icon. I also 
prefer the old set's old-school microphone (AnnouncerAlert.png). Otherwise, I 
think we should go with Bogdan's for SoundAlert.png and WindowAlert.png.

My plan now would be to commit Bogdan's icons except
- DockAlert.png
- AnnouncerAlert.png
- linkToolbar.png (maybe we should go with the old chain for now)

and ask him to make the appropriate changes to these of his icons:
- pref-defaultclient.png
- DockAlert.png
- ErrorAlert.png
- AnnouncerAlert.png

Regards,
Robbie

Re: Icon update proposal

[Robert Vehse]

> I always thought the whole point of this vote was to get an idea which of the
> three sets was the most accepted allowing us to go with a particular set and 
> to
> then work out the issues we have with this set with its author.
> 
> Choosing each icon by itself and thereby mixing different sets might seem the
> easier solution but it doesn't help Adium's appearance. We are left with an 
> odd
> mélange of different styles.
> 
> So my proposal would be to choose a set and to improve it. Both George and
> Bogdan have shown they are responsive and open to suggestions.

Nobody responded to this (or Paul's email prior to mine) but I'd like to see 
this put back on the agenda.

There are two major reasons why I disagree with the selection of icons made by 
Evan and Zac:

1. Icons from all three sets (current, Bogdan's, George's) were chosen which 
results in Adium looking pretty inconsistent. (Paul elaborated on this in his 
email from February 27, 2011 - http://markmail.org/message/4cehenuhfiu6z3xm)
2. The choice is pretty random and doesn't reflect the results of the vote 
(http://wixardy.net/adiumIcons/;http://wixardy.net/adiumIcons/pics.php).

We really, really need to settle on one set and go from there if we want to 
achieve any kind of consistency.

Regards,
Robbie

Re: Twitter: To be or not to be!

[Robert Vehse]

Am 09.02.2012 um 01:47 schrieb Evan Schoenberg, M.D.:

> Here's a suggested reorganization:

I like that.

-Robbie

Re: Adium Website

[Robert Vehse]

Am 08.02.2012 um 22:35 schrieb Paul Wilde:

> Hey guys,
> 
> I've been working on a new design for the Adium website

I love it, it's what the doctor ordered. The quibbles I have with it are minor 
and could be worked out later.

-Robbie

Re: Twitter: To be or not to be!

[Robert Vehse]

Am 07.02.2012 um 22:06 schrieb Adrian Godoroja:

> Hi,
> 
> i've bumped a few services to the top list. 
> (http://cl.ly/0r002c2S0O0F1b332O1y)

Good!

> The question is Twitter, do we want it in the top list or not?

Not, in my opinion.


Am 07.02.2012 um 22:13 schrieb Eric Richie:

>  It's definitely a mainstream service at this
> point (more so than something like Jabber, which we list in the top
> grouping).

True. However, if you look at our Sparkle stats for this year 
(http://adium.im/sparkle/?year=2012&week=*&graph=bar#IMServices), you will find 
that very few use Twitter and while Adium's support for it fits my very basic 
needs I can see why many others feel different about that. It's very much like 
with IRC: we have basic support for the service but it appears it doesn't meet 
the requirements of many users.