metastem / wikiless Goto Github PK

On most instances hitting the edit button leads to a ban info page, which may initially throw some users into confusion. I understand that hiding the edition capabilities completely is not that much of a good idea either, as not every instance is banned.

One solution I can think of is to make the server check for a ban status once, possibly also scraping the ban expiration date, then save that in a file or other form of a metadata it could announce to federated servers* to find those which are not banned, then redirect the user (with a confirmation page, of course). As a result the users willing to make edits to articles censored in their countries can still do that without manually trying to find an instance which does not ban edits.

* e.g. using ActivityPub

Hello
I know wiki.metastem.su is using minimalpedia skin, but can somebody describe how I can use this skin with wikiless on my own instance?
I am using docker btw.

Is it possible for Wikiless to have a more rich table layout similar the one found in Wikipedia.org?
As you can see table columns are sortable and colorized. Which really helps navigating tables with large amounts of data or when you wish to find rows with certain criteria. As you can see in my example when i sorted in favor of free software

Wikiless tables are certainly usable (especially with the added benefit of dark mode) but are quite less productive to use.

zh.wikipedia.org provides multiple versions using different writing systems, among others:

1. Chinese written in simplified letters, commonly used in mainland China
2. Chinese written in traditional letters, commonly used in Taiwan

Conceptually the two are like en-US vs. en-GB but the difference is more radical, as every "alphabet" (letter, "glyph") used to write words are different-shaped, only vaguely similar.

On WP the user may select their familiar flavor of Chinese via 不转换 menu. For example, if you open...
https://zh.wikipedia.org/wiki/%E9%97%A8%E7%BD%97%E5%B8%81
...and then select 臺灣正體, then you'll get
https://zh.wikipedia.org/zh-tw/%E9%97%A8%E7%BD%97%E5%B8%81
which is written in Chinese with the traditional writing system, using the Taiwanese orthography.

Though WP has more Chinese options than the above two, practically it is roughly sufficient if zh-CN & zh-TW are supported (or technically: zh-Hans & zh-Hant). If necessary, educated Chinese speakers can read both, but the two are so different that e.g. for a Taiwanese person, reading a long zh-CN text can be painful, and vice versa.

So It would seem ideal if Wikiless too somehow supports the selection between lang=zh-tw and lang=zh-cn, especially considering that many of the users who might be greatly helped by Wikiless are (or will be) Chinese people behind the Great Firewall (i.e. those who may not be able to read the regular Wikipedia articles freely).

Projects similar to Wikiless (Invidious, Piped, Nitter, BreezeWiki) often feature a handy link to the original link. This is handy not just for sharing the link on social media, but also bookmarking and redirecting in the event of a single instance failing.

Based on both the classic Wikiless design, and the redesign(?) found at wiki.metastem.su, somewhere on the top would be an ideal location for the link.

Side Tangent, I love the redesign at wiki.metastem.su. I think it could still use some work, but I actually prefer it over both classic Wikiless and the current Wikipedia design.

PS: In general I really like the design of BreezeWiki if you wanted some additional inspiration.

resulting in the wikiless layout looking kinda wonky

self-explanatory, no beef against froth.zone tho (i'm sure he's a swell fellow)

On wiki pages, the Navigation menu that should be on the side of the screen is located at the bottom instead.
At first i thought making the navigation menu disappear was a educated decision, but apparently it's not !

This was experienced on the wl.vern.cc.

From mail contact with lawyers from the Wikimedia Foundation, I know that this project is being investigated by them for trademark infringement.

I am not exactly sure what parts are an infringement, but I am pretty sure that using the Wikipedia jigsaw globe logo is an issue. Maybe some links should also be replaced. I'd like to encourage the legal team to specify what parts are problematic so we can fix this issue, before this repository is taken down like the original.

$ npm start

> [email protected] start
> node src/wikiless.js

/home/node/wikiless/src/utils.js:7
  const got = require('got')
              ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /home/node/wikiless/node_modules/got/dist/source/index.js from /home/node/wikiless/src/utils.js not supported.
Instead change the require of index.js in /home/node/wikiless/src/utils.js to a dynamic import() which is available in all CommonJS modules.
    at module.exports (/home/node/wikiless/src/utils.js:7:15)
    at Object.<anonymous> (/home/node/wikiless/src/wikiless.js:28:36) {
  code: 'ERR_REQUIRE_ESM'
}

Node.js v18.17.0

Also, I manually added the entries for express-session and lusca in package.json because otherwise they won't install with npm install

topic

EDIT: this is a bigger issue than i thought, as it doesn't only concern pages generated from search results, but all french wiki pages. i edited this issue to reflect my findings.

Many Wikipedia pages from the french Wikipedia have a broken layout.
Here are some examples i found:

Pages from search results

I use the Wikipedia search engine to search for terms directly in my web-browser (Firefox).

In my example, i'll consistently use wl.vern.cc as my instance, and the term bouvier for my search on the french wiki pages.

If the term i'm searching for directly links to an existing page, that page will have its layout broken, like shown below. In my example, the page link is the following: https://wl.vern.cc/wiki/Sp%C3%A9cial:Recherche?search=bouvier&sourceid=Mozilla-search&lang=fr

