Details

Written by: Kim Jacobsen

Category: Blog

Published: 11 August 2026

Hits: 359

MediaTube Hub 2.11.0

Major Evolution Release Notes — From 2.8.7 to 2.11.0

MediaTube Hub has undergone a substantial architectural evolution since version 2.8.7. What began as a Joomla-based media management and distribution component has progressively developed into a network-capable media infrastructure integrating remote publishing, distributed analytics, secure playback, commercial access control, social interaction, and external content distribution.

Version 2.11.0 represents the consolidation of this development cycle.

Rather than treating media merely as files displayed by a CMS, the current architecture treats each media item as a persistent network object capable of accumulating traffic, engagement, commercial state, distribution metadata, and audience interaction across multiple connected websites.

---

2.8.7 — MediaTube Hub Foundation

Version 2.8.7 established the mature MediaTube Hub architecture upon which the subsequent releases were constructed.

The component provided centralized administration of MediaTube content while extending its role beyond conventional local media presentation. Media items could participate in the MediaTube API and remote-distribution environment, establishing the conceptual distinction between the authoritative Hub and external Remote consumers.

This architecture became the foundation for later network synchronization, traffic attribution, secure playback, commerce, engagement, and sharing functionality.

Principal capabilities

• Joomla-native MediaTube component architecture

• Central media administration

• MP4 media management

• Media metadata and categorization

• Media detail pages

• Hub-oriented API infrastructure

• Remote MediaTube distribution

• Traffic and referral analysis

• API-controlled external access

• Foundation for distributed MediaTube installations

The essential architectural principle introduced during this generation was straightforward:

The Hub owns the media state; remote installations consume and interact with that state.

That principle remains central to MediaTube 2.11.0.

---

2.8.8–2.8.12 — API, Routing and Remote Distribution Maturity

The 2.8.x development cycle concentrated on making MediaTube reliable as a distributed system rather than merely a local Joomla component.

A considerable amount of engineering was directed toward Joomla routing, API state, remote communication, click attribution, client identification and canonical media URLs.

MediaTube was progressively hardened against circumstances in which Joomla SEF configuration, menu Itemid context or remote installations could otherwise generate ambiguous or unusable URLs.

The API and Remote architecture were correspondingly refined so that distributed MediaTube clients could operate against an authoritative Hub without independently reconstructing the Hub's internal routing logic.

Major improvements

• Improved MediaTube API reliability

• API status and configuration corrections

• Remote client communication improvements

• Signed remote requests

• Client identification

• API key management

• Remote media feeds

• Traffic attribution

• Remote click tracking

• Referral-domain statistics

• Improved Joomla Itemid handling

• Corrected media-detail routing

• Improved compatibility with SEF-disabled development environments

• Elimination of inappropriate hardcoded SEF assumptions

• Canonical MediaTube detail URL generation

• More reliable Hub-to-Remote navigation

This development phase was particularly important because distributed systems cannot safely assume that URL structure is identical across installations.

MediaTube therefore moved toward semantic routing: links describe the requested component, view, layout and media identity, while Joomla determines the appropriate presentation context.

---

2.9.0 — Commercial Media Architecture

MediaTube 2.9 introduced an entirely new architectural dimension: commercial media access.

Media could now be treated as a controlled digital asset rather than necessarily being available as unrestricted public content.

The component was prepared for payment-gateway integration and rental-based access, including integration architecture for OnPay.

A media item could therefore possess both content state and commercial state.

Instead of the simplistic relationship:

Visitor → File

MediaTube could now implement:

Visitor → Media Item → Entitlement → Playback Policy → Stream

This distinction became fundamental to the subsequent Secure Stream architecture.

Commercial capabilities

• Per-media rental configuration

• Rental pricing

• Rental duration

• Currency configuration

• Payment workflow architecture

• OnPay integration foundation

• Purchase/rental state

• Access entitlement

• Payment approval handling

• Preview-before-purchase model

• Commercial access validation

The component consequently evolved from media presentation into a rudimentary digital media transaction platform.

---

2.9.1–2.9.4 — Secure Stream & Preview Playback

The Secure Stream generation fundamentally changed how protected MP4 media is delivered.

Previously, an MP4 file accessible through a predictable public path could theoretically bypass application-level rental logic. Secure Stream eliminates that architectural weakness.

