Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add /twitter_info #20

Closed
wants to merge 13 commits into from
Closed

add /twitter_info #20

wants to merge 13 commits into from

Conversation

mmitch
Copy link
Contributor

@mmitch mmitch commented Nov 8, 2010

/twitter_info shows information about cached tweets.
Currently, only the URL of the tweet is reconstructed from the tweet's ID.

If one of the pull requests adding timestamps is merges, the tweet's timestamp can be cached as well.

show information about a cached tweet (currently only the URL)
@mmitch
Copy link
Contributor Author

mmitch commented Nov 8, 2010

should be possible to also display the account that downloaded the tweet.
would this information be of any use?

@zigdon
Copy link
Owner

zigdon commented Nov 8, 2010

I think showing as much info as available would be great. Might also include "in-reply-to", or even a whole conversation tree.

One bug - it assumes the URL is a twitter.com URL, and ignores possible identica users.

@mmitch
Copy link
Contributor Author

mmitch commented Nov 9, 2010

nick, id, tweet text, account and service are now displayed
identica URLs should work, but I have not verified this

%state had to be extended to cache {__acounts} and {__services}
support for timestamps is already there (currently commented out)

$state{__indexes}{$nick} and $state{$nick} contain different notations of the nickname
Remember ID and username of the original message when a reply is encountered.

It looks like Net::Twitter only marks replies in timelimes, not in
searches/subscriptions, so we can only show this information on
timeline tweets.
URLs work with lowercase nicks too, but why not?
I'm actually using this to try to hunt a bug down :-)
But as we have this information, why not store and show it?
only showing tweet ID is rather pointless
@gedge
Copy link
Collaborator

gedge commented Jul 19, 2011

included in latest beta

@gedge gedge closed this Jul 19, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants