Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Watching this module's development with interest. I just wanted to suggest that in addition to views filters, you might create an argument for search term - this would really give a lot of power over what tweets show up on what pages. I'm thinking of CCK fields or taxonomies for hash searches that could be associated with nodes, sections of the website, etc...
Cheers!
Comments
Comment #1
dragonwize commentedInteresting idea. I will have to think on that one though because it is a break from how the module is meant to work.
That would be getting dynamic search terms and then would have to make live calls back to twitter for results. Currently the module is integrated with the twitter module that caches and stores the tweets on cron runs.
So while it shouldn't be too hard, it will definitely be a different approach and anyone using it would have to be aware of the performance implications unless we implemented some kind of caching rules of our own.
Comment #2
dafederActually, now that I think about it, on a site with any decent level of traffic, this could run up against the API limit very quickly. Maybe it's not a very viable option.
Comment #3
summit commentedSubscribing, greetings, Martijn
Comment #4
dragonwize commentedI think dynamic searches of some time would be great. We would need to implement a nice cache layer though to make it feasible.
Postponing until someone is working on this.
Comment #5
sheldon rampton commentedIf someone would like to write a patch to add this functionality, I'd be willing to consider it. However, I don't have time myself to work on it other than testing it if someone else writes it.