Protected originals can be relocated outside the public web root and delivered through MediaTube's controlled streaming endpoint.

Playback therefore becomes an authorization operation rather than merely a file request.

Secure Stream architecture

MediaTube now evaluates:

1. Media identity

2. Publication state

3. Storage state

4. Rental configuration

5. Joomla user identity

6. Active entitlement

7. Preview policy

8. Requested playback resource

Only after these conditions have been evaluated does the component determine what the requester is permitted to receive.

Secure Preview Playback

For users without active rental entitlement, MediaTube can generate and deliver a restricted preview instead of exposing the complete original.

The preview pipeline was hardened with:

• Configurable preview duration

• FFmpeg-based preview generation

• H.264 video transcoding

• AAC audio

• MP4 faststart

• Browser-compatible preview generation

• Range request handling

• HTTP 206 Partial Content support

• HEAD request support

• Output-buffer protection

• Private original storage

• Fail-closed playback behavior

If preview generation fails, MediaTube does not compensate by exposing the complete original.

This is an important security property:

Failure of the preview subsystem must reduce access, never increase it.

---

2.10.0 — Engagement Network Edition

Version 2.10 transformed MediaTube from a distributed media system into a distributed audience-interaction system.

Media items gained persistent social state through:

• Likes

• Dislikes

• Favorites

• Reports

• Downloads

• Shared views

The important innovation is not merely the presence of buttons. The significant change is that engagement is network-authoritative.

The MediaTube Hub acts as the canonical source of engagement statistics.

A Like generated through a remote MediaTube installation is therefore not an isolated local counter. It is transmitted to the Hub and becomes part of the same authoritative state observed throughout the MediaTube network.

Conceptually:

Hub + Remote A + Remote B + Remote N → One Media Identity → One Shared Statistical State

Shared engagement

MediaTube 2.10 introduced synchronized:

• View counts

• Like counts

• Dislike counts

• Favorite counts

• Download counts

• Report events

Remote installations obtain authoritative statistics from the Hub rather than maintaining incompatible independent counters.

This produces a considerably more coherent distributed-media model.

If a media item has 2,500 views, 175 likes and 12 dislikes, those values describe the media object's network activity—not merely its activity on one rendering endpoint.

Like and Dislike semantics

Likes and dislikes are mutually exclusive for the same actor.

Changing from Like to Dislike therefore changes the actor's reaction rather than incorrectly recording two contradictory reactions.

Favorites

Media items can be added to or removed from an actor's favorites while the aggregate favorite count remains centralized.

Reporting system

Media can be reported using structured reasons including:

• Copyright

• Illegal content

• Misleading content

• Spam

• Technical or quality problems

• Other concerns

Reports retain contextual information for subsequent moderation.

Download accounting

Downloads are registered as engagement events while protected commercial media continues to respect entitlement requirements.

Analytics therefore do not supersede security.

---

Shared Views Across the MediaTube Network

View synchronization represents one of the most consequential changes introduced after 2.8.7.

Remote traffic now contributes to the same authoritative media statistics as traffic occurring directly on the Hub.

Remote media clicks can pass through MediaTube's Hub attribution mechanism, allowing the system to register both traffic origin and media consumption.

This creates a useful distinction between:

where the media was presented

and

which canonical media object was consumed.

The result is network-level analytics rather than fragmented site-level counters.

This architecture also improves the semantic value of functions such as Most Viewed, because popularity increasingly represents activity throughout the distribution network.

---

MediaTube Remote Integration

The Remote architecture has matured in parallel with the Hub.

Remote installations can consume Hub-managed media while participating in the same traffic and engagement ecosystem.

The Remote layer supports centralized statistics for views and engagement while signed action URLs permit remote interaction without exposing sensitive API credentials directly in client-side code.

This produces an architecture resembling:

MediaTube Hub

→ authoritative media
→ authoritative statistics
→ access policy
→ commerce
→ API
→ analytics

MediaTube Remote

→ presentation
→ discovery
→ interaction
→ traffic generation
→ engagement transmission

The distinction permits multiple websites to participate in a MediaTube network without requiring each installation to become an independent source of truth.

---

2.11.0 — Share & Embed Edition

MediaTube 2.11 extends distribution beyond the formal MediaTube Remote network.

Every media item can now become independently shareable across external communication and social platforms.

