You are not logged in.
I visited the clang article on ArchWiki then used the search bar to find the article of GCC. GNU Compiler Collection was recommended on results so I clicked on it. Blocked by Anubis with difficulty 6 running for around 12 minutes as of writing and still hasn't completed. (EDIT: completed after around 15 minutes) Most websites use difficulty 2 or 4 and complete under a second. My calculation speed is around 21.000kH/s. My browser is Safari on macOS 15. A private tab on same device is also blocked by difficulty 6 Anubis. My phone which is on the same network receives difficulty 2 Anubis after a search. What can I do to not receive Anubis with difficulty 6 again?
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.6 Safari/605.1.15
Offline
Had the same issue, it's pretty much a lockout of older/slower devices...
You can try a User Agent spoofer, to get back down to difficulty 2.
Though there's probably a reason for this, it's rather annoying.
Offline
I can’t help with the blockade itself, but some search engines allow you to specify site on which you search for information. You may use that to find pages on Arch Wiki.
For example in DDG:
site:wiki.archlinux.org search terms
Offline
Seconding (... I guess thirding?) the annoyance here (Librewolf on various platforms, 2-3 minutes per solve).
I am heavily skeptical of Anubis difficulty being a particularly useful setting in the first place. Like, dumb scrapers are already stopped by low difficulties just by being JS/requiring specific JS features, well implemented scrapers can maintain cookies/state & due to Anubis' server-side-mostly-stateless nature incur the one-time-cost for as many requests as they like. Meanwhile actual users incur the same cost for a relatively low number of queries - arguably a higher cost as its actual humans waiting sometimes minutes in addition to just some CPU calculating away. Exponentially increasing difficulty only punishes a very specific subsection of scrapers (can solve Anubis in the first place but does not maintain state between visits) while significantly annoying users.
Offline
I’m experiencing the same hassle and haven’t been able to use the search function within the Arch Linux Wiki for quite some time now, since the “solution” to this annoying Anubis with difficulty 6 isn’t feasible for my old NUC D54250WYK.
Why is Arch Linux doing this to us?
Are they trying to exclude users of older and weak hardware from using the wiki?
Offline