Open GoogleCodeExporter opened 9 years ago
Original comment by pamela.fox
on 3 Oct 2009 at 12:32
also doesn't seem to populate the usernames for the people I follow. Or it
happens sporadically or on a refresh. Most say "Tweety the Twitbot" -
refreshing the wave seems
to fix.
Original comment by bjkamin...@gmail.com
on 3 Oct 2009 at 12:59
I think i may have filed this in the wrong area. if that is the case please
close
this :)
Original comment by Black.D....@gmail.com
on 3 Oct 2009 at 5:50
Thanks, CCing the author of Tweety. Note that Tweety isn't production-ready yet
-- it
serves only as a demo. So, it's not a good idea to use it on Google Wave
preview with
your friends and family. :)
Original comment by pamela.fox
on 6 Oct 2009 at 6:00
Yes, but Apparently people like working demos, even in dev previews :)
Original comment by Black.D....@gmail.com
on 6 Oct 2009 at 6:06
From what I understand, it's a problem with the Java API handling cron requests
for the robot. I managed to get
a Python robot up and running successfully *with* cron events after digging
through the source code (horribly
undocumented) so it's definitely not the system, and perhaps the Tweety code
just needs to be updated and
redeployed. If you're a Java guy, you can probably just check out the source
and deploy it yourself on App Engine
with minimal tweaking. I will say that it is very sad that what seems to be the
flagship Wave robot isn't practically
usable right now. Better hurry before the general public gets on Wave and is
sorely disappointed in what we've
been telling them is "the future."
Original comment by xdiss...@gmail.com
on 6 Oct 2009 at 6:41
[deleted comment]
Any chance on an update ?
Original comment by steffan....@gmail.com
on 23 Nov 2009 at 7:16
having the same issue: tweety doesn't update twitter information.
Any updates?
Original comment by jorpe...@gmail.com
on 10 Dec 2009 at 5:35
It is not updating for me either. I guess I will be using tweetdeck for
awhile.
Original comment by edmonton...@gmail.com
on 8 Jan 2010 at 7:14
Original issue reported on code.google.com by
Black.D....@gmail.com
on 18 Aug 2009 at 12:55