Usage Guide: Social Media Platforms

Relevant source files

The following files were used as context for generating this wiki page:

• README.md
• README_zh.md
• renderer.js
• index.html
• main.js
• package.json
• setup.js

GeekEZ Browser is a professional anti-detect browser designed for e-commerce operators and social media managers who need to handle multiple accounts safely. Built on Electron and Puppeteer, it focuses on creating strictly isolated browser environments to prevent account association and detection by platforms like Amazon, TikTok, and Facebook. The core strategy is "Native Consistency," which avoids easily detectable JavaScript hooks in favor of native Chromium arguments and noise injection to bypass advanced detectors.

This guide outlines the browser's compatibility with various platforms, its key anti-detection features, and the best practices for managing social media and e-commerce accounts. The browser's architecture ensures that each profile has a unique fingerprint, network environment, and local storage, making it appear as a distinct, legitimate user device to web services.

Sources: README.md:13-19, README_zh.md:15-19

Platform Compatibility & Safety

GeekEZ Browser has been tested for compatibility with several major platforms. The safety rating depends on the platform's specific detection mechanisms and the user's adherence to best practices, particularly the use of high-quality IP addresses.

The following diagram illustrates the core technologies used to achieve platform compatibility.

This diagram shows that the Electron application uses Puppeteer to control a real Chrome instance, with Xray-core managing network traffic. Each profile is launched as a separate, isolated instance with a unique fingerprint to interact with social media platforms.

Sources: README.md:14, package.json:48-56, main.js:6-7

Platform Safety Ratings

The table below, derived from the project's documentation and in-app help content, summarizes the safety level and recommendations for specific platforms.

Platform	Safety Rating	Recommendations
TikTok	✅ Safe	Canvas noise is effective. Requires a clean, high-quality residential IP.
Facebook	✅ Safe	WebDriver/Automation flags are stripped. Avoid high-frequency automation.
Shopee	✅ Safe	Provides a stable fingerprint for seller center operations. Use one fixed environment per account.
Amazon (Buyer)	✅ Safe	Sufficient isolation for buyer and reviewer accounts.
Amazon (Seller)	✅ Safe	TLS fingerprint is safe. Usable for main accounts with a high-quality residential IP and a fixed environment.
Rakuten	✅ Safe	Requires a local IP address.
Mercado Libre	✅ Safe	Similar requirements to Amazon.
Cloudflare	✅ Pass	Bypasses Turnstile/hCaptcha via native injection strategy without JS hooks.

Sources: README.md:104-113, renderer.js:316-322

Core Anti-Detection Mechanisms

GeekEZ Browser employs a multi-layered approach to prevent detection. These mechanisms are applied automatically when a new profile is created and launched.

1. Advanced Fingerprint Isolation

Each profile is generated with a unique browser fingerprint. This is achieved by randomizing hardware and software attributes.

This flowchart shows the process of generating a new fingerprint when a user creates a profile.

Sources: main.js:250-256, renderer.js:636-646

Key fingerprinting features include:

• Hardware Randomization: CPU cores (4/8/12/16) and device memory (4/8/16 GB) are randomized for each profile.
• Media Noise: Non-intrusive noise is added to Canvas, WebGL, and AudioContext to create unique hardware hashes. This is controlled by a noiseSeed value in the profile's fingerprint object.
• Native Injection: Instead of easily detectable JavaScript hooks, the browser uses Chromium's native command-line arguments and Puppeteer to inject fingerprint modifications. This is visible in the launchArgs array.
• TLS Fingerprint Safety: By using a real, unmodified Chrome binary (downloaded by setup.js), the TLS (JA3) fingerprint matches that of a standard Chrome browser, avoiding a common detection vector.
• Timezone & Geolocation: The browser timezone can be set per profile, ideally to match the proxy's IP location. The default is America/Los_Angeles.
• WebRTC Protection: The disable_non_proxied_udp policy is enforced to prevent real IP leaks through WebRTC.

The following code snippet from main.js shows some of the arguments passed to Chrome to enforce isolation and fingerprinting.

// Sources: [main.js:452-472](https://github.com/CurtisLu1/GeekezBrowser/blob/HEAD/main.js#L452-L472)
const launchArgs = [
    `--proxy-server=socks5://127.0.0.1:${localPort}`,
    `--user-data-dir=${userDataDir}`,
    `--window-size=${profile.fingerprint?.window?.width || 1280},${profile.fingerprint?.window?.height || 800}`,
    '--restore-last-session',
    '--no-sandbox',
    '--disable-setuid-sandbox',
    '--disable-blink-features=AutomationControlled',
    '--disable-features=IsolateOrigins,site-per-process',
    '--force-webrtc-ip-handling-policy=disable_non_proxied_udp',
    `--lang=${profile.fingerprint.languages[0]}`,
    `--disable-extensions-except=${extPaths}`,
    `--load-extension=${extPaths}`,
    // ... Performance optimizations
];

Sources: README.md:24-40, main.js:100-105, 427-428, 461, setup.js:154-164

2. Network Isolation with Xray-core

All network traffic from a profile is routed through a dedicated proxy configuration managed by an xray process.

This diagram illustrates the sequence of events when a user launches a profile, highlighting the creation of a dedicated Xray proxy process for the new browser instance.

Sources: main.js:380-485, renderer.js:652-656

3. Safe Workflow & Management

The application includes features to help manage accounts without raising flags.

• Tag System: Profiles can be organized with custom color-coded tags (e.g., "TikTok", "USA", "Main Account"). This is managed in the UI and stored with the profile data.
• Safe Identification: To avoid detection methods that scan document.title, the profile name is displayed in the Bookmarks Bar instead. This is implemented by writing a Bookmarks file into the profile directory before launch.

The bookmark structure is created in main.js:

// Sources: [main.js:433-434](https://github.com/CurtisLu1/GeekezBrowser/blob/HEAD/main.js#L433-L434)
{
  "checksum": "0",
  "roots": {
    "bookmark_bar": {
      "children": [
        {
          "date_added": "13245678900000000",
          "guid": "...",
          "id": "1",
          "name": "🔍 Profile-Name",
          "type": "url",
          "url": "chrome://newtab/"
        }
      ],
      "name": "Bookmarks Bar",
      "type": "folder"
    },
    // ... other bookmark roots
  },
  "version": 1
}

Sources: README.md:58-62, index.html:1012-1014, renderer.js:641-643, main.js:430-435

Best Practices for Social Media

The in-app help manual provides clear best practices for using the browser effectively on sensitive platforms.

1. Use High-Quality IPs: Always use high-quality residential or mobile IP addresses. Avoid datacenter proxies for platforms like TikTok and Amazon.
2. One Account, One Environment: Dedicate a single browser profile to one social media or e-commerce account. Do not log into multiple accounts from the same profile.
3. Avoid Frequent Switching: Maintain consistency. Do not switch proxies or fundamental fingerprint settings (like hardware) for an established account.
4. Simulate Real User Behavior: Avoid robotic, high-frequency automation. Mimic the patterns of a real user.

Sources: renderer.js:296-299, README.md:104-113

Summary

GeekEZ Browser provides a robust solution for managing multiple social media and e-commerce accounts by focusing on deep, native-level isolation. Its compatibility with platforms like TikTok, Facebook, and Amazon hinges on its ability to create unique, legitimate-looking browser fingerprints and its strict network isolation via Xray-core. By following the recommended best practices, users can significantly reduce the risk of account association and suspension. The combination of hardware randomization, media noise, a safe TLS fingerprint, and secure workflow features makes it a powerful tool for multi-account management.