Initial release of the plugin. No upgrade required.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":{"torrent-scraper\/torrent-info":{"name":"torrent-scraper\/torrent-info","title":"Torrent Info"},"torrent-scraper\/tracker-stats":{"name":"torrent-scraper\/tracker-stats","title":"Tracker Stats"},"torrent-scraper\/torrent-files":{"name":"torrent-scraper\/torrent-files","title":"Torrent Files"},"torrent-scraper\/magnet-button":{"name":"torrent-scraper\/magnet-button","title":"Magnet Button"}},"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Torrent manager admin dashboard displaying uploaded torrent lists.","2":"wpForo topic creation editor with torrent upload \/ link options panel.","3":"Live seeder, leecher, and completed download stats badge on a blog post."}},"plugin_section":[],"plugin_tags":[568,5706,7677,12635,5352],"plugin_category":[44],"plugin_contributors":[277480],"plugin_business_model":[],"class_list":["post-330845","plugin","type-plugin","status-publish","hentry","plugin_tags-download","plugin_tags-forum","plugin_tags-scraper","plugin_tags-torrent","plugin_tags-tracker","plugin_category-discussion-and-community","plugin_contributors-rockydev8193","plugin_committers-rockydev8193"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/torrent-scraper-for-blogs-and-forums.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Torrent Scraper for Blogs and Forums<\/strong> lets you publish torrent files and magnet links directly inside WordPress blog posts and wpForo forum topics, complete with live seeder, leecher, and download count badges that auto-update every 5 minutes via WP-Cron.<\/p>\n\n When wpForo is active, the plugin adds a torrent attachment panel to the topic editor. Users with the appropriate capability can upload a .torrent file or paste a magnet link directly from the forum topic form. The torrent metadata card is then automatically displayed inside the topic. This integration is optional<\/strong> -- the plugin works fully as a standalone blog plugin without wpForo installed.<\/p>\n\n After activating, visit Torrent Scraper -- Settings -- System Check<\/strong> to verify your server meets all requirements.<\/p>\n\n This plugin contacts external BitTorrent tracker servers to retrieve live seeder, leecher, and completed-download counts for torrents stored in your database. This section documents every external connection this plugin makes: what is sent, what is received, when it happens, how it happens, why it is needed, and which third-party service is involved.<\/p>\n\n Important:<\/strong> No personal user data is ever transmitted to any external server. No usernames, email addresses, passwords, WordPress session tokens, visitor IP addresses, or any personally identifiable information is sent to tracker servers under any circumstances.<\/p>\n\n\n\n What this service is:<\/strong>\nBitTorrent tracker servers are public network services that coordinate peer-to-peer file sharing. When a client queries a tracker using the \"scrape\" protocol, the tracker reports how many peers are currently seeding (uploading) a file, how many are leeching (downloading) it, and how many times it has been fully downloaded. This plugin uses that information to display live statistics on your WordPress site. The plugin does NOT seed or download any file content. It does NOT join any peer-to-peer swarm.<\/p>\n\n Which tracker servers are contacted:<\/strong>\nThe plugin contacts ONLY the tracker announce URLs that are embedded inside each Example of a tracker URL that may appear inside an uploaded torrent file:\n udp:\/\/tracker.example.com\/announce<\/p>\n\n When does this happen:<\/strong>\n1. Immediately after upload<\/strong> -- When a site administrator uploads a How it works -- HTTP Trackers (BitTorrent BEP 48 Scrape Convention):<\/strong><\/p>\n\n What is sent (outbound):<\/em>\nAn HTTP GET request is sent to the tracker's scrape URL. The request contains:\n- The torrent's info hash<\/strong>: a 20-byte SHA-1 hash of the torrent file's \"info\" dictionary, URL-percent-encoded. This is a mathematical identifier for the torrent and does not contain any personal data or file content.\n- Standard HTTP request headers automatically included by WordPress's built-in Nothing else is sent. No user data. No file content. No authentication credentials.<\/p>\n\n What is received (inbound):<\/em>\nThe tracker responds with a bencoded binary dictionary. The plugin decodes this response and extracts:\n- These three numbers are public, aggregate statistics. They do not identify any individual user. The plugin stores these three values in its own database table ( No other data from the HTTP response body is stored or used. HTTP response headers (such as cache-control or content-type) are used only to process the response and are not stored.<\/p>\n\n How it works -- UDP Trackers (BitTorrent BEP 15 UDP Tracker Protocol):<\/strong><\/p>\n\n What is sent (outbound):<\/em>\nUDP tracker communication follows a two-step handshake:<\/p>\n\n Step 1 -- Connect Request (16 bytes):\n- Step 2 -- Scrape Request (sent after receiving a connection token):\n- Side effect of network connection:<\/strong> Because UDP is connectionless, the tracker server will see your web server's outbound IP address as the network source of the UDP packets. This is an unavoidable, standard side-effect of any internet connection and is equivalent to visiting any website. The plugin does not attempt to mask or spoof this.<\/p>\n\n Nothing else is sent. No user data. No file content.<\/p>\n\n What is received (inbound):<\/em>\nThe tracker responds with a UDP scrape response packet. The plugin decodes this response and extracts:\n- These three integers are stored in the plugin's database ( Why this is needed:<\/strong>\nWithout querying the tracker, the plugin has no way to display live seeder and leecher counts. These statistics are the core value of the plugin -- they allow site visitors to see at a glance whether a torrent is well-seeded before downloading it. The scrape protocol is the only standardized, publicly available mechanism for retrieving this data from BitTorrent trackers.<\/p>\n\n Third-party tracker responsibility:<\/strong>\nThe plugin has no control over which trackers are embedded inside No. The plugin uses only the standard BitTorrent tracker scrape protocol, which is a free, open protocol. No API keys, accounts, or paid subscriptions are required.<\/p><\/dd>\n Yes. The wpForo integration is fully optional. All core features (torrent upload, shortcodes, Gutenberg blocks, REST API, admin dashboard) work on any standard WordPress site without wpForo installed.<\/p><\/dd>\n The plugin catches connection errors gracefully and skips the failed tracker. Previously stored counts are kept until the tracker becomes available again. No errors are shown to site visitors.<\/p><\/dd>\n Yes. When a .torrent file is uploaded, it is saved to The The plugin creates its own tables (prefixed with Yes. Go to Torrent Scraper -- Settings -- Integrations and disable \"Automatic Scraper (Cron)\". The plugin will stop its scheduled background scraping. Note that without periodic scraping, the seeder\/leecher counts displayed on your site will become stale.<\/p><\/dd>\n\n<\/dl>\n\n\nHow It Works<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
\/wp-json\/tsbf\/v1\/<\/code> with pagination, filtering, and per-IP rate limiting.<\/li>\nwpForo Integration<\/h4>\n\n
Who Is This For?<\/h4>\n\n
\n
Requirements<\/h4>\n\n
\n
sockets<\/code> (UDP tracker scraping), curl<\/code> (HTTP tracker scraping), mbstring<\/code> (Bencode decoding), fileinfo<\/code> (file upload security)<\/li>\nExternal Services<\/h3>\n\n
Service 1: BitTorrent Tracker Servers (Core Feature \u2014 Tracker Scraping)<\/h4>\n\n
.torrent<\/code> file that a site administrator uploads through the admin dashboard or wpForo topic form. These tracker URLs are chosen by whoever originally created the torrent file -- the plugin reads them from the file and uses them as-is. The plugin does NOT maintain its own hardcoded list of trackers.<\/p>\n\n.torrent<\/code> file or submits a magnet link, the plugin immediately sends one scrape request per tracker URL embedded in the torrent to populate the initial seeder\/leecher statistics.\n2. Every 5 minutes via WP-Cron<\/strong> -- The plugin schedules a recurring background job (WordPress WP-Cron hook: tsbf_run_scheduler<\/code>) that runs every 5 minutes and sends scrape requests for all active torrents in the database. This keeps statistics up to date automatically. This can be disabled via Settings -- Integrations -- Automatic Scraper<\/strong>.\n3. Manual refresh<\/strong> -- When a site administrator clicks the \"Reload\" button next to a torrent in the admin dashboard, the plugin immediately sends a fresh scrape request for that torrent.<\/p>\n\nwp_remote_get()<\/code> function, including a User-Agent string identifying the WordPress HTTP client.<\/p>\n\ncomplete<\/code><\/strong>: An integer representing the current number of seeders (peers who have the complete file and are sharing it).\n- incomplete<\/code><\/strong>: An integer representing the current number of leechers (peers who are actively downloading the file).\n- downloaded<\/code><\/strong>: An integer representing the total number of times the complete file has been successfully downloaded from the swarm since the tracker began counting.<\/p>\n\n{wordpress_prefix}tsbf_torrent_statistics<\/code>) alongside a timestamp.<\/p>\n\nconnection_id<\/code>: fixed protocol magic constant 0x41727101980<\/code> (publicly defined by the BitTorrent protocol specification)\n- action<\/code>: integer 0<\/code> (meaning \"connect\")\n- transaction_id<\/code>: a randomly generated 32-bit integer used to match this request to its response; discarded after use; never stored<\/p>\n\nconnection_id<\/code>: a temporary token issued by the tracker (valid for approximately 2 minutes; used only to send this request; never stored after the request completes)\n- action<\/code>: integer 2<\/code> (meaning \"scrape\")\n- transaction_id<\/code>: a new randomly generated 32-bit integer; discarded after use\n- info_hash<\/code>: the 20-byte raw binary SHA-1 info hash of the torrent<\/p>\n\nseeders<\/code><\/strong>: Current number of peers with the complete file.\n- completed<\/code><\/strong>: Total number of successful complete downloads recorded by this tracker.\n- leechers<\/code><\/strong>: Current number of peers still downloading the file.<\/p>\n\n{wordpress_prefix}tsbf_torrent_statistics<\/code>) alongside a timestamp. No other data from the UDP response is stored or used. The connection token and transaction ID are discarded immediately after the response is processed.<\/p>\n\n.torrent<\/code> files uploaded by site administrators. Each tracker is a third-party service with its own policies. Site administrators are responsible for reviewing the tracker URLs embedded in the torrent files they upload. The plugin only sends the torrent's info hash to each tracker -- it does not send any personal data.<\/p>\n\n\n\nSummary Table<\/h4>\n\n\n\n\n Connection\n Destination\n Trigger\n Data Sent\n Data Received\n Stored\n\n\n\n\n HTTP Tracker Scrape\n Tracker URLs inside .torrent files\n Upload, WP-Cron every 5 min, manual reload\n Info hash (hex string)\n Seeders, leechers, completed (3 integers)\n Yes \u2014 in plugin database\n\n\n UDP Tracker Scrape\n Tracker URLs inside .torrent files\n Upload, WP-Cron every 5 min, manual reload\n Info hash (20 raw bytes)\n Seeders, completed, leechers (3 integers)\n Yes \u2014 in plugin database\n\n\n\n\n\n\n
Important Notes for Site Owners<\/h4>\n\n
\n
.torrent<\/code> files that administrators choose to upload. Reviewing those tracker URLs before uploading is the site owner's responsibility.<\/li>\n<\/ul>\n\nShortcodes<\/h3>\n\n
\n
[tsbf_torrent id=\"123\"]<\/code> -- Torrent info card (name, size, file count, stats)<\/li>\n[tsbf_torrent_stats id=\"123\"]<\/code> -- Seeder \/ leecher \/ completed badges only<\/li>\n[tsbf_torrent_files id=\"123\"]<\/code> -- File count and total size table<\/li>\n[tsbf_magnet id=\"123\"]<\/code> -- Magnet link button<\/li>\n[tsbf_torrent_list category=\"movies\" limit=\"20\" orderby=\"seeders\"]<\/code> -- Sortable torrent table<\/li>\n[tsbf_global_stats]<\/code> -- Network-wide aggregate stats widget<\/li>\n[tsbf_user_torrents user_id=\"0\" limit=\"20\"]<\/code> -- Torrents uploaded by a user<\/li>\n[tsbf_torrent_browse]<\/code> -- Full browsable torrent listing page<\/li>\n<\/ul>\n\n\n\n
torrent-scraper-for-blogs-and-forums<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\n
Does this plugin require any external API keys or paid services?<\/h3><\/dt>\n
Does this plugin work without wpForo?<\/h3><\/dt>\n
What happens if a tracker is offline or unreachable?<\/h3><\/dt>\n
Does the plugin store torrent files on my server?<\/h3><\/dt>\n
wp-content\/uploads\/torrent-scraper\/<\/code>. Magnet links do not create any files -- only metadata is stored in the database.<\/p><\/dd>\nWhat PHP extensions are required?<\/h3><\/dt>\n
sockets<\/code> extension is required for UDP tracker scraping. The curl<\/code> extension is required for HTTP tracker scraping. The mbstring<\/code> extension is required for Bencode decoding of torrent metadata. The fileinfo<\/code> extension is required for secure MIME type validation during file uploads. All can be verified via the built-in System Check page.<\/p><\/dd>\nWhat data does the plugin store in the WordPress database?<\/h3><\/dt>\n
{wordpress_prefix}tsbf_<\/code>) to store: torrent metadata (name, size, info hash, file list), tracker URLs, scrape statistics (seeders, leechers, completed counts with timestamps), categories, log entries, and post\/topic associations. No visitor personal data is stored in these tables.<\/p><\/dd>\nCan I disable tracker scraping entirely?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n