Integrated sharing destinations

Per-media sharing now includes:

• Facebook

• Reddit

• SMS

• Email

• WhatsApp

• LinkedIn

• Pinterest

• Copy Link

• Native Device Share

Share targets use the current MediaTube/Joomla-generated media URL rather than assuming a hardcoded SEF structure.

This preserves compatibility across differing Joomla routing configurations.

---

MP4 Embed Architecture

Uploaded MP4 media now provides an embeddable player.

MediaTube automatically exposes a copyable iframe structure referencing a dedicated minimal embed layout.

The embed layer allows a MediaTube video to be presented on an external website without requiring the complete MediaTube interface to accompany it.

This substantially expands MediaTube's distribution model:

Hub → MediaTube Remote → External Websites → Social Networks → Messaging Platforms

A single media object can therefore participate in several independent presentation environments while retaining its canonical identity at the MediaTube Hub.

---

Secure Embedding of Commercial Media

Embedding does not circumvent Secure Stream.

This is deliberately enforced at the architectural level.

For protected or rental-enabled MP4 content, the iframe does not expose the physical original file. Instead, playback continues through the MediaTube Secure Stream endpoint.

Consequently, embedding a commercial media item does not transform it into a publicly downloadable resource.

An unauthorized viewer receives only the configured preview, while an entitled user may receive the permitted full stream according to the MediaTube access policy.

Thus:

Distribution is decentralized; authorization remains centralized.

This distinction is essential for combining broad media distribution with controlled commercial access.

---

Architectural Evolution: 2.8.7 → 2.11.0

The progression from MediaTube 2.8.7 to 2.11.0 can be summarized as an expansion across five architectural dimensions:

Media Management → Distribution → Security → Commerce → Network Interaction

Version 2.8.7 established MediaTube as a capable Hub.

The later 2.8.x releases stabilized API communication, routing and remote distribution.

Version 2.9 introduced commercial access and transformed playback into an entitlement-sensitive operation.

The Secure Stream releases separated protected originals from publicly accessible resources and introduced controlled preview delivery.

Version 2.10 established shared network engagement.

Version 2.11 extends the distribution perimeter through social sharing and secure MP4 embedding.

The resulting system is no longer adequately described as simply a Joomla video component.

MediaTube Hub has evolved toward a distributed media orchestration platform in which media identity, playback authorization, commerce, analytics, audience interaction and distribution are coordinated around a centralized authoritative state.

---

Current MediaTube 2.11.0 Capability Profile

MediaTube now combines:

• Joomla-native media management

• MP4 video

• MP3 audio

• Video artwork

• RTMP sources

• YouTube integration

• Spotify integration

• Media categorization

• Dedicated media pages

• API distribution

• Remote MediaTube clients

• Signed API operations

• Traffic attribution

• Referral analytics

• Shared network views

• Likes and dislikes

• Favorites

• Reporting

• Download accounting

• Rental access

• Payment integration architecture

• Secure private MP4 storage

• Controlled streaming

• Time-limited preview playback

• FFmpeg preview generation

• Social sharing

• Messaging sharing

• Native device sharing

• MP4 iframe embedding

• Secure commercial embedding

• Joomla-aware routing

The central architectural achievement of the 2.8.7–2.11.0 development cycle is therefore not the accumulation of individual features.

It is their integration around a common media identity.

A media item can now be uploaded once, represented throughout a distributed network, measured globally, interacted with remotely, commercially protected, previewed securely, embedded externally and shared across communication platforms—while the MediaTube Hub remains the authoritative coordinator of its state.

MediaTube Hub 2.11.0 — Share & Embed Edition

Release classification: Major Feature Evolution
Upgrade path: MediaTube Hub 2.8.7 → 2.11.0
Architecture: Joomla Media Hub / Distributed Media Network
Current generation: Share, Embed, Engagement & Secure Stream
Recommended release: 2.11.0

Download com_mediatube_2.11.0_share_embed.zip

Details

Written by: Kim Jacobsen

Category: Blog

Published: 11 August 2026

Hits: 394

MediaTube Hub 2.8.12 — Release Notes

Release: 2.8.12
Platform: Joomla 5
Component: MediaTube Hub
Release Type: Stability, Analytics & Routing Update

Overview

