VTIRC Stories

Generic IRC Videotelephony

with advisement for the 100 in mind.

root jitsi domain
 Create a meeting at the root jitsi domain, joinable by anyone knowing the meet id.

The revised VTIRC story uses the KIWI web client which replaced the original qwebirc access to Bitlbee. The service from the jitsi apex is just vanilla jitsi meet with some adjustments for anonymous use in this story and use with whatever you are already using for IRC. So that's manual integration, end of that story.

The main story is an elaborated KiwiIRC jitsi plugin. In the new deal, both qwebirc and Bitlbee are replaced by DCP controlled inspircd and this kiwi plugin which is meant to operate from domain space by its users, so all of them, in this story are AKPERSONs. General user access from the wild can use the generic jitsi meet clients with their irc client of choice if they know meeting nonce phrase. They are then ordinary jitsi anonymous users as whatever they are in the 3rd party irc net which will have its own management of them and the IRC - Jitsi coordination with or without DCP automation they may have elected to use/allow.

The per channel subdomains

E.g. haskell.sameboat, prolog.sameboat, etc., serve libera.chat channel namespaces modeled as DS Popular Groups. A managed path is provided that presents the users of those channels with the ready Kiwi client and other services provided on the commons node.

KIWI servers run in a mcpcms shell provsioned and managed by DCP.

While DS IRC and native (jitsi) VT are modified, in the general case neither IRC servers nor 3rd party VT services are intended to be modified so this story presumes eventual integration of those services and is from start intended to work with existing IRC networks. The design intent is generic first.

Real Time Groups

Popular groups are supported by the common video abstraction, whose default, internal supported backend implementation is jitsi. This support is an intrinsic service in sameboat nodes and popular groups hosted on them. In addition to the D7 derivative, each sameboat node also supports by default MCP cells for current MediaWiki, WordPress, the common local directory system (clfe), and solanum customized for this use.

The design intent for the RTG aspect is two fold: seamless video conf and support for popular groups and form a common driving use case with IRC for temporal context processing in the group domains.