The below is an off-site archive of all tweets posted by @mjtsai ever

June 1st, 2012

@drewmccormack The odd thing to me is the rush to require it before the technology was close to ready. Does that make it faster long-term?

via Hibari in reply to drewmccormack

@siegel May the odds be ever in your favor.

via Hibari in reply to siegel

@dinh_viet_hoa For now, yes, although I’m not sure if anything happens on the receiving end when Growl itself becomes sandboxed.

via Hibari in reply to dinh_viet_hoa

@dinh_viet_hoa My understanding is that, before 1.3, the Growl SDK requires a temporary Mach entitlement to post via distributed objects.

via Hibari in reply to dinh_viet_hoa

@nriley As far as I can tell there’s no need to rush. Old version is solid. New network/GCD implementation needs to be reworked post-1.4.

via Hibari in reply to nriley

The experiment of going back to the Growl 1.2.3 SDK seems to be working. No more CPU spikes or crashes. (But it’s not sandboxable.)

via Hibari

@danielpunkass Cool. That’s been on my to-do list for a while. Surprised more apps don’t do this.

via Hibari in reply to danielpunkass

@danielpunkass Is that built-in, or pulled from your server?

via Hibari in reply to danielpunkass