MediaTube Hub 2.8.12 represents a substantial refinement of the component's internal analytics and navigation architecture. This release concentrates on two infrastructural areas that are deceptively simple at the interface level but fundamental to a distributed media platform: persistent referral intelligence and deterministic media routing.

The objective of 2.8.12 is not merely to correct isolated symptoms, but to strengthen the relationship between MediaTube's API layer, Joomla's routing environment, click attribution, media discovery, and long-term statistical integrity.

Persistent Referral Analytics

The referral subsystem has been redesigned to provide durable tracking of external traffic sources.

Earlier implementations maintained referral-domain statistics through JSON data stored within Joomla's cache infrastructure. Although lightweight, cache storage is semantically inappropriate for historical analytics: cache data is inherently disposable and may disappear during administrative cache maintenance, automated cleanup, deployment operations, or filesystem changes.

MediaTube Hub now maintains referral-domain statistics using persistent database storage.

Referral information is recorded in the dedicated:

#__mediatube_referrals

table.

Media IDs and referring domains are associated with persistent counters, allowing MediaTube to construct a reliable historical representation of where media traffic originates.

This architectural change provides several advantages:

• Referral statistics survive Joomla cache cleaning.

• Historical domain attribution remains persistent between sessions.

• Statistics are no longer dependent upon filesystem cache permissions.

• Referral aggregation becomes structurally suitable for future analytical expansion.

• The Top Referral Domains interface can operate against durable data rather than ephemeral cache state.

Where possible, MediaTube also provides compatibility with referral information collected by earlier versions.

Top Referral Domains

The Top Referral Domains functionality has consequently been stabilized.

Administrators can use this information to identify external websites and domains responsible for directing visitors toward MediaTube content.

This transforms referral tracking from a simple counter into a practical traffic-intelligence mechanism. Over time, the accumulated dataset can reveal distribution patterns, successful external placements, syndication activity, audience acquisition sources, and potentially valuable publishing relationships.

In other words, MediaTube can increasingly answer not only:

"How often was this media accessed?"

but also:

"Where did that audience originate?"

That distinction is important for any media platform intended to operate beyond the boundaries of a single website.

Deterministic Media Routing

Version 2.8.12 also introduces important corrections to MediaTube's detail-page and API click-routing architecture.

MediaTube operates inside Joomla's menu-driven SEF routing environment. Joomla's Itemid system provides useful contextual routing, but incorrectly inherited menu contexts can cause component URLs to be interpreted as belonging to unrelated views or categories.

This could previously produce conditions such as:

404 — Category not found

when following media-related links.

MediaTube's routing logic has therefore been hardened to prevent unrelated Joomla menu contexts from determining the identity of a MediaTube resource.

Related Media Navigation

Related-media navigation has been corrected so that media references resolve through the appropriate MediaTube frontend route.

Instead of allowing an incomplete identifier such as:

/?id=52

to become the final destination, MediaTube now maintains the necessary media-detail context.

On the SatHack MediaTube deployment, this produces URLs following the established Joomla SEF structure:

/livecam-shows/xrated-18-videos/?layout=video&id=52

The result is predictable navigation between media resources without incorrectly invoking Joomla category resolution.

API Click Attribution and Redirects

The api.click endpoint has received corresponding improvements.

Signed MediaTube click URLs can perform two logically separate operations:

1. Register and attribute the click.

2. Redirect the visitor to the actual MediaTube resource.

Earlier routing behaviour could successfully perform the first operation while subsequently constructing an incomplete destination URL.

Version 2.8.12 corrects this separation of concerns.

A signed API request can therefore retain MediaTube's tracking functionality while forwarding the visitor to the proper public-facing media detail page.

This preserves analytics without sacrificing navigation integrity.

Public Detail URL Resolution

The fallback strategy for MediaTube's public detail URL has also been refined.

When no explicit Public Detail Base URL is supplied, the component no longer assumes that the Joomla domain root itself constitutes a valid media destination.

The routing layer instead resolves media through the MediaTube frontend context, maintaining the layout=video and media id parameters required to identify the requested resource.

Explicitly configured public detail URLs remain supported.

Architectural Significance

Although 2.8.12 is an incremental version number, the changes address an important architectural principle:

analytics must be persistent, while routing must be deterministic.

Traffic statistics lose analytical value if they disappear with cache maintenance. Likewise, a valid media identifier has little operational value if its interpretation depends upon an unrelated Joomla menu context.

