Difference between revisions of "Wishlist"
m (→Related) |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
| + | |||
| + | * Somewhen migrate to something that <br>(1) allows direct in context feedback (reviewable and spam safe) <br>(2) can be hosted in a federated fashion | ||
| + | ----- | ||
| + | * '''Add the hovercard plugin!!''' | ||
* how to autocollect all the ['''todo:'''...] notes on one page - convert them to templates ...? | * how to autocollect all the ['''todo:'''...] notes on one page - convert them to templates ...? | ||
* where to best host all the special filetypes *.svg *.graphml *.scad <br> wikiwebspace (limited space) / dropbox (good backup but no informative write protection possible) / .. ? | * where to best host all the special filetypes *.svg *.graphml *.scad <br> wikiwebspace (limited space) / dropbox (good backup but no informative write protection possible) / .. ? | ||
| Line 9: | Line 13: | ||
* remove the spambot user corpses - see: [[Special:ListUsers]]- maybe usable: https://www.mediawiki.org/wiki/Extension:UserMerge | * remove the spambot user corpses - see: [[Special:ListUsers]]- maybe usable: https://www.mediawiki.org/wiki/Extension:UserMerge | ||
* easier upload of image files - at best direct sketching in the wiki (hand or svg) | * easier upload of image files - at best direct sketching in the wiki (hand or svg) | ||
| + | ---- | ||
| + | * Some method to visualize the link topology of this mediawiki !! | ||
| + | * Edit date histograms | ||
| + | |||
| + | == Maybe easy == | ||
| + | |||
| + | * In context graphical preview needed (actually a general issue in the www - state 2017).<br>{{wikitodo|Add mediawiki plugin hovercards: https://www.mediawiki.org/wiki/Beta_Features/Hovercards}} | ||
| + | |||
| + | == Eventually desired pages == | ||
| + | |||
| + | * [[The inner life of the cell]] | ||
| + | * [[How natures nanotech compares to gem-gum tech]] | ||
| + | * [[The various kinds of nanotech]] | ||
| + | |||
| + | == Wiki migration?? == | ||
| + | |||
| + | === "Static site" hosting? Not yet :( === | ||
| + | |||
| + | It would be great if this wiki could be migrated to next gen internet hosting. <br> | ||
| + | That is as a so called "static site" that can be hosted decentralize like e.g. on IPFS. <br> | ||
| + | Note: Confusingly "Static site" does not mean that the site is static in the sense of non-interactive. | ||
| + | |||
| + | Advantages would include (among other things): | ||
| + | * Easier to make backups. Both for myself and for other who may want to help in preservation of fork ... | ||
| + | * Resilience to sudden spikes in demand (or DDOS attacks; had experienced had one!!) <br>without the need for turning to something like cloudflare. | ||
| + | |||
| + | '''Obstacle:''' | ||
| + | Unfortunately as this wiki is based on MediaWiki running it as a "static site" is not possible (as of 2022). <br> | ||
| + | <small>Wikipedia faces the exact same problem. Thus still only non-editable backup surface copies can reside on IPFS.</small><br> | ||
| + | The problem is mostly that MediaWiki depends on a big fat monolithoic (mySQL type) database that typically is stored in an area of a webhosters servers file system where the client has no direct access rights to the file system (to check). And more importantly access to that database is processes on the servers CPU. Such things cannot be done on IPFS & co. | ||
| + | |||
| + | Fleek seems like a very nice "static site" hosting option for hosting on IPFS. <br> | ||
| + | As it can "deploy" a static site from github to IPFS (up to 3GB for free as of 2022). <br> | ||
| + | ... | ||
| + | |||
| + | === Other wiki software suitable for "static site" hosting? === | ||
| + | |||
| + | There are some kinds of wiki software that: | ||
| + | * are open source and | ||
| + | * can generate a static site. | ||
| + | But there are too many issues. | ||
| + | |||
| + | Static site generation is possible but it is done in a batch processing way with no memory of the last export <br> | ||
| + | exporting just the edited page after every single edit would need some seriously nontrivial scripting/programming … <br> | ||
| + | |||
| + | Unlike mediawiki zimwiki has no per page integrated edit histories (BAD!) <br> | ||
| + | The alternative of git commit histories are a bad insufficient replacement | ||
| + | |||
| + | Here is a guide how to export mediawiki to zimwiki: | ||
| + | [https://iamhow.com/Technical_Notes/Moving_off_MediaWiki_to_a_static_site.html (guide)] <br> | ||
| + | But due to what is lost this will not be pursued for the foreseeable future. | ||
| + | |||
| + | === Get a better domain name? === | ||
| + | |||
| + | CONs: | ||
| + | * cost – there are pretty much no useful gratis options | ||
| + | * cost – free plan no support for https | ||
| + | * A domain name as additional indirection can be an additional point fragility as it froms a longer serial chain of links.<br> This argument can be turned around though as a domain name as indirection can help in case of loss of hosting service. | ||
| + | PROs: | ||
| + | * Short memorable url can have massive impact form marketing ... | ||
| + | |||
| + | '''Bockchain recorded domain names as an option:''' | ||
| + | * '''ENS:''' Needs regular renewal fees and with rising transaction costs this seems unsustainable (at least for now) | ||
| + | * '''Unstoppable Domains:''' Done: Got some relevant one time payment lifetime possession domains. | ||
| + | Linking these new kind of domain names does not work too well as of yet though (2021 checked). | ||
| + | |||
| + | IPFS alone is content addressed thus <br> | ||
| + | IPFS addresses cannot be directly mapped a domain name as <br> | ||
| + | any changes of content will change the IPFS address and make the domain name still link to the old outdated content. <br> | ||
| + | There is IPNS to solve (hack around) this problem. But I had not much success trying this (back in 2021). <br> | ||
| + | IIRC there is a way to set some IPNS stuff for free, but this gets autoremoved after just a few hours. | ||
| + | |||
| + | == Solutions == | ||
| + | |||
| + | * To use pinterest for advertisement (pinterest allows no svg-files 2016) upload rasterized image versions to flickr link from there to this wiki here and pin rasterized images from there. | ||
| + | |||
| + | == Logo issues == | ||
| + | |||
| + | https://www.mediawiki.org/wiki/Manual:$wgLogo <br> | ||
| + | https://www.mediawiki.org/wiki/Manual_talk:$wgLogo <br> | ||
| + | Official guide does not work. Even going back to original settings. | ||
| + | |||
| + | Related: | ||
| + | * [[Wiki setup notes]] | ||
| + | * [[MediaWiki:Common.css]] | ||
== Related == | == Related == | ||
* [[Wiki setup notes]] | * [[Wiki setup notes]] | ||
| + | * [[Meta pages]] | ||
| + | * [[Support]] | ||
Latest revision as of 09:28, 3 June 2023
- Somewhen migrate to something that
(1) allows direct in context feedback (reviewable and spam safe)
(2) can be hosted in a federated fashion
- Add the hovercard plugin!!
- how to autocollect all the [todo:...] notes on one page - convert them to templates ...?
- where to best host all the special filetypes *.svg *.graphml *.scad
wikiwebspace (limited space) / dropbox (good backup but no informative write protection possible) / .. ? - todo: remove spam user corpses for good
- scaling images to page-width
- good solution for dual language wiki
- resolve bug that the wiki logo isn't showing up
- life visualization of this wiki as a directed graph (arrows between clickable circles) - a locally searching crawler is necessary
[todo: search for existing plugins for wiki graph visualization - again] - remove the spambot user corpses - see: Special:ListUsers- maybe usable: https://www.mediawiki.org/wiki/Extension:UserMerge
- easier upload of image files - at best direct sketching in the wiki (hand or svg)
- Some method to visualize the link topology of this mediawiki !!
- Edit date histograms
Contents
Maybe easy
- In context graphical preview needed (actually a general issue in the www - state 2017).
(wiki-TODO: Add mediawiki plugin hovercards: https://www.mediawiki.org/wiki/Beta_Features/Hovercards)
Eventually desired pages
- The inner life of the cell
- How natures nanotech compares to gem-gum tech
- The various kinds of nanotech
Wiki migration??
"Static site" hosting? Not yet :(
It would be great if this wiki could be migrated to next gen internet hosting.
That is as a so called "static site" that can be hosted decentralize like e.g. on IPFS.
Note: Confusingly "Static site" does not mean that the site is static in the sense of non-interactive.
Advantages would include (among other things):
- Easier to make backups. Both for myself and for other who may want to help in preservation of fork ...
- Resilience to sudden spikes in demand (or DDOS attacks; had experienced had one!!)
without the need for turning to something like cloudflare.
Obstacle:
Unfortunately as this wiki is based on MediaWiki running it as a "static site" is not possible (as of 2022).
Wikipedia faces the exact same problem. Thus still only non-editable backup surface copies can reside on IPFS.
The problem is mostly that MediaWiki depends on a big fat monolithoic (mySQL type) database that typically is stored in an area of a webhosters servers file system where the client has no direct access rights to the file system (to check). And more importantly access to that database is processes on the servers CPU. Such things cannot be done on IPFS & co.
Fleek seems like a very nice "static site" hosting option for hosting on IPFS.
As it can "deploy" a static site from github to IPFS (up to 3GB for free as of 2022).
...
Other wiki software suitable for "static site" hosting?
There are some kinds of wiki software that:
- are open source and
- can generate a static site.
But there are too many issues.
Static site generation is possible but it is done in a batch processing way with no memory of the last export
exporting just the edited page after every single edit would need some seriously nontrivial scripting/programming …
Unlike mediawiki zimwiki has no per page integrated edit histories (BAD!)
The alternative of git commit histories are a bad insufficient replacement
Here is a guide how to export mediawiki to zimwiki:
(guide)
But due to what is lost this will not be pursued for the foreseeable future.
Get a better domain name?
CONs:
- cost – there are pretty much no useful gratis options
- cost – free plan no support for https
- A domain name as additional indirection can be an additional point fragility as it froms a longer serial chain of links.
This argument can be turned around though as a domain name as indirection can help in case of loss of hosting service.
PROs:
- Short memorable url can have massive impact form marketing ...
Bockchain recorded domain names as an option:
- ENS: Needs regular renewal fees and with rising transaction costs this seems unsustainable (at least for now)
- Unstoppable Domains: Done: Got some relevant one time payment lifetime possession domains.
Linking these new kind of domain names does not work too well as of yet though (2021 checked).
IPFS alone is content addressed thus
IPFS addresses cannot be directly mapped a domain name as
any changes of content will change the IPFS address and make the domain name still link to the old outdated content.
There is IPNS to solve (hack around) this problem. But I had not much success trying this (back in 2021).
IIRC there is a way to set some IPNS stuff for free, but this gets autoremoved after just a few hours.
Solutions
- To use pinterest for advertisement (pinterest allows no svg-files 2016) upload rasterized image versions to flickr link from there to this wiki here and pin rasterized images from there.
Logo issues
https://www.mediawiki.org/wiki/Manual:$wgLogo
https://www.mediawiki.org/wiki/Manual_talk:$wgLogo
Official guide does not work. Even going back to original settings.
Related:
