#mediawiki — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mediawiki, aggregated by home.social.
-
Someone's made a #MediaWiki based blogging thing! 🎉
-
Since my MediaWiki postgres container is working again… Taking the vacuum through the tickets.
Some of this is so easy to fix, but you need to be able to test the changes, and often Postgres support is broken again when you want to look at any of these.
-
I've been setting up #Imagor to work with #MediaWiki and it's all pretty straight forward so far. (I'm writing this I guess to curse myself to a day of annoying debugging tomorrow.)
-
I've been setting up #Imagor to work with #MediaWiki and it's all pretty straight forward so far. (I'm writing this I guess to curse myself to a day of annoying debugging tomorrow.)
-
I've been setting up #Imagor to work with #MediaWiki and it's all pretty straight forward so far. (I'm writing this I guess to curse myself to a day of annoying debugging tomorrow.)
-
I've been setting up #Imagor to work with #MediaWiki and it's all pretty straight forward so far. (I'm writing this I guess to curse myself to a day of annoying debugging tomorrow.)
-
RE: https://fosstodon.org/@bluespice/117235083666058960
We'll be exploring the topic of tables, visualizations, and dashboards in knowledge databases. And you'll get a glimpse into our current developments.
#foss #opensource #wiki #mediawiki #bluespice #atlassian #confluence
-
In two months, the #MUDcon (the MediaWiki Users and Developers Conference Fall 2026) will take place in beautiful Ljubljana, Nov 11-13.
If you want to share your experience both in using or developing MediaWiki in all its facets, please participate or contribute:
https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conference_Fall_2026/Call_for_Contributions@ECHOLOT_Project @MWStake
#MediaWiki #SemanticMediaWiki #Wiki -
In two months, the #MUDcon (the MediaWiki Users and Developers Conference Fall 2026) will take place in beautiful Ljubljana, Nov 11-13.
If you want to share your experience both in using or developing MediaWiki in all its facets, please participate or contribute:
https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conference_Fall_2026/Call_for_Contributions@ECHOLOT_Project @MWStake
#MediaWiki #SemanticMediaWiki #Wiki -
In two months, the #MUDcon (the MediaWiki Users and Developers Conference Fall 2026) will take place in beautiful Ljubljana, Nov 11-13.
If you want to share your experience both in using or developing MediaWiki in all its facets, please participate or contribute:
https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conference_Fall_2026/Call_for_Contributions@ECHOLOT_Project @MWStake
#MediaWiki #SemanticMediaWiki #Wiki -
In two months, the #MUDcon (the MediaWiki Users and Developers Conference Fall 2026) will take place in beautiful Ljubljana, Nov 11-13.
If you want to share your experience both in using or developing MediaWiki in all its facets, please participate or contribute:
https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conference_Fall_2026/Call_for_Contributions@ECHOLOT_Project @MWStake
#MediaWiki #SemanticMediaWiki #Wiki -
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
* https://www.w3.org/html/wg/wiki/Main_Page
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.
Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page).
This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.
Here is how to find such a page’s history:
1. Find the “last modified” date in the footer and note the year, month, day.
2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/"
3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today.
4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that.
5. You may have to "close toolbar" the (x) in the top right of the page content.
6. Note the "View History" link, click it.
Presto, view history on a former MediaWiki page that’s been archived to static HTML.
This is my second #WASSUP #WASSUP2026 post, and first useful web tip.
#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified -
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
* https://www.w3.org/html/wg/wiki/Main_Page
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.
Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page).
This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.
Here is how to find such a page’s history:
1. Find the “last modified” date in the footer and note the year, month, day.
2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/"
3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today.
4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that.
5. You may have to "close toolbar" the (x) in the top right of the page content.
6. Note the "View History" link, click it.
Presto, view history on a former MediaWiki page that’s been archived to static HTML.
This is my second #WASSUP #WASSUP2026 post, and first useful web tip.
#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified -
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
* https://www.w3.org/html/wg/wiki/Main_Page
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.
Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page).
This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.
Here is how to find such a page’s history:
1. Find the “last modified” date in the footer and note the year, month, day.
2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/"
3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today.
4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that.
5. You may have to "close toolbar" the (x) in the top right of the page content.
6. Note the "View History" link, click it.
Presto, view history on a former MediaWiki page that’s been archived to static HTML.
This is my second #WASSUP #WASSUP2026 post, and first useful web tip.
#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified -
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
* https://www.w3.org/html/wg/wiki/Main_Page
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.
Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page).
This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.
Here is how to find such a page’s history:
1. Find the “last modified” date in the footer and note the year, month, day.
2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/"
3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today.
4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that.
5. You may have to "close toolbar" the (x) in the top right of the page content.
6. Note the "View History" link, click it.
Presto, view history on a former MediaWiki page that’s been archived to static HTML.
This is my second #WASSUP #WASSUP2026 post, and first useful web tip.
#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified -
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
* https://www.w3.org/html/wg/wiki/Main_Page
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.
Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page).
This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.
Here is how to find such a page’s history:
1. Find the “last modified” date in the footer and note the year, month, day.
2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/"
3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today.
4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that.
5. You may have to "close toolbar" the (x) in the top right of the page content.
6. Note the "View History" link, click it.
Presto, view history on a former MediaWiki page that’s been archived to static HTML.
This is my second #WASSUP #WASSUP2026 post, and first useful web tip.
#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified -
@firefoxwebdevs I believe this would reach its full potential if supported and implemented also for headers in @mediawiki transcluded pages/templates, and in situations with no front-end JavaScript, for example when computing the heading level inside @11ty includes.
-
Last Wednesday, my fellow XPUB1 classmates and me wrapped up the trimester with a collective folding, binding, and paginating party to make A_Mazing Machine[s]: Wordscapes to Liberate Language, the printed publication of our Special Issue 28!
My first few months at @xpub have been incredible. I am so proud of my classmates, the work we did together, and what we learned. I am also very grateful to our tutors, who have been super kind and inspiring!
All information, plus a PDF of the printed version, made with WeasyPrint is available on this Eleventy website we created to share all the things that we explored. It mirrors our incredible, legendary wiki. It was very interesting and insightful, so I published my notes about Using MediaWiki as a CMS for Eleventy.
#WeasyPrint #WebToPrint #Web2print #SI28 #SpecialIssue28 #SpecialIssue #XPUB #ExperimentalPublishing #publishing #WritingMachines #Eleventy #builtWithEleventy #11ty #MediaWiki #wiki
-
@gunchleoc It is supported in #Unicode #CLDR and we use it in #MediaWiki. Look for "@decimal" in the code linked from https://translatewiki.net/wiki/Plural#Plural_in_MediaWiki
-
Nice #translatewiki.net meetup at #Wikimania. Some of us met for the first time despite translating together for over a decade. We also got half a dozen new translators for #Unicode #CLDR.
https://wikimania.wikimedia.org/wiki/2024:Meetups/translatewiki.net_and_MediaWiki_i18n -
Nächsten Samstag treffen sich die Menschen, die am Rhein-Neckar-Wiki mitmachen oder Interesse an dem Projekt haben. Du bist herzlich nach #Heidelberg eingeladen: https://rheinneckar.events/events/edf367c3-ab95-474e-a9a8-50538e18da12
#Wiki #Wikipedia #Mediawiki #Geschichte #Kultur #Lexikon #Wissen #Gestalten #Mitmachen #Entwickeln #Schreiben #Text #Foto #Photo #Fotografieren #RNWiki #RheinNeckar
-
Today, we want to point out three other very awesome webcomic wikis.
The official Pepper & Carrot Wiki
https://www.peppercarrot.com/en/wiki/Index.html
Maintained by P&C creator @[email protected]
Fellow @[email protected] wiki iToons Explained, helping to catelogue explanations for the Comic Irregulars' iToons series
https://itoonsexplained.miraheze.org/wiki/Main_Page
And last but certainly not least, Explain XKCD Wiki, providing high quality explanations to every page of Randall Monroe's XKCD!
https://www.explainxkcd.com/wiki/index.php/Main_Page
All three of these wikis are awesome and you should check them out.
#Webcomic #Webcomics #WebcomicWiki #ComicWiki #MediaWiki #Wiki #IndieWiki #WikisWorld #XKCD #ExplainXKCDWiki #Mezzacotta #ComicIrregulars #iToons #iToonsComic #iToonsExplained #iToonsWiki #PepperCarrot #PepperAndCarrot #PepperAndCarrotWiki -
Worse, this is a case of #YakShaving, I'm trying to fix an issue in the #Canasta #MediaWiki #CLI because I want to spin up an instance of #MediaWiki with #CirrusSearch quickly so I can edit the #UI for the #search interface. 😭 😂
And I'm attempting to use #JetBrains #GoLand which documents exclusions for #JS but not for #Go 🥴
-
Re-#introduction: recurring topics here.
#Wikimedia #Wikidata #Wikipedia #MediaWiki #OpenStreetMap #Wikimania #Wikisource #WikiCite #OpenRefine #wiki #Wiktionary #WikiLovesMonuments #Wikibase #Wikiquote
#i18n #L10n #translatewiki.net #Unicode #CLDR #languages
#Copyright #PublicDomain #PubblicoDominio #Copyleft #CreativeCommons #OpenData #UploadFilters #LicenzaLibera #DatiAperti
#InternetArchive #books #biblioteche #library #Koha #KohaILS #GLAM
#WikiTeam #digipres #ArchiveTeam #XSLT
1/4
-
More #i18n contributions always needed for #CLDR at #Wikimedia / #MediaWiki / #translatewiki.net. There's something for everybody: simple word-by-word translation, more complex localisation, coding, documentation.
https://translatewiki.net/w/i.php?title=CLDR&oldid=10577281