MediaTube Hub 2.8.12 therefore separates these responsibilities more rigorously:

Media identity → MediaTube
Navigation context → MediaTube routing
Click attribution → API analytics
Referral history → persistent database storage
Presentation → Joomla SEF frontend

This separation reduces accidental coupling between Joomla's global navigation state and MediaTube's internal resource model.

Compatibility

MediaTube Hub 2.8.12 is designed as an in-place upgrade from the preceding 2.8.x releases.

Existing media records, component configuration, API infrastructure, media presentation, and previously introduced functionality remain intact.

The persistent referral architecture introduced during the 2.8.x development cycle is retained, together with the subsequent routing corrections.

Upgrade Recommendation

Upgrading to MediaTube Hub 2.8.12 is recommended for installations using:

• MediaTube referral analytics

• Top Referral Domains

• Related-media navigation

• Signed API click tracking

• Joomla SEF URLs

• MediaTube frontend detail pages

• External MediaTube distribution or remote modules

The release is particularly relevant for installations where MediaTube operates as a central media hub serving content through multiple entry points.

Final Perspective

MediaTube Hub 2.8.12 advances the component from merely displaying and distributing media toward understanding the infrastructure surrounding that distribution.

A mature media system should know three things with precision:

what was requested, where the request originated, and where the visitor must ultimately arrive.

Version 2.8.12 strengthens all three.

The result is a more persistent analytical model, a more deterministic routing architecture, and a considerably stronger foundation for future development of MediaTube Hub as a distributed Joomla media platform.

MediaTube Hub 2.8.12 — persistent intelligence, deterministic routing, reliable distribution.

Download com_mediatube_2.8.12.zip

Details

Written by: Kim Jacobsen

Category: Blog

Published: 09 August 2026

Hits: 473

Her er en artikel målrettet MediaTube Remote Connection Plugin, som beskriver pluginets rolle i arkitekturen, anvendelsen og release notes.

MediaTube Remote Connection Plugin 1.2.x

The Secure Communication Layer for Distributed Joomla Media Networks

As digital publishing evolves beyond individual websites, the underlying infrastructure responsible for communication becomes just as important as the content itself. While MediaTube Hub provides centralized media management and the MediaTube Remote Module presents remote content, the MediaTube Remote Connection Plugin serves as the trusted communication layer that securely connects both environments.

Rather than functioning as a visible frontend extension, the plugin operates silently in the background, establishing authenticated communication between Joomla installations while ensuring that every remote request remains secure, identifiable, and manageable.

It is the foundation that enables MediaTube to function as a distributed media platform rather than a traditional standalone component.

---

The Communication Layer

The Remote Connection Plugin acts as the gateway between a remote Joomla installation and the MediaTube Hub.

MediaTube Hub
        │
        │
 Secure JSON API
        │
        ▼
Remote Connection Plugin
        │
        ▼
MediaTube Remote Module
        │
        ▼
Website Visitors

Unlike the Remote Module, which focuses on presentation, the plugin manages communication, authentication, identity, and transport.

Separating these responsibilities creates a cleaner and more maintainable software architecture.

---

Why a Dedicated Plugin?

Maintaining communication inside the display module would tightly couple presentation with networking logic.

The Remote Connection Plugin separates these concerns.

Presentation remains inside the module.

Communication remains inside the plugin.

This modular architecture improves maintainability while allowing each component to evolve independently.

---

Authentication

Each remote Joomla installation authenticates using an individual API key.

The plugin securely attaches authentication headers to every request while automatically identifying the remote website through its configured Client ID.

This enables the MediaTube Hub to distinguish between connected websites without exposing database credentials or administrative access.

Supported authentication features include:

• Individual API keys

• Client identification

• Secure request headers

• API permission validation

• Domain restrictions

• Optional statistics access

Each website therefore operates as an independent client within the MediaTube ecosystem.

---

Secure Communication

The Remote Connection Plugin establishes secure communication through HTTP-based APIs.

Features include:

• JSON feed retrieval

• HTTP status validation

• Request timeout management

• Response validation

• Automatic header generation

• Error reporting

• Local caching integration

Only published media explicitly exposed by the Hub become available to remote installations.

No direct database communication is ever required.

---

Traffic Attribution

The plugin also enables distributed traffic measurement.

