Comments on: i.TV Brings TiVo Scheduling to iPhone

By: Justin (from i.TV)

Justin (from i.TV) — Mon, 02 Nov 2009 15:11:28 +0000

@Kevin — Saw your comment. Have you tried sending an email to support[at]i.tv? If that hasn’t worked for you, come visit us on Twitter @mediamyway and we’ll help you out.

By: Kevin

Kevin — Mon, 02 Nov 2009 01:25:15 +0000

I been receiving the SSL read error also when trying to link my tivo account to I.TV. I have not found out a fix yet. i have tried to change my login info on tivo’s website, but that has not worked.

By: Joy

Joy — Sun, 01 Nov 2009 18:22:15 +0000

I am receiving an error message when I try to link my accounts: SSL error 52: SSL read error 140994415:SSL routines:SSL3_READ_BYTES: ssl v3 alert certificate expired, errno0. Did anyone else have this problem? Do you know how to fix it?

By: Brian

Brian — Wed, 24 Dec 2008 05:09:32 +0000

I wish they would get Uverse line ups added so I could use the app and Tivo synching.

By: Todd

Todd — Mon, 22 Dec 2008 21:53:54 +0000

Shame on iTV for not using OAuth and eliminating the need to give out your TiVo ID.

NetFlix supports it though!

http://blog.oauth.net/2008/12/18/oauth-inside

By: John

John — Mon, 22 Dec 2008 21:18:15 +0000

Yep, same error here (about different providers). Too bad.

By: Martin

Martin — Mon, 22 Dec 2008 19:31:25 +0000

I’m with Dave to say that the volume of comments does not warrant threading. Plus, most threading UI’s make you do excessive clicking to read all the comments. I’m lazy and would rather just scroll once. If replies are confusing, I’m fine with scrollig up.

By: Dave Zatz

Dave Zatz — Mon, 22 Dec 2008 19:15:42 +0000

Alex, I won’t be implementing threaded comments via WordPress. Not as long as I have this theme, at least. Also, given the amount of comments I’m not sure it adds a whole lot of value. If I go with an Intense Debate at some point, they have it built in. However, I may implement the WP 2.7 page breaks after X comments. But I won’t actually be upgrading to 2.7. Waiting on 2.7.1 – here’s the evolving bug tracker: http://trac.wordpress.org/query?status=closed&milestone=2.7.1&resolution=fixed&resolution=invalid&order=priority