But if i access the same page from somewhere else on the instance, as you can see below, the page looks like normal. The link to this page is different: https://wl.vern.cc/wiki/Bouvier?lang=fr

Maybe wikiless can convert the search link to a regular link instead. I don't think the info passed down through the search result link is important to wikiless or the instance through which it passes.

Navigation menu

copied from #86

On wiki pages, the Navigation menu that should be on the side of the screen is located at the bottom instead.
At first i thought making the navigation menu disappear was a educated decision, but apparently it's not !

This was experienced on the wl.vern.cc instance.

Other stuff probably ?

These are some observations i could make, but i guess more layout problems might exist. It might be worth checking other languages to see if their pages are broken too.

If accounting for any other languages than english is too hard, maybe then display a warning message explaining wikiless doesn't currently fully support pages for languages other than english, with an option to redirect to the official Wikipedia page, or the equivalent english page on Wikiless.

I've been testing out using minerva skin for mobile user agents. I got it working but the CSS is broken, even if I make it load the minerva CSS scraped from Wikipedia, SVG's doesn't load . Also dark mode wouldn't work since there is no stylesheet for mobile.

Esmail is actively forbidding members or supporters of the LGBTQIA+ community to use their services via a TOS document*.
This is absolutely queerphobic and extremely discriminating. Therefore I ask to remove their instance wikiless.esmailelbob.xyz / wikiless.esmail5pdn24shtvieloeedh7ehz3nrwcdivnfhfcedl7gf4kwddhkqd.onion from the list, to not further support their actions.

*See the commit here: EsmailELBoBDev2/upptime@c46b9bf

Hi,
Can you please add my instance to the list?

URL: https://wikiless.rafo.tech
CDN: Cloudflare
Anti bot protection: Yes

It's disturbing that the official instance https://wikiless.whateveritworks.org/ is blocking Tor. Such a privacy-unfriendly, Tor-censoring instance should be clearly marked as scuh, as Tor users assume that privacy-friendly services are almost always Tor-friendly, and as such, when you block Tor, you'll potentially lose credibility. If warned in advance (that Tor is not supported on that instance), this rude shock would be somewhat mitigated, even though privacy-oriented users might prefer another option (e.g. metager), once they realize wikiless is not really serious - not trying to help Tor users (some of whom can view the Internet freely only thanks to Tor, Snowflakes etc).