Whenever a visitor clicks a remote media item, the plugin communicates with the MediaTube Hub using signed requests that identify:

• Remote client

• Media item

• Request source

• Authentication context

The Hub records these events before redirecting the visitor to the canonical destination.

This creates measurable visibility into how distributed Joomla installations contribute to traffic generation.

---

Configuration

Installation requires minimal configuration.

Administrators simply provide:

• MediaTube Hub endpoint

• API key

• Client ID

Once configured, every request is automatically authenticated.

No manual programming is required after initial setup.

---

Performance

The Remote Connection Plugin has been optimized for lightweight operation.

Performance features include:

• Minimal memory consumption

• Fast HTTP communication

• Cached responses

• Reduced network overhead

• Efficient JSON parsing

• Graceful timeout handling

Because communication occurs only when required, the plugin introduces negligible impact on overall Joomla performance.

---

Security Model

Security remains one of the primary design objectives.

The plugin supports:

• API authentication

• Client validation

• Domain restrictions

• Request rate limiting

• Read-only communication

• No database exposure

• Secure transport headers

• Response verification

Even if a remote installation is compromised, direct access to the Hub database remains impossible.

---

Administration

Administrators benefit from centralized management.

The Hub can:

• Issue API keys

• Disable clients

• Rotate credentials

• Monitor traffic

• Track requests

• Restrict permissions

• Review usage statistics

The Remote Connection Plugin therefore becomes an integral part of a centrally administered Joomla media network.

---

Release Notes

Version 1.2.x

New Features

• Dedicated communication layer for MediaTube Hub.

• Secure JSON API transport.

• Individual API key authentication.

• Automatic Client ID support.

• Remote endpoint configuration.

• Signed request support.

• Secure HTTP header generation.

• Improved diagnostics.

• Joomla 5 compatibility.

Improvements

• Optimized request handling.

• Faster API communication.

• Reduced processing overhead.

• Improved response validation.

• Cleaner transport architecture.

• Enhanced compatibility with MediaTube Hub 2.8.x.

• Better administrator configuration workflow.

Security

• Per-client authentication.

• Permission-aware communication.

• Secure API requests.

• Read-only media access.

• Domain validation support.

• Optional statistics authorization.

• Protected transport layer.

Bug Fixes

• Improved cURL transport compatibility.

• Updated deprecated transport handling.

• Better HTTP response validation.

• Enhanced timeout management.

• More informative diagnostic messages.

• Improved endpoint verification.

---

Looking Forward

The MediaTube Remote Connection Plugin establishes the communication backbone for future MediaTube deployments.

Future versions will introduce encrypted client registration, automated API key provisioning, webhook subscriptions, event-driven synchronization, distributed cache invalidation, intelligent load balancing, and advanced telemetry.

Together with MediaTube Hub and the MediaTube Remote Module, the plugin completes a three-tier architecture in which centralized administration, secure communication, and distributed presentation operate independently while forming a cohesive and scalable Joomla media platform capable of supporting modern content distribution networks across multiple websites.

Download plg_system_mediatuberemote_1.2.0.zip

Details

Written by: Kim Jacobsen

Category: Blog

Published: 09 August 2026

Hits: 363

MediaTube Remote Module 1.2.x

Extending Joomla Beyond a Single Installation

Modern content platforms increasingly operate across multiple websites rather than within a single content management system. As organizations expand, maintaining identical media libraries on multiple installations becomes inefficient, difficult to synchronize, and costly to administer.

The MediaTube Remote Module addresses this challenge by introducing a distributed publishing architecture that enables multiple Joomla websites to consume media from a centralized MediaTube Hub.

Instead of replicating databases or manually synchronizing content, remote websites securely retrieve media through the MediaTube API while preserving centralized administration.

The result is a scalable media distribution platform capable of powering entire website networks from a single authoritative source.

---

A Centralized Publishing Architecture

The Remote Module transforms MediaTube into a hub-and-client ecosystem.

MediaTube Hub
      │
      │ JSON API
      ▼
Remote Joomla Website
      │
MediaTube Remote Module
      │
      ▼
Visitors

The MediaTube Hub remains the single source of truth.

Remote installations become presentation layers capable of displaying selected media collections while leaving content management entirely to the Hub.

This architecture eliminates duplicated administration and dramatically reduces maintenance requirements.

