Quote from: marcus_of_augustus on June 27, 2013, 09:46:49 AM

Quote from: elqntdotorg on June 26, 2013, 09:37:24 AM

I've been working on a new peer-to-peer exchange that employs WebRTC for the past few weeks.

It's pretty unique because it fully complies with FinCEN's regulations around exchange because all communication in the platform is conducted directly peer-to-peer and subsequent exchanges are conducted physically by the respective exchangers (I'd love to employ an online transfer in further iterations, but don't have a good solution yet).

I just went live with an early alpha tonight if others would like to try it out and give feedback.

My primary goal with the platform is give as much anonymity as possible, meaning that I self-host all files (no external js). I'm stuck using an external tile-server (which means mapquest logs some data, including IP + timestamp), but I hope to get some capacity soon to bring that in-house as well so no external logging of users occurs (beyond ISPs).

The site is elqnt.org (pronounced eloquent).

Best,
Stephen

Looks slick ... what are the mechanics/specs on the back-end security ... TLS comms, etc?

In follow-up to back-end security --

I host the web server and peer server in-house.
Analytics utilized (Piwik) are self-hosted as well, in-house. I also plan to let users opt-out of ananlytics, but haven't had time yet to set this up.
All JS is self-hosted as well, in-house.

Basically this means no external logging occurs, except for the tile server (for the time being) and any other ISP related logging.

Tile server uses ssl, but is currently hosted through MapQuest and serves Open Street Map tiles. I'd like to bring this in house, but the hardware requirements are a bit beyond what my stuff can swing at the moment. For details on the data they collect, check it out here -- http://developer.mapquest.com/web/info/terms-of-use
Specific section in their ToS is: ACCESS AND USAGE DATA > Usage Data