4 ms·
Interesting project. Would be keen to hear about technical details. How real-time is the data? I noticed a lot of repeating images so I'm assuming the data is
by ux-app 13y ago
Interesting project. Would be keen to hear about technical details.
How real-time is the data? I noticed a lot of repeating images so I'm assuming the data is collected and batch processed? Or are the images being fetched directly using the twitpic API?
Any reason for using canvas element instead of images or CSS backgrounds? My gut would suggest that loading an image and then painting to the canvas would incur a greater overhead than simply setting an img src attribute.
The page is generating a ton of traffic. A sustained 80-90kb/s for me. Within a few minutes the count was up to 50mb+ of image data!! Are the images all hotlinked from twitpic or are you doing your own storage and using a CDN?
Would be nice to be able to slow down the stream a bit.
- Wilya 13y agoNot the author but: - Repeated images probably come from quoted tweets (when you quote a tweet and reply by adding something). If you pull a twitter API feed, you'll get many of these. - Not sure, but it's possible that ever-changing images cause lots of reflow. What happens between the moment you set the src attribute and the moment the image loads ? I'd have to test, but I think a reflow of everything is worse than painting to canvas. - Looking through dev tools, images are hotlinked.
- geuis 13y agoData comes directly from twitter live. Canvas is much more performant. Your gut is wrong =). Look at the network tab. All data is delivered from the source. I've thought about more features. Stay tuned.