---

Secure API Communication

Communication between the Remote Module and the Hub occurs through authenticated HTTP requests.

Each remote installation receives its own API credentials and unique Client ID, allowing the Hub to distinguish between connected websites.

Supported security features include:

• Individual API keys

• Client identification

• Domain restrictions

• Rate limiting

• Feed permissions

• Statistics permissions

• Signed traffic attribution

• HTTP cache headers

• ETag support

This allows administrators to expose media safely without granting direct database access.

---

Intelligent Media Distribution

Remote websites may independently configure:

• Adult collections

• Media Stream

• Media Hybrid

• Entire media libraries

• Maximum number of media items

• Ordering methods

• Local cache duration

Every website can therefore present different sections of the same centralized media library while maintaining complete visual independence.

---

Traffic Generation

One of the most powerful capabilities introduced by the Remote Module is intelligent traffic attribution.

Rather than functioning as a simple feed reader, the module allows traffic generated by remote installations to be measured and attributed.

Each click can be routed through the MediaTube Hub, where the originating client and destination media item are recorded before the visitor is redirected to the canonical media page.

This creates measurable insight into how distributed Joomla installations contribute to audience growth.

Administrators can evaluate:

• Top-performing remote websites

• Most-clicked media

• Traffic sources

• Referral efficiency

• Content popularity

• Distribution performance

Publishing decisions can therefore be based on measurable data rather than assumptions.

---

Performance

The Remote Module has been designed with scalability in mind.

Performance optimizations include:

• Local module caching

• Conditional HTTP requests

• Efficient JSON parsing

• Lightweight rendering

• Reduced database duplication

• Minimal server overhead

The architecture allows multiple websites to consume the same media feed while placing minimal load on the Hub.

---

Installation

Installing the Remote Module requires only a few steps.

1. Install MediaTube Hub on the primary Joomla website.

2. Enable the MediaTube Remote API.

3. Generate an API key.

4. Install the MediaTube Remote Package on the client website.

5. Configure:

   • Hub endpoint

   • API key

   • Client ID

6. Publish the MediaTube Remote Module in any Joomla module position.

The remote installation immediately begins displaying media from the centralized Hub.

---

Use Cases

The MediaTube Remote Module is suitable for a wide range of deployment scenarios.

Examples include:

• Multi-brand media networks

• Affiliate websites

• Corporate portal networks

• Community websites

• Regional content distribution

• White-label media platforms

• Educational media portals

• Franchise websites

• Content syndication

Every deployment benefits from centralized administration while maintaining complete freedom over local presentation.

---

Release Notes

Version 1.2.x

New Features

• Introduced MediaTube Hub architecture.

• Secure JSON API integration.

• Individual API key authentication.

• Client identification support.

• Category-specific media distribution.

• Adult, Media Stream and Media Hybrid filters.

• Configurable sorting and item limits.

• Signed traffic attribution.

• Redirect-based click tracking.

• Local response caching.

• HTTP cache validation.

• Improved API diagnostics.

• Enhanced remote error reporting.

• Joomla 5 compatibility improvements.

Improvements

• Optimized remote feed performance.

• Improved module rendering.

• Better response handling.

• Enhanced cache management.

• Cleaner administrator configuration.

• Improved compatibility with MediaTube Hub 2.8.x.

• Refined API communication layer.

Security

• Secure API authentication.

• Optional origin restrictions.

• Per-client permissions.

• Request rate limiting.

• Protected statistics endpoints.

• No direct database exposure.

Bug Fixes

• Corrected Joomla 5 compatibility issues.

• Improved cURL transport handling.

• Removed deprecated transport calls.

• Improved HTTP error diagnostics.

• Enhanced response validation.

• Better endpoint verification.

---

Looking Ahead

The MediaTube Remote Module establishes the technological foundation for a distributed media ecosystem.

Future development will expand this architecture with intelligent synchronization, AI-assisted recommendations, advanced analytics dashboards, webhook integrations, real-time notifications, CDN-aware distribution, and predictive traffic intelligence.

Rather than functioning as a conventional Joomla module, the MediaTube Remote Module represents the beginning of a scalable media distribution platform capable of powering interconnected websites through centralized content management while preserving independent presentation and measurable traffic generation.

Download mod_mediatube_remote_1.2.1.zip