Skip to main content

One post tagged with "twitter"

View All Tags
IntelSocial

Social signals (June 30): XPoint desktop/WiFi geo friction on BetRivers; GGPoker freeze flagged; DE boundary complaint

XpointRushStreet Interactive (BetRivers)
socialbetriversxpointreddittwitter

Source. June 30, 2026 weekly sync — End-user Feedback (Valeria).
Dataset. Social Media Competitive Signals · Reddit + X/Twitter public posts.

GGPoker / WSOP (former 888) — flagged for awareness

A GGPoker / WSOP player (former 888, XPoint deployment) reported to us that a location-related issue causes the game screen to freeze/blink, preventing any in-game action.

GGPoker is no longer a current GeoComply customer, but the report is flagged given competitive relevance in the poker / iGaming space.

BetRivers — RSI feedback scan summary

Since the XPoint migration, there is a recurring pattern of desktop / WiFi geolocation failures that do not show up on mobile:

  • Users on PC are flagged as out-of-state despite testing multiple browsers, networks, and even public WiFi.
  • The same connection works fine on phone / tablet.
  • Common workaround: switch to cellular-only or disable whichever network interface is not in use.

Representative quotes:

"Hello since they went to the new xpoint software I can no longer use my pc they keep thinking im playing out of state when im not. I have tried multiple pcs browsers my neighbors internet even using a pc at walmart with there internet and it doesnt work" — Reddit, May 19, 2026

"Started doing this to me this morning and I don't use a VPN. What I still can't figure out is that with Betrivers it won't let me place bets when I'm connected to my home wifi. I have to disconnect and only use cellular with Betrivers. Every other app is fine. This started about a month or so ago." — May 2026

Additional signals

  • Apple App Store review (June 21): consistent location-verification failures blocking bet submission. Workaround: navigate into support and back — but that triggers new scrolling / UI bugs.
  • Twitter (April 21, June 9): geolocation described as inconsistent and "needing a serious update" — users report app reinstalls sometimes required to temporarily fix it.
  • Delaware user (April 17): told their location was invalid while physically in-state on the Delaware-specific platform — suggests the boundary / geofence detection issue is not limited to ambiguous border cases.

Why it matters

Public friction on BetRivers aligns with the June 23 / June 30 Pennsylvania field-test gaps on XPoint — desktop geo is failing users in production while mobile often works, and the same vendor missed sustained RDP sessions in controlled testing the same week.

June 30 weekly sync → · BetRivers PA CIV-88 retest (June 30) · BetRivers social brief (June 23)