• Cams

  • Someone else tying as me to Cam Girls

Hello, So I had a weird experience last night and wondering if anyone else has experienced this. I was having a good time with a cam model in public, tipping lots for actions, etc, and talking with her via text. Next thing I know, someone else starts typing to her as well, but under my name. So this of course confused the model, and she did not know what was going on when I tried explaining there was someone else using my name to talk. It probably looked like I lost my marbles.

Has anyone else experienced this? Is there a way to prevent it? I do not like that it ruined my experience, and the person doing this got to continue on with her after I left the room thinking she was still talking with the person that had tipped her so much.

Ugh, title should have been "Someone else TYPING as me to Cam Girls"

    Hi spyeagle we’ve seen similar behavior in the past from some users. Here is what we can do, please raise a ticket here: https://www.sexlikereal.com/pages/contact and include the day when it happened, the model, and the approximate time if possible. The potential outcome would be to ban the user and check if they have any other accounts.

      Can confirm what @PabloSLR mentioned here. In addition to that, camgirls should also have a slightly different view of their chat, similar to us mods here on the forum. So, in theory, camgirls should be able to differentiate two users from one another, although I don't know the full details on their end.

      We brought this up in the past and will definitely bring it up again to avoid confusion and concern 👍️

        Megas_SLR In their SLR profiles, users can change their alias which is the name that will appear in the cam chat. As it seems that it is possible to change one's alias to the name of a heavy tipper, can't you just prevent that on your end by not allowing two users in the system having the same alias?

          That's the thing, the system we have in place does work, it's the shared info with camgirls' system that's causing the issue. We brought it up to them, though and are working towards getting answers and a resolution