Debian wiki2025 alpha - User contributions [en]

WikiRevamp

2026-08-28T09:04:15Z

RogueScholar-guest: Page cleanup

: '''''Note:''' This was generated using Pandoc to convert MoinMoin's parsed HTML output directly into MediaWiki syntax. This is an experiment to check fidelity.''
At DebConf25, a BOF was dedicated to discuss the state of the Debian Wiki.<ref name="etherpad">[https://salsa.debian.org/debconf-team/public/data/dc25/-/blob/main/etherpad/txt/146-debian-wiki-bof.txt Etherpad from the BOF].</ref> Known historical issues were summarized, in particular:
* The wiki relies on old software.
* There are no clear guidelines on the scope of what is and is not appropriate wiki content.
* There is no "default" license, most of the pages don't specify one and the few who do use a variety of them. As a consequence, most of the pages probably do not comply with DFSG.
* There is no clear way to handle communications about the wiki.

In the following days, action was taken about this.

== Participating ==
Want to help? Start by reading the [[#Communication|very next section below]] on channels of communication. On IRC, you can ask how you can help and participate in discussions regarding migration and licensing.

== Communication ==
The [https://lists.debian.org/debian-wiki debian-wiki mailing list] was created to discuss the Wiki, in addition to the [ircs://irc.oftc.net/debian-wiki #debian-wiki IRC channel]. If you want to participate, you are encouraged to reach via at least one, but ideally both of them, as discussions often occur on both at the same time.

== Software migration ==
: '''''See also:''' The '''[https://lists.debian.org/debian-wiki/2025/07/threads.html#00007 MediaWiki next steps]''' thread on the debian-wiki mailing list''
During the BOF, the possibility was brought up of a migration to MediaWiki: a well-established wiki platform already being used by many others, like Wikipedia and the Arch Wiki.

Since then, @taavi has worked with DSA to setup mozart.debian.org, a machine running Debian Trixie that hosts a MediaWiki instance. It can be accessed at [https://wiki2025.debian.org/ wiki2025.debian.org].

:: <span style="font-size: 1.1rem; font-weight: 700; text-decoration: underline;">Do not begin to migrate content here yet, though, as it could still be erased without notice.</span>

Currently, the plan is to migrate most pages to the MediaWiki instance using tools being developed by @guillem and @maytham, which will retain the edit history of each as well as convert the content to the MediaWiki syntax as a final stage at the end. This is achieved by accessing the internal file-based database for MoinMoin. You can find a demonstration of this at [[FreedomBox]] (in particular, the preservation of the [{{fullurl:FreedomBox|action=history}} edit history]), which is the end result of using the migration tools on the [https://wiki.debian.org/FreedomBox old wiki's page about the same software].

Current resources for conversion:
* @guillem: A Debian fork of the mm2mw Perl scripts for migrating the old edit histories as well as converting the syntax (evolving at [https://salsa.debian.org/guillem/mm2mw <kbd>guillem/mm2mw</kbd>] on Salsa).
* [[User:Maytha8|@maytham]]: Shell scripts to retain edit histories, but without syntax conversion, developed at [https://salsa.debian.org/Maytha8/wiki-scripts <kbd>Maytha8/wiki-scripts</kbd>] on Salsa.
* @sunilmohan: [https://salsa.debian.org/sunilmohan/moinmoin_to_mediawiki/ <kbd>sunilmohan/moinmoin_to_mediawiki</kbd>] on Salsa (based on a tool to generate the [[FreedomBox|FreedomBox]] manual PDF).
* [[User:Andrewsh|@AndrewSayers]]: [https://salsa.debian.org/AndrewSayers/mediawiki-recommendations/ <kbd>AndrewSayers/mediawiki-recommendations</kbd>] on Salsa (a counterpart to the [https://wiki.debian.org/DebianWiki/WikiRevamp/Recommendations recommendations page] on the old wiki).

The configuration and extensions for the new instance have not been finalized yet. @maytham is working on an extension ([https://salsa.debian.org/Maytha8/DebianWiki Salsa repository]) to provide it with the Debian navigation bar that is present on many other Debian sites. New extensions require manual intervention by DSA which can take some time, especially if they are not already packaged for Debian.

== Content licensing ==
The migration provides a good opportunity to think about the long-standing licensing problems that are often interpreted to mean that content from the old wiki cannot in fact be reused or redistributed legally.

Since {{#formatdate:2025-07-24}}, new content on the MoinMoin-based wiki is released under the terms of the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License, version 4.0 (CC-BY-SA-4.0)],<ref name="old_wiki_copyright">[https://wiki.debian.org/copyright.html Copyright page] on the old Debian Wiki.</ref> unless otherwise noted, so non-copyrighted work will gradually be replaced even absent an orchestrated migration effort.

The migration will most likely work like those that occurred for previous MoinMoin version bumps: the old edit history will be retained, followed by a conversion edit to migrate any deprecated syntax. That ensures the migration to MediaWiki isn't blocked on the time-consuming process of rewriting content, and the licensing issues will eventually fade away with the passage of time.

=== Choice of license ===
The Creative Commons license was agreed upon between participants on the mailing list and IRC because it:
* is designed for and applies to content, in contrast to other licenses that are aimed at software source code;
* requires [https://wiki.debian.org/copyright.html#Re-use_of_content attribution] for contributors' hard work;
* ensures any adaptations of the work remain available for reuse/redistribution under the same terms, preventing potential future bad actors from taking the work and making it proprietary; and
* is relatively permissive and compatible with the GNU GPL v3.0.

==== Frequently asked questions ====
: '''''See also:''' The '''[https://lists.debian.org/debian-wiki/2025/07/msg00005.html Re: Content licensing]''' thread on the debian-wiki mailing list''
; Why not a dedication to the public domain, a la CC0?
: The license chosen should generally require attribution. Virtually no content from other sources/sites could be copied to the wiki because nothing is compatible with the public domain except other public domain content.
; Why not Expat (a.k.a., the MIT License)?
: That license is intended for software, whereas the Creative Commons licenses are intended for use specifically with non-software works. Note that the [https://www.debian.org/ Debian website proper] (www.debian.org) uses this, though.
; Why not GFDL?
: In 2006, Debian Developers [https://www.debian.org/vote/2006/vote_001 approved a General Resolution] that defined the project's official posture towards the GFDL, declaring it DFSG-incompatible except when it is used without any of its invariant options. It is also much more restrictive, thereby reducing the possibility of reusing wiki content elsewhere, such as in man pages or the official documentation.
; Why not Creative Commons' NonCommercial (NC) or NoDerivatives (ND) options?
: Neither of those are DFSG-compatible.

=== Old content ===
@maytham is leading an ongoing relicensing effort (coordinated in the [https://salsa.debian.org/Maytha8/wiki-relicensing/ <kbd>Maytha8/wiki-relicensing</kbd> repository] on Salsa), seeking to make contact with all previous Debian Wiki contributors and obtain permission for their work to be re-licensed under CC-BY-SA-4.0.

=== New content ===
Notices have been added to the current wiki stating that any contributions submitted after midnight UTC on {{#formatdate:2025-07-24}} are released under CC-BY-SA-4.0, ''unless otherwise noted''. A copyright.html page<ref name="old_wiki_copyright" /> has also been written up with details on how to be compliant with the license.

== Recommendations and mass edits ==
Before the old wiki can be migrated in bulk, we need to identify all the ways in which it will behave differently and work out how to adapt to those differences. For example, the current wiki has "discussion" pages that end with <code>/Discussion</code>, and are linked from within the page body. The equivalent MediaWiki convention is for "Talk" pages to use the same page name as their "content space" counterparts but nevertheless exist in parallel and separate namespaces that have the word <code>Talk:</code> appended, e.g., <code>Category_talk:</code>, and are linked from above the page content. Rules and recommended processes are being written up at [https://wiki.debian.org/DebianWiki/WikiRevamp/Recommendations WikiRevamp/Recommendations] on the old wiki.

Several differences involve converting loose editing conventions to automated rules by writing pattern-matching code and doing mass edits to normalize all of the migrated content under a single, workable format. For example, "discussion" links on the old wiki have almost always been added by individual editors with page-specific styling. Every instance of that will need to be removed or massaged into conformity with the migration tool's definition of acceptable syntax. To achieve that, we plan to change all discussion links to [https://wiki.debian.org/HelpOnProcessingInstructions#supplementation supplementation page instructions] that can be easily removed during the migration process. Tools for these conversions are available in the [https://salsa.debian.org/AndrewSayers/mediawiki-recommendations/ <kbd>mediawiki-recommendations</kbd> repository] on Salsa.

=== Specific mass edits ===
A "mass edit" refers to using an automation tool to process and edit a great many (usually hundreds or thousands) of pages at once with the goal of tackling very pervasive formatting issues in a deterministic manner. The term itself is a reference to MediaWiki's own [[mediawikiwiki:Special:MyLanguage/Extension:MassEditRegex|MassEditRegex extension]].

Some target objectives for these tasks have already been identified.
; <kbd>#language</kbd> tags ({{#formatdate:2025-08-17}})
: Many old wiki pages have a processing instruction such as <code>#language pt_BR</code>. This edit changed about 15 pages with errors in their processing instructions; see the [https://lists.debian.org/debian-wiki/2025/08/msg00028.html mailing list thread] for more details.
; Category footers ({{#formatdate:2025-08-17}})
: Categories are generally appended to pages after a [https://wiki.debian.org/HelpOnRules horizontal rule] generated by entering four consecutive hyphen-minuses on a line by themselves in the page's source code. This edit changed about 620 pages containing issues that made it harder to detect the category list; see the [https://lists.debian.org/debian-wiki/2025/08/msg00028.html mailing list thread] for more details.
; <kbd><nowiki><<FullSearch>></nowiki></kbd> ({{#formatdate:2025-09-06}} and {{#formatdate:2025-09-07}})
: MoinMoin's [https://wiki.debian.org/HelpOnMacros#A:.2BAH4:text.3DFullSearch <kbd><nowiki><<FullSearch>></nowiki></kbd> macro] doesn't have a direct MediaWiki equivalent, so we will need to convert it differently depending on its contents. This edit changed about 130 pages in an effort to reduce the number of patterns that need to be considered; see the [https://lists.debian.org/debian-wiki/2025/09/msg00000.html mailing list thread] for more details.
; Translation page names ({{#formatdate:2025-10-04}})
: Translations should have page names that resemble each other, but many old wiki pages don't fit that pattern, such as when some language translations haven't been updated since the English version was renamed). This edit renamed approximately 100 pages to fit the normal naming convention; see the [https://lists.debian.org/debian-wiki/2025/09/msg00013.html mailing list thread] for more details.
; Non-wiki <kbd>#format</kbd>s ({{#formatdate:2026-02-20}} and {{#formatdate:2026-02-21}})
: MoinMoin's [https://wiki.debian.org/HelpOnProcessingInstructions#A.23format <kbd>#format</kbd> processing instruction] isn't widely used, but adds another special case to the migration process; consider using a page-wide [https://wiki.debian.org/HelpOnParsers#highlight_parser <kbd>#!highlight</kbd> block] instead. See the [https://lists.debian.org/debian-wiki/2026/02/msg00002.html mailing list thread] for more details.

=== Responding to mass edits ===
If you expect an upcoming mass edit to affect a lot of pages you maintain, consider making a rule to ignore e-mails with the subject <code>Update of ".*" by <author></code> and a date within the specified range, where <author> is the wiki username of the person managing the edit (e.g. [[User:Andrewsh|Andrew Sayers]]).

If you wish to object to an upcoming mass edit, contact the mailing list (preferably in a reply to that edit's announcement thread) before it occurs and explain your objection. We'll talk through the issue and look for suitable ways to change the upcoming work. If you're having difficulty phrasing your objection, it's fine to just say "I need time to think through the implications, please postpone by a week," and then write a longer reply a few days later.

If you want to object to an already-completed mass edit, you should again make contact on the mailing list after reverting the change, explaining your objection. We'll look for solutions, e.g., a new mass-edit to fix other pages. Editors are usually notified about changes to pages they've edited, but a mass edit that affects a thousand pages will generate notifications for all future changes to all thousand pages, so you shouldn't assume the mass editor has seen your reversion.

== Other conversations ==
: '''''Be advised:''''' {{MoinMarkup/Smiley|alert}} ''This section attempts to summarize conversations from the [https://lists.debian.org/debian-wiki mailing list] and [ircs://irc.oftc.net/debian-wiki IRC channel]. It will always be somewhat out-of-date and incomplete.'' {{MoinMarkup/Smiley|alert}}

=== Debian Bug Tracker links ===
: '''''See also:''' The [https://lists.debian.org/debian-wiki/2025/07/msg00054.html DebianBug links thread] on the mailing list.''
The current wiki renders links to Debian and Ubuntu bugs with a distinct style, receiving a <code>title</code> attribute with their subject line, with closed bugs also shown struck with a line through them. For example, the following bugs should be struck through, and you should see a tooltip with their subject line when you hover your mouse pointer over them: [https://bugs.debian.org/399237 <span title="installation-reports: Etch-rc1 on Thinkpad T60 [SUCCESS]" style="text-decoration: line-through;">Bug #399237</span>] and [https://bugs.launchpad.net/bugs/1597017 <span title="AppArmor: mount rules grant excessive permissions" style="text-decoration: line-through;">LP #1597017</span>].

At the code level, this is implemented by including [https://salsa.debian.org/debian/wiki.debian.org/-/blob/master/usr/htdocs/bugstatus.js <code>bugstatus.js</code>] in every page, where it scans the HTML for those specific link types and sends requests to the [https://salsa.debian.org/debian/wiki.debian.org/-/blob/master/bin/bugstatus bugstatus script] and the [https://salsa.debian.org/debian/wiki.debian.org/-/blob/master/bin/launchpad launchpad script]. The bugstatus script in turn uses the [https://wiki.debian.org/DebbugsSoapInterface Debbugs SOAP interface] while the launchpad script uses the eponymous [https://pypi.org/project/launchpadlib/ <code>launchpadlib</code> Python module].

The MediaWiki alternatives to these approaches include:
* <kbd>[[MediaWiki:Common.js]]</kbd> is a JavaScript file included in every page on a wiki. This is the alternative that's most similar in function, but it can be hard to manage because of the temptation to put unrelated content in the same file.
* The MediaWiki [[mediawikiwiki:Special:MyLanguage/Extension:Gadgets|Gadgets extension]] is a more powerful alternative to MediaWiki:Common.js, and seems like the natural choice for a replacement for the current MoinMoin implementation.
* [[mediawikiwiki:Special:MyLanguage/Manual:$wgEnableScaryTranscluding|Scary transcluding]] lets you include pages and templates from other wikis with a cache for the page data and a configurable timeout. For example, this would let us run an internal service that generates HTML from some pre-existing Perl library, then transclude that HTML into ordinary wiki pages. It's the wrong tool for this particular job, but may be worth revisiting if other use cases pop up.
* The [[mediawikiwiki:Special:MyLanguage/Extension:Cargo|Cargo extension]] lets MediaWiki store and query data in an internal database (which could potentially be synchronised with an external database, somehow), but Cargo has a poor security reputation and synchronizing the data could be awkward.
* The [[mediawikiwiki:Special:MyLanguage/Extension:External Data|External Data extension]] lets MediaWiki interrogate external sources, like the [https://wiki.debian.org/UltimateDebianDatabase Ultimate Debian Database]. This would let us render links server-side instead of in JavaScript, but would introduce questions around caching. Allowing the wiki to query the UDD opens up a lot of interesting possibilities, and this might be a good way to make that possible. This is the solution we currently expect to eventually make use of.

=== Migrating user accounts ===
: '''''See also:''' The [https://lists.debian.org/debian-wiki/2025/07/msg00073.html "How to manage new Salsa accounts with the new wiki" thread] on the mailing list.''
The plan is to switch from MoinMoin's built-in user database to authenticating using Salsa accounts, so people will need to [https://salsa.debian.org/users/sign_up create a Salsa account].

The suggested solution is to disable creation of new wiki accounts at some point and give account holders from the old wiki replacement accounts on Salsa with the same username, and ask them to change their information if they want.

=== Boilerplate page headers ===
Pages often start with some boilerplate text (i.e., translation headers). Putting a common header template on all pages would make it easier to manage that text; see [[Template:PageHeader]] for an initial demonstration of how that might look. This has been mentioned in passing, but no firm decision has yet been made.

=== Translations ===
: '''''See also:''' The [https://lists.debian.org/debian-wiki/2025/08/msg00005.html "Info request on new Wiki translations - any automatic handling of translation headers and translated pages?" thread] on the mailing list.''
We plan to install MediaWiki's [[mediawikiwiki:Special:MyLanguage/Help:Extension:Translate|Translate extension]] to handle content localization workflows. The benefits of doing this include:
* No need to maintain a <code>TAG:TRANSLATION-HEADER</code> block, instead just add <code><nowiki><languages /></nowiki></code> to the top of a page and the rest is handled automatically on the backend.
** For a good example of this extension in action, check out the "Languages" block at the top of Translate extension's [[mediawikiwiki:Special:MyLanguage/Help:Extension:Translate|help page]].
* It provides advanced translation tools, like always showing up-to-date completion progress for each language and suggesting machine translation suggestions to translators directly within the interface.
* It will likely be familiar to people coming here from other MediaWiki-based wikis, too.

We could avoid the need to manually add <code><nowiki><languages /></nowiki></code> tags to pages by installing MediaWiki's [[mediawikiwiki:Special:MyLanguage/Extension:UniversalLanguageSelector|Universal Language Selector extension]] and enabling [[mediawikiwiki:Special:MyLanguage/Help:Extension:Translate/Configuration#:~:text=$wgTranslatePageTranslationULS|wgTranslatePageTranslationULS]]. To see how this works, go to the [[wikipedia:Debian|Debian]] article on English Wikipedia and there click on the [[File:CdxIconLanguage.png|x22px]] Languages button near the top of the page.

Another approach would be to write our own custom templates for managing translations (see [[ExampleForTranslation]] for a proof of concept). They would have no external dependencies and we could modify them more easily, but they'd be harder to maintain and wouldn't have as many features.

Still another alternative would be [https://wiki.openstreetmap.org/wiki/Template:Languages OpenStreetMap Wiki's Languages template], which is powered by a [https://wiki.openstreetmap.org/wiki/Module:Languages Lua module] so it only requires the common [[mediawikiwiki:Special:MyLanguages/Extension:Scribunto|Scribunto extension]]. It would probably produce a better result than custom templates, but doesn't provide the advanced tools found in MediaWiki's solution.

We plan to include a template for linking to localized versions of pages, so for example, if you're translating <code>Some page</code> and encounter a link to <code>This other page</code>, you would only need to use a simple syntax like <code>{{[[Template:Ll|'''Ll''']]|This other page}}</code> to create a link to that page's translations to the same language on all of the translations of <code>Some page</code>; see MediaWiki's [[mediawikiwiki:Special:MyLanguage/Template:Localized_link|Localized link]] template, OpenStreetMap Wiki's [https://wiki.openstreetmap.org/wiki/Template:LL LL] template, and our very own [[Template:Ll]] right here to compare the implementation choices.

=== Editorial tasks (e.g. CategoryProposedDeletion) ===
: '''''See also:''' The summary of the IRC discussion surrounding [https://lists.debian.org/debian-wiki/2025/07/msg00068.html "Issues around CategoryProposedDeletion"].''
On the MoinMoin wiki, pages are added to [https://wiki.debian.org/DebianWiki/Administration#Current_tasks editorial categories] like [https://wiki.debian.org/CategoryProposedDeletion CategoryProposedDeletion], with the expectation that the editorial work will be undertaken at some time in the future. That editorial process is discussed in the [https://wiki.debian.org/DebianWiki/EditorGuide editor guide] there.

MediaWiki makes it easy to create more verbose and precise admonitions, with guidance on the page itself; see the pro forma [[ExampleForProposedDeletion]] for one potential style.

=== Scope ===
Discussion on the scope of the wiki is ongoing, but still in early stages. Most of it is happening in the ''[https://lists.debian.org/debian-wiki/2025/08/msg00015.html "aims of the wiki?"]'' thread on the mailing list.

A draft of potential guidelines was published at [https://wiki.debian.org/MaythamAlsudany/DraftContentGuidelines MaythamAlsudany/DraftContentGuidelines] on the old wiki, with related discussions about them ongoing at the [https://wiki.debian.org/MaythamAlsudany/DraftContentGuidelines/Discussion /Discussion] subpage.

=== Milestones and gamification ===
MediaWiki automatically sends editors congratulatory notifications when they make a "milestone" number of edits (1st, 10th, 100th, etc.). This can be disabled by going to your [[Special:Preferences#mw-prefsection-echo event|User preferences]] page and disabling the "Edit milestone" option, but there doesn't seem to be a way to disable this by default for all new users.

=== Automated bot edits ===
We don't have bots making edits to the old wiki, but some proposals for the new wiki would benefit from such automation.
* The Debian [https://wiki.debian.org/DebianWiki/WikiRevamp#Debian_Bug_Links Bug Tracker links] handling could be implemented without JavaScript, so long as editors remember to create links to them as template calls (a la <code>{{[[Template:DebianBug|'''DebianBug''']]|NNN}}</code>) instead of <code><nowiki>[[DebianBug:NNN]]</nowiki></code> or <code><nowiki>[https://bugs.debian.org/NNN Bug #NNN]</nowiki></code>. That's more likely to happen if a bot fixes those links automatically.
* [https://wiki.debian.org/DebianWiki/WikiRevamp#Boilerplate_page_headers Boilerplate page headers], such as those for [https://wiki.debian.org/DebianWiki/WikiRevamp#Translations translations], need to be added to the top of each page. Having a bot do that is probably easier than educating each new editor that comes along.
* [https://wiki.debian.org/DebianWiki/WikiRevamp#Editorial_tasks_.28e.g._CategoryProposedDeletion.29 Editorial tasks] involve scheduling some action for a particular future date (e.g., deleting a page if nobody objects for one month). Automating those actions would give everyone more certainty about the issue, and might mean non-admin users don't need permission to delete pages themselves.
** An alternative would be to encourage people to help clean up the wiki in general, rather than just focus on their little corner of it. This hasn't worked before, because doing so is less inherently rewarding, risks treading on others' toes, and is unnecessarily hard work in MoinMoin, but this hasn't had its own dedicated discussion, and no decision has been made.

=== Interwiki links vs. templates ===
: '''''See also:''' The brief mention in the [https://lists.debian.org/debian-wiki/2025/07/msg00053.html#:~:text=DebianIRC "Re: Complex conversion issues"] thread on the mailing list, and the resulting [[Template:DebianIRC|DebianIRC template]].''

The current wiki's [https://wiki.debian.org/InterWikiMap InterWikiMap] is quite large, and as evidenced by the debate over [https://wiki.debian.org/DebianWiki/WikiRevamp#Debian_Bug_Links Debian Bug links] there's interest in pushing beyond what it's currently designed to handle. MediaWiki [[mediawikiwiki:Special:MyLanguage/Manual:Interwiki|interwiki links]] can only be changed by editing a database table, so a direct translation would be harder to use than the current solution.

Templates are more flexible than interwiki links, and also more familiar to users. So far, nobody has objected to the idea of converting most interwiki links to templates.

== References ==
<references />

== See also ==
* The [https://lists.debian.org/debian-wiki debian-wiki mailing list]
* The [ircs://irc.oftc.net/debian-wiki #debian-wiki] IRC channel on the OFTC network
* The [[Main Page|demo instance of the new MediaWiki-based Debian Wiki]]
* [[:Category:Example|Some examples of ideas for the new wiki]]

Template:DebianBug

2026-08-28T08:51:22Z

RogueScholar-guest: Convert to more common parser tag arragement

<includeonly>{{InterWiki|DebianBug|{{{suffix|{{{1|}}}}}}|{{{text|{{{2|}}}}}}}}</includeonly><noinclude>
== Usage ==
: {{InterWikiBoilerplate}}

=== TemplateData ===
<templatedata>{
"description": "Creates links to https://bugs.debian.org/ using Extension:Interwiki, so they don't get styled as external",
"params": {
"suffix": {
"type": "line",
"required": true,
"description": "URL suffix to link to",
"aliases": ["1"]
},
"text": {
"type": "line",
"required": false,
"description": "Link text",
"aliases": ["2"]
}
}
}</templatedata></noinclude>

File:CdxIconLanguage.png

2026-08-28T05:16:27Z

RogueScholar-guest: The official [https://doc.wikimedia.org/codex/latest/icons/all-icons.html Wikimedia Codex language icon].

== Summary ==
The official [https://doc.wikimedia.org/codex/latest/icons/all-icons.html Wikimedia Codex language icon].
== Licensing ==
{{cc-by-4.0}}

FreedomBox/Manual/Coturn

2026-08-28T03:54:51Z

RogueScholar-guest: Remove disallowed custom display title and change large image wiki is unable to resize to center alignment

[[File:Coturn icon-en V01.webp|thumb|right|Coturn icon]]
'''Available since''': version 20.8

== Coturn (VoIP Helper) ==
Coturn is a server to facilitate audio/video calls and conferences by providing an implementation of [[wikipedia:Traversal Using Relays around NAT|TURN]] and [[wikipedia:STUN|STUN]] protocols. WebRTC, SIP and other communication servers can use it to establish a call between parties who are otherwise unable connect to each other.

It is not meant to be used directly by users. Servers such as Matrix Synapse need to be configured with the details provided on the Coturn app page. Apart from Matrix Synapse, Jitsi, Ejabberd, Nextcloud Talk, etc. can use Coturn server for audio/video calls and conferences. There is no need for the servers to be running on the same machine as FreedomBox and external servers can use Coturn running on FreedomBox.

Coturn is configured in FreedomBox as an advanced app. This means that you need to check 'Show advanced apps and features' in 'General Configuration' to see Coturn icon in the Apps section.

=== How it works ===
When making an audio/video call, it is best to route the media streams between two peers directly. This will give the best possible latency (better signal quality) and avoid depending on a centralized server (privacy). It scales well because a simple chat server can host thousands of calls without involving the server in any way other than to setup the call. However, this approach does not work most of the time due to how networks are configured. Most peers on the network do not have a unique IP address allocated to them. They work hidden behind a network device that performs 'Network Address Translation' (NAT) for them. This means that the two peers have no way of reaching each other.

To address this problem, a simple technique known as STUN was introduced. With the help of a third party STUN server, the peers can trick the NAT devices, to carry the traffic between the two peers. Unfortunately, this trick only works about 80% of the time. So, if STUN fails, peers have no choice but to route their traffic through an intermediary server called TURN server. All the mechanism of trying out STUN first and then falling back to TURN is described in a protocol known as [[wikipedia:Interactive Connectivity Establishment|ICE]], an acronym for Interactive Connectivity Establishment.

On FreedomBox, Coturn provides both STUN and TURN servers. Both services are provided over TCP as well as UDP. They are provided on unencrypted as well as encrypted channels (which have a higher chance of success). Since STUN servers are very inexpensive and don't consume a lot of server resources, there is no authentication needed to use them. TURN servers on the other hand need authentication. This authentication is highly simplified and does not require maintaining a database of users. A server such as matrix-synapse which is about to setup an audio/video call between two peers will generate a username and password using a shared secret. When the peers use the TURN server, they will be validated using these credentials because the TURN server also knows the same secret.

In summary, a communication server needs to know the URLs of the STUN/TURN servers along with a shared authentication secret for TURN. After that, during audio/video call setup, they will correctly guide the peers to use STUN/TURN servers. Coturn app in FreedomBox provides exactly this information. This information can be used to configure a communication server irrespective of whether it is running on the same FreedomBox or on another server.

=== Configuring Matrix Synapse ===
To configure Matrix Synapse to use Coturn TURN/STUN server, you need to check 'Automatically manage audio/video call setup' in Matrix Synapse's configuration section, and then click on Update.

[[File:Matrix Synapse with Coturn.webp|frame|center|Matrix with Coturn]]

=== Port Forwarding ===
If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Coturn:
* UDP 3478
* TCP 3478
* UDP 3479
* TCP 3479
* UDP 5349
* TCP 5349
* UDP 5350
* TCP 5350
* UDP 49152-50175
* TCP 49152-50175

== External links ==
* [https://github.com/coturn/coturn Upstream project]
* [https://github.com/coturn/coturn/wiki/ End user documentation]

FreedomBox/Manual/Coturn

2026-08-28T03:52:21Z

RogueScholar-guest: Fix broken file and interwiki links

[[File:Coturn icon-en V01.webp|thumb|right|Coturn icon]]
'''Available since''': version 20.8

== Coturn (VoIP Helper) ==
Coturn is a server to facilitate audio/video calls and conferences by providing an implementation of [[wikipedia:Traversal Using Relays around NAT|TURN]] and [[wikipedia:STUN|STUN]] protocols. WebRTC, SIP and other communication servers can use it to establish a call between parties who are otherwise unable connect to each other.

It is not meant to be used directly by users. Servers such as Matrix Synapse need to be configured with the details provided on the Coturn app page. Apart from Matrix Synapse, Jitsi, Ejabberd, Nextcloud Talk, etc. can use Coturn server for audio/video calls and conferences. There is no need for the servers to be running on the same machine as FreedomBox and external servers can use Coturn running on FreedomBox.

Coturn is configured in FreedomBox as an advanced app. This means that you need to check 'Show advanced apps and features' in 'General Configuration' to see Coturn icon in the Apps section.

=== How it works ===
When making an audio/video call, it is best to route the media streams between two peers directly. This will give the best possible latency (better signal quality) and avoid depending on a centralized server (privacy). It scales well because a simple chat server can host thousands of calls without involving the server in any way other than to setup the call. However, this approach does not work most of the time due to how networks are configured. Most peers on the network do not have a unique IP address allocated to them. They work hidden behind a network device that performs 'Network Address Translation' (NAT) for them. This means that the two peers have no way of reaching each other.

To address this problem, a simple technique known as STUN was introduced. With the help of a third party STUN server, the peers can trick the NAT devices, to carry the traffic between the two peers. Unfortunately, this trick only works about 80% of the time. So, if STUN fails, peers have no choice but to route their traffic through an intermediary server called TURN server. All the mechanism of trying out STUN first and then falling back to TURN is described in a protocol known as [[wikipedia:Interactive Connectivity Establishment|ICE]], an acronym for Interactive Connectivity Establishment.

On FreedomBox, Coturn provides both STUN and TURN servers. Both services are provided over TCP as well as UDP. They are provided on unencrypted as well as encrypted channels (which have a higher chance of success). Since STUN servers are very inexpensive and don't consume a lot of server resources, there is no authentication needed to use them. TURN servers on the other hand need authentication. This authentication is highly simplified and does not require maintaining a database of users. A server such as matrix-synapse which is about to setup an audio/video call between two peers will generate a username and password using a shared secret. When the peers use the TURN server, they will be validated using these credentials because the TURN server also knows the same secret.

In summary, a communication server needs to know the URLs of the STUN/TURN servers along with a shared authentication secret for TURN. After that, during audio/video call setup, they will correctly guide the peers to use STUN/TURN servers. Coturn app in FreedomBox provides exactly this information. This information can be used to configure a communication server irrespective of whether it is running on the same FreedomBox or on another server.

=== Configuring Matrix Synapse ===
To configure Matrix Synapse to use Coturn TURN/STUN server, you need to check 'Automatically manage audio/video call setup' in Matrix Synapse's configuration section, and then click on Update.

[[File:Matrix Synapse with Coturn.webp|frame|right|Matrix with Coturn]]

=== Port Forwarding ===
If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Coturn:
* UDP 3478
* TCP 3478
* UDP 3479
* TCP 3479
* UDP 5349
* TCP 5349
* UDP 5350
* TCP 5350
* UDP 49152-50175
* TCP 49152-50175

== External links ==
* [https://github.com/coturn/coturn Upstream project]
* [https://github.com/coturn/coturn/wiki/ End user documentation]

{{DISPLAYTITLE:Coturn (VoIP Helper)}}

File:Matrix Synapse with Coturn.webp

2026-08-28T03:46:40Z

RogueScholar-guest: File migration from old [https://wiki.debian.org/FreedomBox/Manual/Coturn?action=AttachFile&do=view&target=matrix_with_coturn.png MoinMoin-based Debian Wiki].

== Summary ==
File migration from old [https://wiki.debian.org/FreedomBox/Manual/Coturn?action=AttachFile&do=view&target=matrix_with_coturn.png MoinMoin-based Debian Wiki].
== Licensing ==
{{cc-by-sa-4.0}}

File:Coturn icon-en V01.webp

2026-08-28T03:35:03Z

RogueScholar-guest: File migration from [https://wiki.debian.org/FreedomBox/Manual/Coturn?action=AttachFile&do=view&target=Coturn-icon_en_V01.png MoinMoin-based Debian Wiki].

== Summary ==
File migration from [https://wiki.debian.org/FreedomBox/Manual/Coturn?action=AttachFile&do=view&target=Coturn-icon_en_V01.png MoinMoin-based Debian Wiki].
== Licensing ==
{{cc-by-sa-4.0}}

Category:Pages with broken file links

2026-08-28T03:28:09Z

RogueScholar-guest: Create tracking category

This is a [[Special:TrackingCategories|tracking category]] for pages with '''broken file links'''.

[[Category:Wiki maintenance|Broken file links]]

User talk:RogueScholar-guest

2026-04-17T10:19:04Z

RogueScholar-guest: Create user talk page

Holler at me here, if you need to. No guarantees are made that grievances will be corrected to anyone's satisfaction besides my own, though…remember, we're on the internet.

User:RogueScholar-guest

2026-04-17T10:14:28Z

RogueScholar-guest: Create user page

I'm RogueScholar (or occasionally RScholar) all over the G*d-damned internet at this point; chances are that if you've interacted with or noticed someone by those usernames at a code forge, Linux distribution or crowdsourced public initiative like the Wikimedia projects, MusicBrainz or OpenStreetMap, it was me. Unless you thought that person was a major dick, then it most certainly was someone else. … My friends call me Peter, and my ''really'' close friends call me PoopDawg (it's a long story, though people seem to like it when they hear it).

I'm friendly enough but also quite a glutton for punishment, since I enjoy participating in large, collaborative endeavors despite intensely preferring to work alone. 🤣 If you need to get my attention, please be amply stocked with patience and persistence. I stay busy by design and often have a lag in responding to communiqués. If it's important, just repeat the request and I'll try to bump you to the front of the queue.

<div style="float: right; font-size: 1.03rem; font-style: italic; font-weight: 600; margin-right: 5%;">Keep on keepin' on – life's a garden. Dig it?</div>

Template:Action

2026-04-17T09:53:55Z

RogueScholar-guest: Give the template some actual documentation and flesh out the functionality with parameterized control over action, link target and text

<span class="plainlinks">{{#switch:{{{action|{{{1|}}}}}}
| info | history | log = [{{fullurl:{{{page|{{{2|{{FULLPAGENAME}}}}}}}}|action=history}} {{{text|{{{3|view history}}}}}}]
| recoverpass | login = [https://salsa.debian.org/users/sign_in {{{text|{{{3|reset password}}}}}}]
| subscribe | watch = [{{fullurl:{{{page|{{{2|{{FULLPAGENAME}}}}}}}}|action=watch}} {{{text|{{{3|add to watchlist}}}}}}]
| userprefs | preferences = [[Special:Preferences|{{{text|{{{3|preferences}}}}}}]]
| edit | #default = [{{fullurl:{{{page|{{{2|{{FULLPAGENAME}}}}}}}}|action=edit}} {{{text|{{{3|edit page}}}}}}]
}}</span><noinclude><div style="clear: both;"></div>
This template, <code style="background: transparent; border: hidden; font-weight: 600;">{{[[Template:Action|Action]]}}</code>, produces links that perform an action on the target page through the use of URL query parameters. The design goal is to provide equivalent functionality to MoinMoin's <kbd><<Action()>></kbd> macro. Note that this only replicates functionality that existed on the Debian wiki at the time of migration—other actions may be supported by MoinMoin itself.

== Usage ==
The baseline behavior for the template is to produce a link to edit the page it appears on, using the text: {{Action}}; when invoked with no parameters that will always be the result.

=== Parameters ===
This template currently accepts three parameter values, though none of them are strictly required. They are each independent of the others and can be used individually or in any combination to suit the situation. They may be used either by name or as unnamed positional parameters, but beware that the latter style requires that parameters always be defined in tandem with any others that precede them in the positional sequence (i.e., you can only set the second parameter along with the first, and only set the third after the other two). The loophole in that scenario is that the preceding positional parameters do not need to be used, per se, since null (empty) values are accepted as valid.

{| class="wikitable" style="text-align: center;"
! Position
! style="min-width: 8rem;" | Name
! Description
|-
| 1<sup>st</sup>
| <code>|action=</code>
| style="text-align: left;" | One of a set of keywords that specify the desired page action to trigger, with <code>edit</code> as the default when not defined. The list of valid keywords can be found in the [[#TemplateData|§ TemplateData]] section below.
|-
| 2<sup>nd</sup>
| <code>|page=</code>
| style="text-align: left;" | The name of the page to perform the action on, ''including the namespace'' if not in Main. If <code>|action=<<var>login</var>|<var>preferences</var>|<var>recoverpass</var>|<var>userprefs</var>></code>, this parameter is ignored.
|-
| 3<sup>rd</sup>
| <code>|text=</code>
| style="text-align: left;" | The text to be linked to the page action; when undefined sensible defaults are used.
|}

=== Link text ===
The default link text used by each of the action keywords is as follows:
{| class="wikitable" style="text-align: center;"
|+ Default values for <code>|text=</code>/<code>|3=</code> based on <code>|action=</code>/<code>|1=</code>
! scope="col" style="min-width: 14rem;" | Action keyword
! scope="col" style="min-width: 12rem;" | Default text
|-
! scope="row" | <code>edit</code>
| {{Action|edit}}
|-
! scope="row" | <code>history</code>, <code>info</code>, <code>log</code>
| {{Action|info}}
|-
! scope="row" | <code>login</code>, <code>recoverpass</code>
| {{Action|login}}
|-
! scope="row" | <code>preferences</code>, <code>userprefs</code>
| {{Action|userprefs}}
|-
! scope="row" | <code>subscribe</code>, <code>watch</code>
| {{Action|watch}}
|}

== TemplateData ==
<templatedata>{
"description": "Produces linked text that triggers an action on the target page through the use of URL query parameters; specifically designed as a drop-in replacement for MoinMoin-style action behaviors",
"format": "inline",
"paramOrder": [
"action",
"page",
"text"
],
"params": {
"action": {
"label": "Page action",
"description": "The action to trigger on the target page",
"type": "line",
"aliases": [
"1"
],
"default": "edit",
"example": "history",
"suggestedvalues": [
"edit",
"history",
"info",
"log",
"login",
"preferences",
"recoverpass",
"subscribe",
"userprefs",
"watch"
],
"required": true
},
"page": {
"label": "Target page",
"description": "The page to perform the action on, defaults to the transcluding page if omitted.",
"type": "wiki-page-name",
"aliases": [
"2"
],
"default": "{{FULLPAGENAME}}",
"example": "Doc-base",
"suggested": true
},
"text": {
"label": "Link text",
"description": "The displayed text that will be linked to the page action; sensible defaults will be used if omitted.",
"type": "line",
"aliases": [
"3"
],
"example": "Edit me!",
"required": false
}
}
}</templatedata>

== Template demo / sandbox ==
A demonstration page for its feature set is available at [[ExampleForAction]].

[[Category:MoinMarkup]]
</noinclude>