-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kill the Wiki? #238
Comments
I can see a mild use of the Wiki for the hackathon, but that's about it. Archiving it or making it read-only would not solve the issue of people finding it and looking up outdated information. If we are to keep it then I would make it private. |
Hence the banner I mentioned first. Not sure what private entails in practice but if no content is available, it will push users towards the indexed/InternetArchive versions which wont have the banner. |
Nobody reads banners https://en.wikipedia.org/wiki/Banner_blindness I don't see user going to the internet archive when there's other, fresh content available elsewhere. |
Do you understand the use case I'm writing about? Say User looks for “Kiwix Hotspot” in Google. There's a link to that Wiki page because it was relevant at some point. User clicks but it doesn't work because it's private (credentials prompt?). User would hit Back and use the search engine feature to access the archived version. I suggested that we keep the URL working and there present information mentioning it's gone. Whether people read it or not, we have the responsibility to write that content we keep online is outdated ; otherwise we mislead them on purpose. |
The Kiwix Wiki is full of outdated content. When it's not incorrect, it's usually incomplete or present information that is available elsewhere.
The main issue is that there is no warning that the Wiki has been abandoned for years and does not represent a reliable source of information.
It think the very minimum we should do is add a banner informing users that this is mostly obsolete.
Beside this, we should discuss:
The text was updated successfully, but these errors were encountered: