@saifalfalah Just by looking at the traffic it appears the screenshot is first uploaded to their server (82.196.13.85 / seedshot.io / zapsnap.io) then it's downloaded from their server to your browser, at which that tab then becomes a peer, which other people download the image from. Not to sure why the images get uploaded to their server first, surely the image could be passed from the zapsnap app to Chrome... Also more info is on their GitHub page: https://github.com/twobucks/zapsnap
@saifalfalah@adriel thanks for explaining how it works. Maybe it would be possible to do it with some sort of Chrome extension, to avoid server completely, but then it would only work for Chrome. I'm a noob when it comes to Chrome extensions so I decided to do it the way you described.
@shimetweets Hey, no worries. Just curious why you can't jump from the menu bar app direct to the browser, couldn't you run a mini web server in the menubar app to which the browser initially connects to? That way no external server would be needed. I don't know, just thinking out loud.
@adriel That way would only work on localhost, so it wouldn't be publically accessible. We are also running a DB server, but that could be avoided. The biggest problem with your approach is mapping requests to info hash of the torrent. With the current approach we map image hash from URL to info hash of the torrent.
@raphchabaud sorry about that, Raphaël. I didn't have time to do that for the MVP. I'll personally notify you on Twitter once we add support for Windows.
Journmail
Journmail
Foreign Ipsum
Journmail
Journmail
Foreign Ipsum
Journmail