Talk:Main Page: Difference between revisions

From Hackers Against Climate Change
Jump to navigation Jump to search
No edit summary
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:


== To Do ==
== Future? ==
<ul><li>Add a better editor for wiki pages</li>
=== General ===
<li>Transfer content from 35c3-wiki </li>
This Wiki was supposed to be migrated and moved, but due to a lack of effort (for various reasons), I, Peter did not make this happen.
<li>Transfer select content from the various pads over</li>
Because of this, the Wiki was down for a while earlier this year and has been and can be regarded as deprecated.
<li>Create Main Pages for different "working groups" and link them on the main page</li>
<li>Link to matrix/IRC-Channel if available</li>
</ul>
--[[User:Peter|Peter]] ([[User talk:Peter|talk]]) 19:48, 1 January 2019 (CET)


== Knowledge base "how to green a conference" ==
=== So what to with this? ===


<b>Collect valuable sources of knowledge and discuss it :)</b><br><br>
New solutions and old solutions for the problem this Wiki aimed to solve are both "pad" (web-based collaborative real-time editor) based, see
<li>one goal already reached in Leipzig: a sustainable caterer (improvements still needed) https://www.do-it-at-leipzig.de/de/Suche/Auszeichnung-fuer-nachhaltiges-Catering-fairgourmet-gewinnt-Meeting-Experts-Green-Award_1156.html?news1263.id=107&news1263.year=2017&news1263.month=2&strQuery=nachhaltig&jumpancor=news107</li>
 
<li>a "completely green event" by Deutsche Bundesstiftung Umwelt: https://www.nachhaltigkeitspreis.de/ueber-uns/green-event/</li>
* https://totalism.org/hacc and
<li>a little bit offtopic but maybe worth a read: https://www.bund-berlin.de/themen/klima-ressourcen/energie-klimaschutz/gesundheitswesen/</li>
* https://pad.hacc.space/index#
<br>
 
<b>we might need:<br></b>
=== Commitments ===
<li>a co2-calculator for congress related transports/storage, travel, accomodation + and something to compare it to other events <br>
 
https://media.ccc.de/v/34c3-8741-treibhausgasemissionen_einschatzen</li>
I commit to keeping this site runnning until at least three months after the next in-person CCC Congress or Camp best I can, which in all likelihood will be November 2023 (after CAMP).
<br>
 
<b>still unsorted links:</b>
PHP issues have been solved in the simplest way possible, via cronjob.
<br>
 
<li>https://media.ccc.de/v/34c3-9184-a_hacker_s_guide_to_climate_change_-_what_do_we_know_and_how_do_we_know_it/related</li>
Alternatives to make sure that no content get's lost would be to convert the contents of the Wiki (as is) to ZIM, as decribed here
<li>https://bits-und-baeume.org/de</li>
<li>https://nachhaltig.digital/</li>
* https://iamhow.com/Technical_Notes/Moving_off_MediaWiki_to_a_static_site.html
https://nachhaltig.digital/index.php?menuecms=2830&id=224
 
https://nachhaltig.digital/index.php?menuecms=2830&id=305
=== How can you help? ===
<br>
Please offer ideas, chime in, tell me what would work for you. The best way to do so is on this page.
<br>
Thank you!
<b>unsorted thoughts:<br></b>
 
<li>at 35c3 (partially already at 34c3) we had a local transportation ticket included and collectively financed :)</li>
[[User:Peter|Peter]] ([[User talk:Peter|talk]]) 19:32, 22 April 2021 (CEST)
<li>many things at congress are built with wood :)</li>
 
<li>we have an inhouse navigation tool and inhouse phone system (POC), reducing costs for international guests :)</li>
:Hello, Peter. What do you mean by "the PHP daemon ''died''"? Is this wiki is running on a Debian-based or Arch-based Linux OS? Those make it easier for servers running open-source software to stay running and up-to-date. If a service goes down, the admin could write a bash script that automatically restarts it. I'm guessing you know that already. Most wiki software including DokuWiki require PHP too.
<li>congress helpers often sleep at hostels or collective housing projects :)</li>
 
<li>we have "congress everywhere" :)</li>
:Three other bugs:
<li>we collectively re-use and repair old gadgets at congress - and we teach others how to do it (soldering!!) :)</li>
 
