Riplox 1.2.1 - two things that were telling you something untrue
Two things that were telling you something untrue. Everything from
1.2.0 is
in this build as well.
"Signed in" when the site had no session at all
Signing in reads the whole browser profile, and that profile holds every site
ever signed in through it. So a TikTok sign-in that never completed still came
back with a healthy pile of YouTube cookies, saved them, and the screen said
Signed in — while TikTok had none. It is possible to sign in twice and still
be told to sign in.
The sign-in now checks that the site whose window it opened is actually in what
came back, and says which one is missing when it is not:
No TikTok session was captured. Sign in fully in the window that opened, then
close that window — Riplox reads the session once the window is closed.
The per-site rows in Settings were always honest about this; the line above them
was not.
TikTok: what is really happening
TikTok is refusing the machine, not the video. The page it serves is a 1.4 KB
bot-check shell with no video data in it at all — which is what the engine
reports as "Unexpected response from webpage request".
Everything worth trying was tried against a failing link and measured:
| tried | result |
|---|---|
| plain request | refused |
| five browser impersonations (Chrome/Safari/Android targets) | refused |
| desktop user-agent | refused |
| both alternate TikTok API hosts | refused |
| cookies taken from a real Chrome that had got through the wall | refused |
So "sign in and try again" was not advice, it was a wrong answer that costs
someone an afternoon. The message now says what is actually true: signing in
does not get past it, and a different connection is the only thing that has
helped.
Everything else about TikTok is fine — the site loads, its login page loads, and
the engine has browser impersonation available. It is the video page, and only
on some connections.
Files
| SHA-256 | ||
|---|---|---|
| Riplox | Riplox_Setup_v1.2.1.exe (71.97 MB) |
92D3FE4C49AE889AD47A9110A84CBE8F391E356D68E392E5AED976E6E120E4EE |
| Sender, Windows | RiploxSend_Setup_v1.0.1.exe (18.49 MB) |
C5BB64932B58BB71D656799ACD439ACCB5B7E79C86997EA64EAE6DE599E74CAD |
| Sender, Android | RiploxSend_Android_v1.0.1.apk (97 KB) |
07D0DFE4385E56A0ED761F0926C1216314BDC10085B9D5BEA9579D2352304875 |
Riplox is the app that downloads — that is the one to install, and the only
one most people need. The two senders are unchanged from 1.2.0 and are
optional: install one on a phone or another PC you want to send links from.
Both senders now have their source in this repository, in
send-windows/
and
send-android/.
Installing
The installers are per-user and do not ask for administrator rights. Windows may
show "Windows protected your PC" the first time — these builds are not
code-signed, so choose More info → Run anyway, or check the file first:
certutil -hashfile Riplox_Setup_v1.2.1.exe SHA256
Requires Windows 10 or 11 with the Microsoft Edge WebView2 Runtime, already
present on Windows 11 and on any Windows 10 with a current Edge. The Android APK
is signed but not from a store, so Android will ask permission to install it.
Android 8 or newer.