Martin Dufort's dashboard

Martin Dufort started following the idea "Calendar integration and support in Postbox" in Postbox, Inc..

Martin Dufort asked a question in Postbox, Inc. on April 24, 2009 03:23:

See list of BCC from sent email

When sending an email with a bunch of BCC, there is no way to see the list of BCC from the retrieved email in the send Mail section.

Martin Dufort replied on March 26, 2009 13:56 to the problem "Support of .ics attachment in Inspector pane not working" in Postbox, Inc.:

I'm forwarding you that same invitation... Thanks for looking into this. This is really bugging me and preventing me from doing a complete switchover from Mail.app

Martin Dufort replied on March 26, 2009 00:26 to the problem "Support of .ics attachment in Inspector pane not working" in Postbox, Inc.:

I've downloaded the b10 build and I'm still not seeing the invite properly. I have this text:
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2007
VERSION:2.0
BEGIN:VTIMEZONE
TZID:New Zealand Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+1300
TZOFFSETTO:+1200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=4
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000

at the beginning of my email the event section in the inspector is populated with a file that is not openable.

Martin Dufort replied on March 16, 2009 22:28 to the problem "Support of .ics attachment in Inspector pane not working" in Postbox, Inc.:

However in the Mail.app on OSX, for the same mail message, the invitation is shown as both text and as an attachment that can be opened by iCal.

Martin Dufort reported a problem in Postbox, Inc. on March 06, 2009 14:21:

Support of .ics attachment in Inspector pane not working

Postbox does not show attached .ics invitation in Inspector panel. Invitation only showed as text so there is no way to accept or deny the invitation.

Martin Dufort started following the problem "iCal invite attachment comes up as text" in Postbox, Inc..

Martin Dufort replied on November 21, 2008 15:40 to the question "Tweetsville crashes at startup." in Tapulous:

Updated to TweetsVille V1.1. Still crashing on startup. Here's the console output:

Fri Nov 21 10:36:06 unknown kernel[0] <debug>: Tweetsville 2842 FS_WRITE_DATA SBF /System/Library/Frameworks/Security.framework/TrustStore.sqlite3 13 (seatbelt)
Fri Nov 21 10:36:10 unknown Tweetsville[2842] <warning>: *** Assertion failure in -[TVTimelineController tableView:cellForRowAtIndexPath:], /Users/jess/Source/Tweetsville/trunk/Classes/TVTimelineController.m:495
Fri Nov 21 10:36:10 unknown Tweetsville[2842] <error>: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Item not found in database!'
Fri Nov 21 10:36:10 unknown Tweetsville[2842] <error>: Stack: (\n 808221155,\n 806100820,\n 808035755,\n 812497771,\n 19981,\n 816419340,\n 816420548,\n 816494672,\n 816447444,\n 816291648,\n 836031656,\n 836031416,\n 836029236,\n 836028412,\n 807837997,\n 807836001,\n 807834471,\n 827655876,\n 816145636,\n 816184028,\n 8343,\n 8244\n)
Fri Nov 21 10:36:10 unknown UIKitApplication:com.tapulous.Tweetsville[0xb328][2842] <notice>: terminate called after throwing an instance of 'NSException'
Fri Nov 21 10:36:11 unknown ReportCrash[2844] <notice>: Formulating crash report for process Tweetsville[2842]
</notice></notice></error></error></warning></debug>

Martin Dufort replied on November 18, 2008 03:45 to the problem "Quickly scrolling the Tweetsville timeline makes the application crash" in Tapulous:

Ed: I sent Zach the Console log from the iPhone Configuration utility.

Martin Dufort replied on November 18, 2008 01:52 to the problem "Tweetsville crashes when scrolling through the timeline." in Tapulous:

Zach: The console output for the timeline scrolling crash is in your inbox. L8er

Martin Dufort replied on November 18, 2008 01:44 to the problem "Tweetsville crashes when scrolling through the timeline." in Tapulous:

This is now happening everytime. I've got the console output from the iPhone Configuration Utility. Where can I send it ?

Martin Dufort reported a problem in Tapulous on November 13, 2008 18:46:

Quickly scrolling the Tweetsville timeline makes the application crash

Quickly scrolling back and forth the timeline makes the application crash

Martin Dufort replied on November 13, 2008 17:28 to the problem "Tweetsville crashes upon fetching the timeline" in Tapulous:

+1 here. Changing to US region (Settings -> International -> US) from Canada works after deleting and reinstalling the application.

Martin Dufort replied on November 13, 2008 17:22 to the problem "Tweetsville crashes upon fetching the timeline" in Tapulous:

Same problem with Canadian settings

Martin Dufort started following the problem "Tweetsville crashes upon fetching the timeline" in Tapulous.

Martin Dufort replied on October 25, 2008 23:42 to the question "Default action should be define per contact" in Instinctive Code:

Super that will be a big plus for me on the usability side.
Thanks

Martin Dufort asked a question in Instinctive Code on October 25, 2008 20:56:

Default action should be define per contact

Right now the default action is defined at the application level. I think it would make more sense to define it at the contact level. I have some contacts which I mostly use SMS with them and it would be great to specify that as their default action. Other emails, other phone.

Overall this is really, really good. Congrats Matt.

A comment on the idea "Automatic Check-ins == You Win" in Brightkite:

Excellent summary Josh. – Martin Dufort, on June 16, 2008 14:43

Martin Dufort marked one of Josh Lewis' replies in Brightkite as useful. Josh Lewis replied to the idea "Automatic Check-ins == You Win".

Martin Dufort replied on June 14, 2008 14:54 to the idea "Automatic Check-ins == You Win" in Brightkite:

I've been requesting a read from FireEagle from quite some time now. The BrightKite are saying it is in the roadmap but we do not seem to get a straight answer as to when it would be implemented. I completely stopped using BK until this is done as I do not want to update my location in 20 different spots.