Today, I am announcing plans for the biggest change to Pandora's Tale Wiki since its founding: I am going to port the wiki away from MediaWiki and convert it to a git repository of text files. This conversion process may not be easy, but it is necessary. If we continue down the current path, I am going to burn out and will not be able to continue maintaining the wiki. I have described the reasons for the change in the article for Project: Texts About Pandora
https://pandorastale.wiki/wiki/Pandora%27s_Tale_Wiki:Texts_About_Pandora#Hosting_availability
(Yes, the name of the article is a pun on the pages "Texts from Pandora" and "Texts from Pandora 2".)
https://comicsbyxan.com/comic/texts-from-pandora/
https://comicsbyxan.com/comic/texts-from-pandora-2/
There are still some things I need to determine.
1) First and most significantly, I have to figure out how to convert a MediaWiki instance into a git repository. I've found several scripts which claim to do it, but they all seem to have significant drawbacks in addition to being unmaintained. I would greatly appreciate advice from computer creatures in this regard.
2) Then I have to decide on the text format: Plaintext, gemtext, or markdown? There are ups and downs to each of them, though I'm not as worried since I believe it might be possible to convert between them later.
3) Finally I have to decide on the hosting software and platform if I want anyone else to be able to read it. Gitlab, Forgejo, sourcehut, or something else?
Once I answer these questions, I am going to move Pandora's Tale Wiki to a git repository, and then I will ask Miraheze to shut down their copy of the wiki. I don't know how long this process will take, but I believe it's the only way I can continue the wiki.
#PandorasTale #PandorasTaleWiki #ComicsByXan #Webcomics #Homestuck #MSPaintAdventures #Miraheze #Wiki #Wikis #WebcomicWiki #MediaWiki #Git #PlainText #GemText #GeminiProtocol #Markdown #MD #SourceHut #srht #Forgejo #Gitlab
Recent searches
Search options
Administered by:
#srht
I understand that #nix fetchers "set a dangerous precedent" and this is why, say, #srht fetcher or other fetchers won't ever be accepted and #github shall have that socially privileged status...
But I also want to confess that the existence of fetchers make me so happy.
I really don't mind hosting or mirroring my stuff on #github because I don't have the time to pick _alll_ the battles.
Anyone else publishing Markdown -> Static Site Generator here?
Logseq -> Sourcehut is my setup and I'll be making it sing over the next month.
Curious about what y'all are working with :)
Oh, look, that's so cute, draft commits have a little "under construction" colouring in #Mercurial when using #SrHt/#Sourcehut.
Can your git do THIS?
I keep forgetting that #SourceHut #SrHt is a fully-featured #Mercurial host. It even lets you set publishing on or off!
Drew explicitly doesn't mention his own project/company, so I will:
https://sourcehut.org/
For $20 a YEAR, you can be an 'Amateur Hacker' level supporter of his FULLY FLOSS platform.
If you believe in 'voting with your wallet', that's an excellent way to support and promote FLOSS alternatives.
There are also other plans for $50 or $100 although it currently doesn't provide extra features.
See https://sourcehut.org/pricing/ for details