[throw14082020]

What do you mean by anonymous connections? Without them being logged in and you actively tracking them, it is anonymous. You'd be reinventing the wheel to de-anonymize the user if you want to track users across devices, which is certainly not anonymous: existing companies use advertising IDs or cookies, based on the problem. There is no way you can identify users across devices devices (or solve this problem better) than Google and Facebook, since you run in 1 application, they run in almost all of them.

"We did look at syncing all this with RTC data channels,", that's when you use a reliable service with additional functionality like history and presence, not WebRTC data channels, that might be why you struggled. It sounds like you should be using WebSockets for this type of data.

It sounds like you're trying to build chat for ecommerce websites, but isn't that Intercom, tidio.com (free tier alternative). Agora is lower level, but also solves these problems and more: messaging, audio, video calls. I don't think any of these offer cross device identification without having users log in on all their devices.

[ejb503]

"I don't think any of these offer cross device identification without having users log in on all their devices."

Exactly, we have...

I wrote a little blog about it: https://yown.it/live-video-call-webrtc

If that doesn't explain it well enough I'll just assume you see being intentionally aggressive!

None of the above solutions enable users to easily manage personalized commerce experiences without paying a developer!!

[throw14082020]

Since you advertised yourself as a solution to some problem, I first wanted to find out what the problem was, and then see how you are solving it. I don't know either at the moment (I've read the product hunt too). I did visit the yown.it website, and still didn't understand. Now I have read that blog post, and I still don't understand. That blog post served to explain that you didn't read enough about WebRTC before trying it. You didn't know that WebRTC doesn't specify signalling, but this quite literally a basic concept in WebRTC, have a read of the introduction section. https://www.w3.org/TR/webrtc/#introduction

> Exactly, we have...

I guess it also works when using TOR...