It seems that the search function is broken in the non-English wikiless pages. When I try to search on the Dutch page, I get redirected to the English main page. (So not even to the Search Results special page, but the ‘Front page/Main Page’

Some image pages do not resolve and end up with an INVALID_HTML error.

Here are some examples.
https://wikiless.whateveritworks.org/wiki/File:Processing_Chips.JPG?lang=en
https://wikiless.whateveritworks.org/wiki/File:Apple_M1.jpg?lang=en

It supposed to work like the below links.
https://wikiless.whateveritworks.org/wiki/File:Caller_ID_receiver.jpg?lang=en
https://wikiless.whateveritworks.org/wiki/File:Nokia-9110-4.jpg?lang=en

This is the case with all current Wikiless instances including the official instance.

Hi, after latest update. My instance keep running for a while then errors out with "SERVER_ERROR_REDIS_SET"

PS: I use docker

For example, clicking on the Wikiless logo directs me to https://wikiless.lunar.icu/Main_Page?lang=en, which shows Cannot GET /Main_Page. The correct url should be https://wikiless.lunar.icu/wiki/Main_Page?lang=en. The /wiki/ is missing in all wiki links except for switching languages.

Using instance https://wikiless.lunar.icu/.

It is going offline soon.

Instance: wiki.seitan-ayoub.lol
Location: Germany
Cloudflare: no

Hello, reopening that issue (sorry for responding too late on the previous one)

as seen on https://wikiless.datura.network/ i get the error "invalid lang" even though i put 'en' as the language.

current files:

-docker-compose.yml: https://privatebin.nihilism.network/?de4d85add74740d3#H6jW6hVncNEjHSwXVjkQUt3H6cuWdrsjmwgBszoZT446

-wikiless.config: https://privatebin.nihilism.network/?9d16b41b278d2416#Bu77KAgyrcUjGcGAtDXavZT8pReDNFN3GZD79A5kjVtQ

(new since last issue: removed the onion headers)-nginx reverse proxy site config: https://privatebin.nihilism.network/?ddf8831f6377d299#4xr3k2DKxtT4EeWMw9Awiac3sKpNQJVEC164awA3dBQn

(new since last issue): testing the webserver without going through the nginx reverse proxy: https://privatebin.nihilism.network/?a023c303685ab320#BGTafV1wR4R5Mdyp529doPkKKUGXU9GX6K2ECQx9LN3P

not sure that it would be the reverse nginx proxy being the issue since when testing directly without going through nginx i still get the invalid lang error.

What are the valid values for the lang parameter in the wikiless.config file ?

also letting you know where are each file: https://privatebin.nihilism.network/?0f2a9debc6015e79#47412nt3Vfvi8cKjtHdVGdysZLdNMZgF6ZcR43BpkMzh

I am trying to host a public instance for wikiless, however for each link that I click it returns CANNOT GET <topic> . I have tried redirecting https://wiki.example.com to https://wiki.example.com/ using NGINX but then nothing seems to function properly. NGINX serves the instance as it supposed to but links and other CSS elements don't load. Any idea how to fix this?

I run an instance at https://wikiless.r4fo.com and now also at http://wikiless.r4focoma7gu2zdwwcjjad47ysxt634lg73sxmdbkdozanwqslho5ohyd.onion.

For privacy improvements, I have disabled Cloudflare proxying. Can you please edit the list?

My instance was running for a while, but then suddenly stopped working and I couldn't get it to restart. Decided to reclone the repo and prune the old images and build again, but I'm having some trouble.
Here's what I did:
1: Clone the repo with git clone https://github.com/Metastem/wikiless
2: Edit docker-compose.yml, commenting out image: wikiless:latest and uncommenting out build ., setting version to 3.3 and setting a different port for wikiless: networks: ports, as well as setting the port in wikiless.config.
3: Run docker-compose build, and then docker-compose up -d.

This makes two containers for me: wikiless_wikiless_1 and wikiless_wikiless_redis_1. The redis one is reported as running fine, but the first one is stuck on restarting.

I'm not very good with docker so I'm probably missing something here. Any help with this is greatly appreciated as I wanna keep providing this alternative for others who need it. It's nice to see that you're keeping the project here after its removal. Thanks for doing that.

@Metastem I think I have full right to say my point of view about it, you give me ZERO chances. About the why I did it, look at my reply: https://codeberg.org/LibRedirect/libredirect/issues/89#issuecomment-919797

I'm waiting your reply about it

My instance still does not work correctly regardless of how many times I've deleted and rebuilt it. If there is an issue where this has been solved, please point me in the right direction. I can't find anything other than issue [https://github.com//issues/92], and that does not appear to be resolved either. I'm honestly at a loss and genuinely looking for help.

Wikiless was originally designed with the "Vector 2010" design in mind.

After the redesign late last year, it quickly came to people's attention that appending a mere URL parameter could not only change the design of classic Wikipedia, but Wikiless as well. Thus, appending ?useskin=vector could fix the major formatting errors found on Wikiless.

In addition to eventually supporting the more modern design, I think it would be nice to offer support for older designs such as ?useskin=modern or ?useskin=minerva. Some themes are especially more ideal for mobile use such as ?useskin=timeless.

If you would like to see what I mean, try this userscript.

Hello,

as seen on https://wikiless.datura.network/ i get the error "invalid lang" even though i put 'en' as the language.

current files:

-docker-compose.yml: https://privatebin.nihilism.network/?2c50d36283da2f67#3nKhFrJHDUpe8VmCtYmp5G8ZHb1r4XMytnfdVuN8zuKw

-wikiless.config: https://privatebin.nihilism.network/?4ce8268ce094847a#DsCCUR8pAEREAgUrZ4GgSSL4bGaVQBw3jwozJKQqr5Wo

-nginx reverse proxy site config: https://privatebin.nihilism.network/?c80d9878ed9ebe28#HZv5DxEr8PftrsqjndFRVkKMnRMppyfGt1ZpaeGKub8J

any idea what i did wrong there ?

I'm running a local instance of wikiless for my use only. Recently it sort of broke. I can go to any wikipedia article (e.g. from a web search using LibRedirect). However, clicking any link in the article gives me an error. Here is my docker-compose:

version: "3.7"

services:
  wikiless:
   #build from source, incase repo goes down!
    #build:
      #context: .
      #dockerfile: Dockerfile
    image: ghcr.io/metastem/wikiless:latest
    restart: always
    networks:
      wikiless_net:
        ipv4_address: 172.4.0.6
    environment:
      REDIS_HOST: redis://172.4.0.5:6379
    ports:
      - "8380:8080" # change port if needed
    security_opt:
      - no-new-privileges:true
    cap_drop:
      - ALL
    depends_on:
        - wikiless_redis

  wikiless_redis:
    image: redis:latest
    restart: always
    networks:
      wikiless_net:
        ipv4_address: 172.4.0.5
    ports:
      - "6379"
    user: nobody
    read_only: true
    security_opt:
      - no-new-privileges:true
    tmpfs:
      - /data:size=10M,mode=0770,uid=65534,gid=65534,noexec,nosuid,nodev
    cap_drop:
      - ALL
    cap_add:
      - SETGID
      - SETUID
      - DAC_OVERRIDE

networks:
  wikiless_net:
    ipam:
      config:
        - subnet: 172.4.0.0/16

Everything was working fine, but now I get (from today's front page):

Cannot GET /Revolutionary_Girl_Utena

I've noticed that when the link resolves it's missing '/wiki/' in the URL. If I manually add it in, it works.

This doesn't work: http://192.168.1.114:8380/Revolutionary_Girl_Utena?lang=en
This does: http://192.168.1.114:8380/wiki/Revolutionary_Girl_Utena?lang=en

Any help would be appreciated.