<li>our electronics gadgets are mainly made of plastic, have a short lifespan and use lots of power :(</li>
:# The filter form on [[Special:RecentChanges|RecentChanges]] doesn't load for me.
<li>is the energy source for heating and electricity at congress/camp/event sustainable? </li>
:# Neither does the filter form on page histories.
-> (Messe Leipzig?! http://www.leipziger-messe.de/unternehmen/nachhaltigkeit/)<br>
:# [[wikipedia:Wikipedia:Citing sources#Footnotes|Footnotes]] and [[wikipedia:Help:Footnotes#List-defined_references|list-defined references]] didn't work when I tried to use them for writing this comment.
-> sustainable fairground with tents https://www.dbu.de/phpTemplates/publikationen/pdf/1106120214467vbo.pdf<br>
 
<li>could we ask a bike sharing company to deliver ~100 bikes to the CAMP? this might reduce individual transportation costs and reduce loading space and coordination efforts. if the bikes can be used "30/60 minutes for free" or locally used via an untracked codelock app, we might just pay the bike rental a general fee for delivery&service</li>
:Etherpad, HedgeDoc, etc. are fine for ''temporary'' and ''personal'' markdown or text files, but they have much less control than wikis do against spam. While they do have a learning curve that stumps most bots, they have very limited or no support for access control, user authentication, content moderation, etc. Many wiki software do, including MediaWiki and DokuWiki via extensions. I can suggest some extensions later.
<br>
 
--[[User:Ralf|Ralf]] ([[User talk:Ralf|talk]]) 20:55, 02 February 2019 (CET)
:Markdown is convenient for simple, temporary text files, but it's cumbersome to read around inline formatting and links and scroll for footnotes. Tables in markdown are ugly and can't be sorted easily by column. Many different markdown standards exist that a given text file could use that editors would have to learn, and even people just reading are likely to have to learn what the formatting codes mean and would probably be frustrated reading all the codes sprinkled throughout the text. Etherpads make linking between pages a mess and searching a group of pages impossible.
 
:Wikis are the best tool for writing and archiving documentation, tutorials, or journals. Their best features are not just collaborative editing and revision control but ''linking'' documents, searching, managing them, and offering most of their tools through a very easy interface for new users. Links between pages are crucial for discovering and organizing information and building a web of knowledge. Consider your audience most of all.
 
:I have several years of experience editing different MediaWikis, DokuWikis, Trac wikis, and use Zim offline. I have a little bit of experience using git, and I strongly oppose requiring git if you want your readers to become editors. Its learning curve is extremely steep, and it and its tools are not designed for being used as a wiki.
 
:On Mastodon, you asked[https://chaos.social/@1peter10/106838969399250388] people to get in touch with you if they "know some wiki platform that... has tools to pull mediawiki content over". The keywords you want to search for are "import" or "export". But if you [[wikipedia:Comparison of wiki software|compare wiki software]] ([https://www.wikimatrix.org/]), you'll find that MediaWiki itself has the most tools for importing and exporting various formats, the most help documentation and tutorials, and has extensions that are more refined and actively developed than those of other wiki software.
 
:As climate activism is a worldwide movement, I believe it deserves an interlanguage wiki or family of language-based wikis or an embedded feature that can translate page content in any browser that supports JavaScript. MediaWiki has lots of experience, documentation, and extensions for interlanguage wikis. Besides this wiki, the only other wiki for climate activism that I know of is https://wiki.fridaysforfuture.is/, but it's only in the German language and intended for the German chapter of Fridays For Future.
 
:This wiki is self-hosted, but if admins would rather a third party hosts their wiki, here is a [[wikipedia:comparison of wiki hosting services|comparison of wiki hosting services]]. Miraheze looks like it would be the best of those for climate activists, but it blocks Tor.
 
:I hope this message reaches you because I decline to give my e-mail address to Matrix before it will allow me to connect to the channel, and I don't want a Mastodon account associated with my activity on this wiki. I use Tor Browser. That also gives me an unusual perspective about the design of access controls. Thank you for allowing me, a Tor user, to register here.
 
:'''Spam management and content moderation'''
 
:Delegate roles. Give [[wikipedia:Wikipedia:User access levels|Bureaucrat and Administrator rights]] ([https://www.mediawiki.org/wiki/Manual:User_rights]) (permission roles) to people you trust to review page revisions. Copy-paste or import or link to as many features, templates, guideline documents, or organizational policies as you want from Wikipedia and its trove of [[wikipedia:Help:Contents|help pages]] ([https://en.wikibooks.org/wiki/MediaWiki]) or from other wikis that use open licenses. If you need reliable helpers, advertise this wiki! Send direct toots to high-profile users of Mastodon instances for the climate justice movement. Here are a few instances for climate activism:[https://climatejustice.global/][https://climatejustice.social/][https://climatejustice.rocks/][https://social.rebellion.global/][https://sunbeam.city/]
 
:Block anonymous edits. (This wiki does.) Require a username to edit pages (this wiki does) unless your wiki has a large population of trusted, reliable, active editors who review revisions. On the registration page, make it optional to supply an e-mail address or social network account (this wiki does), but ''require'' completion of a non-Google (non-tracking) Captcha or TextCha and/or a hold of 12 to 48 hours denying permission of the new account to edit pages of the main namespace (as opposed to Talk pages or User pages). This is so that editing is allowed without an e-mail or social network account and that those wiki accounts will accumulate reputation so abusive accounts can be dealt with more effectively than if they were IP addresses, even by contributors who register through Tor. (This wiki uses a TextCha, but it asked me the same question twice.) Wikipedia implements similar restrictions on newly registered users until they are autoconfirmed.[https://en.wikipedia.org/wiki/Wikipedia:Why_create_an_account%3F][https://meta.wikimedia.org/wiki/Newly_registered_user] New accounts that remain inactive for, let's say, a week or two possibly could be automatically deleted or blocked.[https://en.wikipedia.org/wiki/Wikipedia:Delete_unused_username_after_90_days][https://en.wikipedia.org/wiki/Wikipedia:Username_policy#Deleting_and_merging_accounts]
 
:* [[mediawikiwiki:Extension:ConfirmEdit]]
::already active, using QuestyCaptcha. Sadly I have a hard time of thinking of dumb questions to ask.
:* [[mediawikiwiki:Manual:Combating spam]]
:* [[mediawikiwiki:Manual:$wgAutopromote]]
:* [[mediawikiwiki:Manual:Autoconfirmed users]]
:* [[mediawikiwiki:Help:User rights and groups#User_group_expiry]]
:* [https://www.phpcaptcha.org/ Securimage captcha]
:* Captcha chosen by Tor Project's BridgeDB,
:** Scroll to "Enabling CAPTCHA Support" in their README file somewhere around [https://gitweb.torproject.org/bridgedb.git/tree/README.rst#n212 line 212].
:** [https://github.com/isislovecruft/gimp-captcha gimp-captcha]
:* [[wikipedia:Wikipedia:CheckUser]]
:* [[wikipedia:Wikipedia:Recent changes patrol]]
:* [[mediawikiwiki:Manual:Preventing access]]
:* [[wikipedia:MediaWiki#Groups_and_restriction_of_access]]
 
:[[mediawikiwiki:Extension:AbuseFilter/Actions#Disallowing|Disallow (not block)]] the basic editor account group that has only basic permissions from committing extensive changes to a page [[wikipedia:Wikipedia:Added or removed characters|all at once in one revision]]. This is so people who review other people's edits will not face being flooded by combined changes lacking context for the smaller changes. In the world of git and databases, these concerns led software project managers and reference guides to recommend "atomic commits" although it may not have to be so extreme on a wiki. In Trac, a bug tracker and wiki system, the threshold to disallow a commit is rolled into a "karma" calculation[https://trac.edgewall.org/wiki/TracIni] for each commit to the wiki (called a "submission" in Trac's documentation). Also related is the derogatory usage of the term, "[[wikipedia:cowboy coding|cowboy coding]]".
 
:* [[mediawikiwiki:Extension:AbuseFilter]]
:* The "[[mediawikiwiki:Extension:AbuseFilter/Rules format#Variables_available_for_some_actions|edit_delta]]" variable
:* [[wikipedia:Wikipedia:Blocking policy]]
:* [[metawikimedia:Abuse_filter|AbuseFilter configurations]] in use by Wikimedia projects
 
:There are other MediaWiki tools for editors that make it easier to review and revert page edits, but they don't appear to be as urgently needed for this wiki as spam management tools are.
 
:By the way, remember to indent replies by prepending colons (:) to every line of text like I did in the wikitext markup of this comment. Multiple colons indents multiple tab-distances (:::::).
 
:--[[User:Cefra|Cefra]] ([[User talk:Cefra|talk]]) 19:30, 28 October 2021 (CEST)
 
::Thank you for your feedback! Sorry for not reacting for quite a long time, but motivation was at rock bottom and ... it wasn't exactly a short post, listing some things as measures to take that are (and were) already in place.
::I've finally deleted the spam accounts - tedious - and it does not really make me like MediaWiki more, it really feels like it's stuck in time and is very much it's own world. I hope to find the time to set up some other recommendations.
::Cheers,
::--[[User:Peter|Peter]] ([[User talk:Peter|talk]]) 12:41, 15 October 2022 (CEST)
 
== The focus of this wiki ==
 
Since anyone can register, what is the focus of this wiki? What topics are allowed? If people with the For Future Alliance[https://www.for-future-buendnis.de/], Extinction Rebellion[https://rebellion.global/], or Sunrise Movement[https://www.sunrisemovement.org/] came to this wiki, would you allow them to create pages for their needs too? I think they would gain a great amount of cooperative mutual aid from something more archival and concentrated than scattered pads, e-mail threads, chatrooms, and video meetings that are ephemeral and hard or impossible to search. --[[User:Cefra|Cefra]] ([[User talk:Cefra|talk]]) 20:16, 28 October 2021 (CEST)
 
: I tried to reword the Main Page to make clear that every group you listed is welcome. --[[User:Peter|Peter]] ([[User talk:Peter|talk]]) 13:37, 15 October 2022 (CEST)

Latest revision as of 19:36, 19 October 2022

Future?

General

This Wiki was supposed to be migrated and moved, but due to a lack of effort (for various reasons), I, Peter did not make this happen. Because of this, the Wiki was down for a while earlier this year and has been and can be regarded as deprecated.

So what to with this?

New solutions and old solutions for the problem this Wiki aimed to solve are both "pad" (web-based collaborative real-time editor) based, see

Commitments

I commit to keeping this site runnning until at least three months after the next in-person CCC Congress or Camp best I can, which in all likelihood will be November 2023 (after CAMP).

PHP issues have been solved in the simplest way possible, via cronjob.

Alternatives to make sure that no content get's lost would be to convert the contents of the Wiki (as is) to ZIM, as decribed here

How can you help?

Please offer ideas, chime in, tell me what would work for you. The best way to do so is on this page. Thank you!

Peter (talk) 19:32, 22 April 2021 (CEST)

Hello, Peter. What do you mean by "the PHP daemon died"? Is this wiki is running on a Debian-based or Arch-based Linux OS? Those make it easier for servers running open-source software to stay running and up-to-date. If a service goes down, the admin could write a bash script that automatically restarts it. I'm guessing you know that already. Most wiki software including DokuWiki require PHP too.
Three other bugs:
  1. The filter form on RecentChanges doesn't load for me.
  2. Neither does the filter form on page histories.
  3. Footnotes and list-defined references didn't work when I tried to use them for writing this comment.
Etherpad, HedgeDoc, etc. are fine for temporary and personal markdown or text files, but they have much less control than wikis do against spam. While they do have a learning curve that stumps most bots, they have very limited or no support for access control, user authentication, content moderation, etc. Many wiki software do, including MediaWiki and DokuWiki via extensions. I can suggest some extensions later.
Markdown is convenient for simple, temporary text files, but it's cumbersome to read around inline formatting and links and scroll for footnotes. Tables in markdown are ugly and can't be sorted easily by column. Many different markdown standards exist that a given text file could use that editors would have to learn, and even people just reading are likely to have to learn what the formatting codes mean and would probably be frustrated reading all the codes sprinkled throughout the text. Etherpads make linking between pages a mess and searching a group of pages impossible.
Wikis are the best tool for writing and archiving documentation, tutorials, or journals. Their best features are not just collaborative editing and revision control but linking documents, searching, managing them, and offering most of their tools through a very easy interface for new users. Links between pages are crucial for discovering and organizing information and building a web of knowledge. Consider your audience most of all.
I have several years of experience editing different MediaWikis, DokuWikis, Trac wikis, and use Zim offline. I have a little bit of experience using git, and I strongly oppose requiring git if you want your readers to become editors. Its learning curve is extremely steep, and it and its tools are not designed for being used as a wiki.
On Mastodon, you asked[1] people to get in touch with you if they "know some wiki platform that... has tools to pull mediawiki content over". The keywords you want to search for are "import" or "export". But if you compare wiki software ([2]), you'll find that MediaWiki itself has the most tools for importing and exporting various formats, the most help documentation and tutorials, and has extensions that are more refined and actively developed than those of other wiki software.
As climate activism is a worldwide movement, I believe it deserves an interlanguage wiki or family of language-based wikis or an embedded feature that can translate page content in any browser that supports JavaScript. MediaWiki has lots of experience, documentation, and extensions for interlanguage wikis. Besides this wiki, the only other wiki for climate activism that I know of is https://wiki.fridaysforfuture.is/, but it's only in the German language and intended for the German chapter of Fridays For Future.
This wiki is self-hosted, but if admins would rather a third party hosts their wiki, here is a comparison of wiki hosting services. Miraheze looks like it would be the best of those for climate activists, but it blocks Tor.
I hope this message reaches you because I decline to give my e-mail address to Matrix before it will allow me to connect to the channel, and I don't want a Mastodon account associated with my activity on this wiki. I use Tor Browser. That also gives me an unusual perspective about the design of access controls. Thank you for allowing me, a Tor user, to register here.
Spam management and content moderation
Delegate roles. Give Bureaucrat and Administrator rights ([3]) (permission roles) to people you trust to review page revisions. Copy-paste or import or link to as many features, templates, guideline documents, or organizational policies as you want from Wikipedia and its trove of help pages ([4]) or from other wikis that use open licenses. If you need reliable helpers, advertise this wiki! Send direct toots to high-profile users of Mastodon instances for the climate justice movement. Here are a few instances for climate activism:[5][6][7][8][9]
Block anonymous edits. (This wiki does.) Require a username to edit pages (this wiki does) unless your wiki has a large population of trusted, reliable, active editors who review revisions. On the registration page, make it optional to supply an e-mail address or social network account (this wiki does), but require completion of a non-Google (non-tracking) Captcha or TextCha and/or a hold of 12 to 48 hours denying permission of the new account to edit pages of the main namespace (as opposed to Talk pages or User pages). This is so that editing is allowed without an e-mail or social network account and that those wiki accounts will accumulate reputation so abusive accounts can be dealt with more effectively than if they were IP addresses, even by contributors who register through Tor. (This wiki uses a TextCha, but it asked me the same question twice.) Wikipedia implements similar restrictions on newly registered users until they are autoconfirmed.[10][11] New accounts that remain inactive for, let's say, a week or two possibly could be automatically deleted or blocked.[12][13]
already active, using QuestyCaptcha. Sadly I have a hard time of thinking of dumb questions to ask.
Disallow (not block) the basic editor account group that has only basic permissions from committing extensive changes to a page all at once in one revision. This is so people who review other people's edits will not face being flooded by combined changes lacking context for the smaller changes. In the world of git and databases, these concerns led software project managers and reference guides to recommend "atomic commits" although it may not have to be so extreme on a wiki. In Trac, a bug tracker and wiki system, the threshold to disallow a commit is rolled into a "karma" calculation[14] for each commit to the wiki (called a "submission" in Trac's documentation). Also related is the derogatory usage of the term, "cowboy coding".
There are other MediaWiki tools for editors that make it easier to review and revert page edits, but they don't appear to be as urgently needed for this wiki as spam management tools are.
By the way, remember to indent replies by prepending colons (:) to every line of text like I did in the wikitext markup of this comment. Multiple colons indents multiple tab-distances (:::::).
--Cefra (talk) 19:30, 28 October 2021 (CEST)
Thank you for your feedback! Sorry for not reacting for quite a long time, but motivation was at rock bottom and ... it wasn't exactly a short post, listing some things as measures to take that are (and were) already in place.
I've finally deleted the spam accounts - tedious - and it does not really make me like MediaWiki more, it really feels like it's stuck in time and is very much it's own world. I hope to find the time to set up some other recommendations.
Cheers,
--Peter (talk) 12:41, 15 October 2022 (CEST)

The focus of this wiki

Since anyone can register, what is the focus of this wiki? What topics are allowed? If people with the For Future Alliance[15], Extinction Rebellion[16], or Sunrise Movement[17] came to this wiki, would you allow them to create pages for their needs too? I think they would gain a great amount of cooperative mutual aid from something more archival and concentrated than scattered pads, e-mail threads, chatrooms, and video meetings that are ephemeral and hard or impossible to search. --Cefra (talk) 20:16, 28 October 2021 (CEST)

I tried to reword the Main Page to make clear that every group you listed is welcome. --Peter (talk) 13:37, 15 October 2022 (CEST)