Polly

Suggestion: Search WITHOUT need for Realtime API

Asked by Michael Tunnell

I understand Realtime API probably takes a LOT of work but I would like to make a request.

Search Functions that don't need realtime:
1. Hashtag Search - this is possible when you click in a tweet but I would like to enter a hashtag myself than rely on someone tweeting it to show in a stream or if it is trending.

2. User Search - you can load profiles in Polly which is awesome but you have to find them tweeting first. It would be great to be able to search for a username and load a profile that way.

3. Specific Tweet Search - insert the url of a tweet somewhere and then go to it directly from Polly.

For Example:
https://twitter.com/MichaelTunnell/status/324713128199847938

Then use the 324713128199847938 portion to display the tweet and maybe conversation.

These would be AWESOME!

Question information

Language:
English Edit question
Status:
Solved
For:
Polly Edit question
Assignee:
No assignee Edit question
Solved by:
Michael Tunnell
Solved:
Last query:
Last reply:
Revision history for this message
Conscious User (conscioususer) said : 		#1

You are simply suggesting search. Search has always been on the plans, I just didn't have the time to implement it yet.

Revision history for this message
Michael Tunnell (michaeltunnell) said : 		#2

I am not simply suggesting search...I suggesting that the non-realtime searches be expanded on while the regular search is worked on in a lower priority.

You already have hashtag search made, allowing users to type in what hashtag to search for would improve the usability of the app but at least tripled.

Yes I am suggesting search but the main issue with the regular search is the realtime API (based on a previous question asked) but these suggestions bypass the need for the realtime API and that is the point.

Any search at all is MUCH better than an error message...even if the search only let you search hashtags to start it would be a big improvement to the usability because it is kind of hard to explain to people who test it why the search always errors.

Revision history for this message
Conscious User (conscioususer) said : 		#3

What I'm saying is that everything you are suggesting has always been on the plans, regardless of priority.

Right now I don't have the time to implement either high-priority items or low-priority ones.

As for explaining why the search always errors, I don't think saying "you are using an incomplete, pre-alpha software" is hard.

Revision history for this message
Michael Tunnell (michaeltunnell) said : 		#4

ok I see and yea it isn't that hard but why not just make the error say that instead?

Revision history for this message
Conscious User (conscioususer) said : 		#5

Because Polly already advertises itself as pre-alpha. So "not implemented yet" should be self-explanatory.