Documentation
Browsing simulation in RMS
Configure public-page browsing, video playback, traffic budgets, and request logs in RMS builds that include this feature, and check their runtime requirements.
Version availability: This page applies to newer RMS builds that include “Browsing simulation.” If your older version has no such card, upgrade to a release whose notes explicitly list this feature.
RMS uses a real browser with mobile viewport, touch, and browser settings to visit public pages. Browsing originates from the machine running RMS, rather than from each miner. It uses mobile websites, not native phone apps. Sites may require authentication or verification, and page or video availability is not guaranteed.
Open the Card and Apply Settings
Find Browsing simulation (上网行为模拟) on the right side of the RMS home page. The desktop application and web management interface use the same entry point.
- The feature is initially disabled. The card switch starts or stops browsing with the saved settings.
- Choose Configure, edit the draft, then Save and Apply to make and persist changes.
- Cancel or closing the dialog discards unsaved edits. Changing tabs keeps the draft.
- Turning the feature off requests a stop without saving other pending edits. Saved settings survive RMS restarts.
The dialog has five tabs:
| Tab | Purpose |
|---|---|
| Runtime Status | Current action, browser readiness, content-page count, video switches, and playback state. |
| Websites | Select presets and add or edit custom sites. |
| Browsing Behavior | Intervals, round duration, navigation limits, reading time, and video timing. |
| Traffic and Protection | Upload/download limits, daily budget, and CPU pause threshold. |
| Access Logs | Recent page and resource requests, including errors, redirects, and cancellations. |
Choose Websites
The 11 presets are Baidu, IT Home, SSPAI, Guokr, Hupu, Autohome, SMZDM, Douban, Baidu Tieba, Douyin, and bilibili. Select the sites you want to include.
You can add up to 16 custom sites, each with a name and URL. Names are required, allow at most 64 characters, and cannot contain control characters. URLs must use public HTTPS on standard port 443, with no credentials, local/private destination, or duplicate URL. A name is a display label; it does not change the destination.
Save and Apply stores names, URLs, and other settings in local.conf. They remain after a restart. Older URL-only entries are read automatically with a hostname-based name; saving writes named URL objects.
New configurations select all 11 presets and enable video viewing and switching, while the overall feature remains disabled. Existing saved site selections and video settings retain their values.
What Happens in a Round
Each round randomly chooses one selected preset or custom URL. After loading the entry page, RMS looks for visible public content links within the site’s allowed domain scope, selects unread content, and scrolls or pauses for a random time. A page is counted only after navigation is confirmed. By default, at most three further content or video navigations can complete after the entry page. With no suitable link or no remaining navigation allowance, it stays on the current page until the round ends.
With video enabled, RMS requests muted playback of visible videos and checks that playback time actually advances. After a random viewing interval it can select another public item; Douyin feeds may also receive a bounded upward swipe. Navigation or swiping alone does not prove playback. A switch is counted only after the next video also advances. Articles without video continue as reading visits.
RMS skips login and verification gates. It does not log in automatically, bypass CAPTCHAs, or perform likes, comments, coin donations, or follows. Buffering, unavailable media, and missing links may prevent the requested navigation or viewing activity.
Defaults and Resource Protection
| Setting | Default for a new configuration |
|---|---|
| Download / upload limit | 32 KiB/s / 4 KiB/s |
| Daily combined upload/download budget | 200 MiB |
| Interval between rounds | Random 30–120 seconds |
| Total round duration | 45 seconds; configurable up to 300 seconds |
| Further content/video navigations | At most 3 after the entry page |
| Reading time per content page | Random 4–10 seconds |
| Viewing time per video | Random 6–18 seconds |
| CPU pause threshold | 80% |
The round deadline takes precedence over reading and viewing times. The default download rate may leave videos buffering. Adjust it to available spare bandwidth if needed; RMS does not increase the configured rate automatically.
This feature shares its rate limits and budget across its page traffic, rather than multiplying them for each request. They are not a hard limit on the whole network interface: short bursts remain possible, and connection metadata such as DNS is outside the budget. The daily budget resets at midnight Beijing time and is not cleared by restarting RMS.
Sustained CPU threshold readings pause browsing. When current performance diagnostics are available, scheduling and queue-delay warnings can also trigger a pause, followed by a retry after recovery. These measures reduce resource contention; they do not guarantee zero impact on mining. Browsing still uses CPU, memory, disk, and bandwidth, so monitor the site after enabling it.
Request Log Retention
Logs contain basic metadata for documents, scripts, stylesheets, images, video, and Fetch/XHR requests: URL, method, HTTP status, duration, size, and errors. Unknown values appear as “—”, and redirect hops have separate entries.
- Only the latest 200 entries are kept in memory across browsing rounds; older entries are evicted.
- Closing the dialog or disabling browsing retains them. Restarting RMS clears them. They are not saved in
local.conf. - Headers, cookies, request bodies, and response bodies are not stored. URLs over 8192 bytes are truncated and marked.
- The list is fetched only while the log tab is open and refreshes every three seconds. Response sizes use a different accounting basis from the combined traffic budget.
One page produces many resource requests. Changing pages, stopping, or reaching the round deadline can cancel unfinished requests; these cancellations differ from server HTTP errors and connection failures.
First Use and System Requirements
Complete new release packages distribute the browser runtime inside the single RMS file, so a separate Chrome installation is unnecessary. First use verifies and extracts it into rms-browser-runtime beside RMS. Disabling the feature does not extract or start the large browser runtime; an existing extracted cache remains available for reuse.
Keep the RMS directory writable and at least 3 GiB of additional disk space free, excluding the RMS file itself. Upgrades that retain older caches need more space, and first preparation can take time. Single-file distribution still creates runtime files and browser processes.
Targets are Windows x86_64, with GUI and console builds, and Linux x86_64, aarch64, and armv7. The corresponding browser’s operating-system, kernel, and sandbox requirements still apply. An architecture match alone does not establish support for every old Windows release, minimal Linux image, or OpenWrt installation. On Linux, running as root or lacking sandbox support may prevent startup; RMS does not automatically disable the sandbox.
The Windows GUI retains its existing system WebView2 requirement. The bundled browsing engine does not replace that GUI dependency. Verify page loading, media formats, and site access on the actual target machine; successful compilation or packaging does not establish video playback support.