Riplox 1.2.0 - the engine update tells you what it is doing
The engine update, which was the real complaint
Pressing Update engine fetched an 18 MB zip in a single read and said
nothing for as long as that took. Measured on a slow line it arrived at
0.10 MB/s and the connection was dropped at 15.9 MB after 161 seconds — which
is indistinguishable from a hang.
- It now reads in chunks and shows a percentage on the button.
- A dropped connection resumes: the part already on disk is kept and the next
attempt asks for the rest with aRangeheader, instead of starting the
18 MB again. Three attempts, with a growing pause. - Timeouts that fail honestly — 30 seconds per read, ten minutes for the whole
job, and a sentence saying what happened rather than a button that goes quiet. - Once a day Riplox asks which engine version is published and writes one line
in Settings. That check is the releases API, a few hundred bytes. It never
downloads the engine on its own.
Sign-in, one file per site
Captured sessions are stored as one DPAPI-encrypted file per site rather than
one file holding all of them, so signing out of TikTok is a file delete and the
other six are not rewritten to do it. The existing store is migrated on first
run. A download is still only ever handed the cookies of the site it came from.
Sign-in now covers YouTube, Instagram, TikTok, Facebook, X, Reddit and
Vimeo, and an exported cookies.txt is filtered the same way.
A sender for Windows
Windows has no share sheet, so Riplox Send for Windows earns its place on
the keyboard: copy a link in any program, press Ctrl+Shift+S, and it
is on its way to the PC that downloads. Nothing opens; the answer arrives as a
notification. It is also the only sender that can reach that PC directly over
the local network — a web page cannot, because an HTTPS page is not allowed to
call a plain-HTTP address on the LAN.
Opening a pairing link on Windows now hands it to that app rather than to the
browser. The pairing code works once, so pairing the browser spent it and left
the app needing a second code. Its installer registers riploxsend:// under
HKCU — per-user, no administrator — and removes it on uninstall.
Source is in send-windows/.
Also in this release
- Find everything on a page — point it at a page and it lists every media
link on it, in the same screen playlists use. - Schedule — hold new downloads outside chosen hours. A download already
running is never cut off, and the queue says why anything is waiting. - Start with Windows — optional, per-user, and it starts into the tray
rather than onto your screen. - TikTok now says which half of the advice applies: whether there is a
saved TikTok sign-in at all, rather than telling everyone to try again later.
If TikTok is serving its verification page, signing in from Settings is the
answer — and if you have never signed in, it says so. - Defaults reviewed, each with the reason written beside it in the source.
Downloads now go into a folder per site by default. - Riplox stays a video downloader — the general file downloader that was
tried during development has been taken back out. - Fixed: Quit from the tray no longer claims Riplox is still running.
Files
| SHA-256 | ||
|---|---|---|
| Riplox | Riplox_Setup_v1.2.0.exe (71.96 MB) |
AF5F554DE02C03FE4F8E44DD0562FF58C65C3AC2E28DE9A9B08805256F73D3DF |
| 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 first, and
the only one most people need. The two senders are optional: install one on a
phone or on another PC you want to send links from. Neither downloads
anything itself; each hands a link to the PC running Riplox.
The Android APK is the same build the pairing page offers, byte for byte, and
it keeps itself up to date from there — it is published here so it can be
downloaded and checked without pairing anything first.
Riplox Send for Windows 1.0.1 replaces the 1.0.0 that was here for the first
half hour of this release. Being removed by the PC left the app still counting
itself as paired, so it showed a sending form that could only be refused and
kept the pairing screen hidden. It now opens the pairing screen on its own in
that state. Nothing else changed.
Installing
Both installers are per-user, so neither asks for administrator rights.
Windows may show "Windows protected your PC" the first time. These builds
are not code-signed — a certificate is a yearly cost this project does not
carry — so choose More info → Run anyway. If you would rather verify the
file first, compare its SHA-256 with the value above:
certutil -hashfile Riplox_Setup_v1.2.0.exe SHA256
Requires Windows 10 or 11 with the Microsoft Edge WebView2 Runtime, which is
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 for
permission to install it — that is normal for an app installed this way.
Android 8 or newer.