2 ms·
Interesting idea. Some things I've noticed: 1) It could use a description on the main page, so that new users know what they're in for. 2) Scrolling through t
by Samuel_Michon 16y ago
Interesting idea. Some things I've noticed:
1) It could use a description on the main page, so that new users know what they're in for.
2) Scrolling through the result page (using the mouse's scroll wheel) makes my browser stall for > 10 seconds before loading new entries. (Firefox 3.6.3 on Win7)
3) The 'beta' badge on the main page has a very light yellow color, which makes the white text hard to read. The label text could also use some letter spacing.
4) The 'y' in the ReadEvery logo is cropped a bit too much, making it look like a 'v'.
5) The results page could use some filter options, to focus on location or relevancy. It would also be nice to be able to remove users from the list on a case-by-case basis.
6) Retweet and reply buttons (per tweet) would be also be nice.
- combiclickwise 16y agoI see what you mean. It definitely needs to be fixed on Firefox. Thanks a lot.
- combiclickwise 16y agoThanks for your time on this. Really appreciate it. I am working on the remove/unfollow user functionality already. The retweet/reply buttons is a very good idea :-) I had not seen the cropped 'y'. Will fix that too
- Samuel_Michon 16y agoAnother thing that just occurred to me: since you're presenting the tweets out of their context, sorting them purely by user, perhaps it'd be better to remove replies from the flow? That way snippets of conversations wouldn't confuse the reader. I'm assuming this view is meant to find standalone tweets that contain insightful remarks or links/media? Also, how about auto-converting links in tweets into embedded media? (images, YouTube, etc)
- combiclickwise 16y agoauto-converting links.. didn't occur to me at all. Thanks to remove re-tweets, I should probably set that as the default option (removed) and yet provide the user a way to turn it on