Difference between revisions of "Main Page"

From The Hive
(→‎more language codes: wikilink to new page)
(pgp)
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== Welcome to The Hive ==
 
== Welcome to The Hive ==
  
The Hive https://www.colmena.biz is now secured with a [https://certbot.eff.org/ Certbot] certificate from [https://letsencrypt.org/ Let's Encrypt].
 
  
* [[User:Justina]]
+
 
 +
The Hive https://www.colmena.biz is now secured with a [https://certbot.eff.org/ Certbot] certificate from [https://letsencrypt.org/ Let's Encrypt] and the [https://shorewall.org/ Shorewall] configuration utility for [https://www.netfilter.org/ iptables].
 +
 
 +
Further ideas for enhancing security on the internet are [[SPF+DKIM+DMARC]] for email and [[X.509+DNSSEC+DANE+CAA‎]] for general domain security.
 +
 
 +
* [[User:Justina]] (pgp keys etc.)
  
 
Don't forget to visit our blog [https://www.mushroom.global Mushroom.Global].
 
Don't forget to visit our blog [https://www.mushroom.global Mushroom.Global].
Line 11: Line 15:
 
Change URL structure:
 
Change URL structure:
  
* https://www.colmena.biz/en/index.php/Main_Page
+
* https://www.colmena.biz/html/en/Main_Page
* https://www.colmena.biz/es/index.php/Página_principal
+
* https://www.colmena.biz/html/es/Página_principal
 
* etc.
 
* etc.
  
Directories "en" and "es" etc. can each be created on the web server with separate LocalSettings.php but the other files all symlinked from the base of a common wiki installation. There will be separate databases, or at least separate tables in the same database. Why not?
+
Directories "en" and "es" etc. can each be created on the web server with separate LocalSettings.php but the other files all symlinked from the base of a common wiki installation.
 +
 
 +
Probably not symlinks. I'm thinking that the whole directory structure needs to be replicated, with hard links for the files.
  
 
Needs more experimentation ...
 
Needs more experimentation ...
  
This is not a HOWTO. Do not try this at home.
+
:$IP = Intellectual Property ... no skins installed ... 500 error. Something's off.
  
The "index.php" part need not matter so much. It's Latin and the reader is "looking something up."
+
::No, the problem is all that "absolute path" stuff ("__DIR__" etc.) in the php programs for MediaWiki, due to "highly secure coding practices" as mandated by non-profit foundation management. Some of those restrictions are beneficial and well-meant of course: your MediaWiki installation is less likely to get hacked, as some vandals on Wikipedia in the early days did roo the database through obscure SQL injections and other CVE-type vulnerabilities, but some of this stuff is too bureaucratic, and not as flexible for end use installation as it could be. PHP itself has a questionable reputation for security: a lot of it is little more than thin wrappers over C code, and like C it depends on secure coding practices. Still up for public domain scratch space.
  
==== [[Alaska Native language codes]] ====
+
# This is the [https://www.mediawiki.org/wiki/Manual:Wiki_family#Multiple_wikis_sharing_common_resources family of wikis] approach, which is probably the best.
 +
# There is also a [https://www.mediawiki.org/wiki/Extension:Translate Translate] extension that provides multilingual support in one wiki, which seems useful as a bridge to full support for a new wiki language.
  
https://www.loc.gov/standards/iso639-2/php/English_list.php
+
This is not a HOWTO. Do not try this at home. Refer to [https://www.mediawiki.org/wiki/Manual:Short_URL official sources] for instructions. Caveat: that is a wiki, too, and those are not precise instructions either, but general ideas with advantages and disadvantages.
 
 
* ale = "Aleut"
 
* ath = "Athapascan languages"
 
* hai = "Haida"
 
* iku = "Inuktitut"
 
* ipk = "Inupiaq"
 
* tli = "Tlingit"
 
* ypk = "Yupik languages"
 
 
 
Three-letter codes after the NWO elitists ran out of two-letter codes.
 
 
 
==== Sami (Northern Europe) ====
 
 
 
* smi = "Sami languages"
 
* smn = "Inari Sami"
 
* smj = "Lule Sami"
 
* sme = "Northern Sami"
 
* sms = "Skolt Sami"
 
* sma = "Southern Sami"
 
  
 
=== Getting started ===
 
=== Getting started ===
Line 55: Line 43:
 
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
 
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
 
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]
 
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]
 +
 +
[[es:Página principal]]

Latest revision as of 02:26, 27 February 2020

Welcome to The Hive

The Hive https://www.colmena.biz is now secured with a Certbot certificate from Let's Encrypt and the Shorewall configuration utility for iptables.

Further ideas for enhancing security on the internet are SPF+DKIM+DMARC for email and X.509+DNSSEC+DANE+CAA‎ for general domain security.

Don't forget to visit our blog Mushroom.Global.

To Do

Change URL structure:

Directories "en" and "es" etc. can each be created on the web server with separate LocalSettings.php but the other files all symlinked from the base of a common wiki installation.

Probably not symlinks. I'm thinking that the whole directory structure needs to be replicated, with hard links for the files.

Needs more experimentation ...

$IP = Intellectual Property ... no skins installed ... 500 error. Something's off.
No, the problem is all that "absolute path" stuff ("__DIR__" etc.) in the php programs for MediaWiki, due to "highly secure coding practices" as mandated by non-profit foundation management. Some of those restrictions are beneficial and well-meant of course: your MediaWiki installation is less likely to get hacked, as some vandals on Wikipedia in the early days did roo the database through obscure SQL injections and other CVE-type vulnerabilities, but some of this stuff is too bureaucratic, and not as flexible for end use installation as it could be. PHP itself has a questionable reputation for security: a lot of it is little more than thin wrappers over C code, and like C it depends on secure coding practices. Still up for public domain scratch space.
  1. This is the family of wikis approach, which is probably the best.
  2. There is also a Translate extension that provides multilingual support in one wiki, which seems useful as a bridge to full support for a new wiki language.

This is not a HOWTO. Do not try this at home. Refer to official sources for instructions. Caveat: that is a wiki, too, and those are not precise instructions either, but general ideas with advantages and disadvantages.

Getting started

Consult the User's Guide for information on using the wiki software.