Metadiscussion

Cannot archive Booru links

Megalodon and Ghost Archive return Access Denied errors when trying to archive booru links. This makes documentation and archiving of the Booru on the wiki difficult. It seems to be Cloudflare related. Please fix this as soon as possible @admin :tired:
w
There is also a issue where cloudflare caching on the wiki is VERY strict. we can't overwrite files and most articles appear outdated for logged out users. Could you lower this down? It affects happenings pages too where they are updated daily. It looks to be 2 to 3 days behind
not much good archival services right now besides megalodon
14lesothowon88↗
not much good archival services right now besides megalodon
True. I agree both issues rn are pretty urgent to solve though
Alright
Okay good
I did want to say as well the amount of times I have to do the cloudflare security validation check is also pretty annoying, at least on the booru
Fen↗
I did want to say as well the amount of times I have to do the cloudflare security validation check is also pretty annoying, at least on the booru
this is all over the saltsphere. Nothing can really be done to fix it until they change the system.
WicklowFrog↗
Fen↗
Show quoted text
I did want to say as well the amount of times I have to do the cloudflare security validation check is also pretty annoying, at least on the booru
this is all over the saltsphere. Nothing can really be done to fix it until they change the system.
True, but I am just saying it does seem to happen a lot more often on the booru for me. Just saying is that I would appreciate if the checks were made to be a little less aggressive, especially across the 'sphere. Im sure you find it a bit annoying as well
Fen↗
WicklowFrog↗
Show quoted text
this is all over the saltsphere. Nothing can really be done to fix it until they change the system.
True, but I am just saying it does seem to happen a lot more often on the booru for me. Just saying is that I would appreciate if the checks were made to be a little less aggressive, especially across the 'sphere. Im sure you find it a bit annoying as well
yes it's really annoying, but I don't really expect the admins to fix it.
WicklowFrog↗
Fen↗
Show quoted text
True, but I am just saying it does seem to happen a lot more often on the booru for me. Just saying is that I would appreciate if the checks were made to be a little less aggressive, especially across the 'sphere. Im sure you find it a bit annoying as well
yes it's really annoying, but I don't really expect the admins to fix it.
Only Salt really has access to couldflare I think. He hasn't been seen anywhere recently though. Still, all the mentioned issues are pretty urgent to resolve
@admin It appears you disabled InstantCommons on the wiki. Could you please elaborate on why you did this? All shared files from Wikimedia commons is now broken.
Alphonse↗
@admin It appears you disabled InstantCommons on the wiki. Could you please elaborate on why you did this? All shared files from Wikimedia commons is now broken.
this includes flags, icons, logos, and a ton of other media files in use. If you keep it disabled, we will be forced to re-upload all of them. Please appoint a bureaucrat who can consult matters like these with you, as there are some other critical issues that require resolving as soon as possible.
do thread links still get fucked over if they're moved
@admin You now broke the wiki by installing the incorrect versions. The wiki is on 1.43, the extensions you installed are for 1.45
Alphonse↗
@admin You now broke the wiki by installing the incorrect versions. The wiki is on 1.43, the extensions you installed are for 1.45
Salt's brain... :jsid:
Alphonse↗
@admin You now broke the wiki by installing the incorrect versions. The wiki is on 1.43, the extensions you installed are for 1.45
It's up to you, but if you are planning on upgrading to 1.45, don't, as 1.45 is risky. Stay on 1.43 1.45 is already legacy and not LTS https://www.mediawiki.org/wiki/MediaWiki_1.45 (you want LTS, which is 1.43)
Salt just restore the extensions back to the REL_1.43 versions :tired:
Log in to reply to this thread.