The ***** spam seems to have been cleaned up, was that automatic?
The previous threads, including the ***** spam ones, were dated around 2016

The input form in the catalog page is a little less vandalized, but the subject and file input fields are still hidden
https://endchan.net/dump/catalog.html

Okay, we'll see what can we do about it.

Do you want to claim the board perhaps?

>>19014
I would be interested in managing it, yes.

>>19015
Make an account (usernames are case sensitive).
Send an email here, that you want to claim the board:
https://endchan.gg/.static/contact.html
Usually it could take some time, but perhaps today we can transfer it to you.

Send the username too. (Don't forget it's case sensitive.)

sent email

I've also just discovered one more vandalism
it appears the /dump/ board is set to allow only 1 thread, so every new thread autodeletes the previous one

Example:
new thread
https://endchan.net/dump/res/8.html
the previous thread 7 is already auto-deleted
https://endchan.net/dump/res/7.html

>>19018
Which also explains how all the previous ***** spam suddently vanished after the first test thread was made

>>19018
>>19019
Board should be transferred to you now.
I have to note: what you describe isn't really vandalization. Both custom css and the thread limit are board settings, and legitimate to change. Granted it's not the usual way how boards look and behave.

>>19020
>it's not the usual way how boards look and behave
It's an abstract kind of board.

>>19020
Thanks, I'm making it usable again

I called it vandalization because those previous settings were devised to make the whole board unusable
But yeah, that "act" woulodn't have been possible if the site settings didn't allow it to happen

>>19023
Could you share the CCS that makes a board unusable? I want to create my own board for the sole purpose of using that CCS. Call it a personal art project.

>>19024
Something about:
table tr {display:none;}

Just wondering, is there a setting somewhere to allow images uploaded on a board to appear on the site index?
https://endchan.net/
Or it's just a selected few boards to have that feature?

Also, in the board settings, what does the little "2" stand for?
I couldn't find any reference about those, what are the max and default limits for each field marked with "2"?

>>19024
Just set relevant dom elements to display: none.

>>19026
The posted images do show up on the new images feed. Then disappear as other images get posted, the feed is live. When the site is very active some images might skip I imagine, and if displayed they won't spend much time like that.

>>19026
I think you have to be a SFW Christian board to have such privileges.

>>19029
images from /dump/ don't seem to show
>>19030
Guessed it was that stopping images from showing up, and how are boards set to either sfw or nsfw?

But guess, for a matter of safety it would be better to keep /dump/ as it is, not showing images sitewide, i can't guarantee to be always ready to stop a sudden ***** spam attack

>>19028
I guess the 2s signify some footnote. I've no idea.
Maximum files, I think 5 the max.
Max file size is 350MB on paper. But even with JS disabled it's hard to upload a ~300 MB file. I managed couple of times. With JS on don't expect nowhere that. Still even a 100 MB is insanely large compared to other imageboards.
Thread limit is how many threads are allowed. I think 160 max.

>>19030
There is a checkbox above the new images feed on the home page. For displaying NSFW boards (well, all boards really). If it is unchecked for you, then for you it won't show up.

>>19031
See the last line in previous post.
If your board is set to NSFW, then the images will only show up if the NSFW checkbox is marked on the home page's new images feed.
That new images feed needs JS to work however. If on your browser it is turned off (like on Tor browser perhaps), then it won't display it to you.

>>19033
Yes, /dump/ right now appears to be set a nsfw
but how are the whole boards themselves set to either sfw or nsfw?
There doesn't appear to be a setting for that in the board settings, so I guess the whole board sfw/nsfw setting can be changed only by side mods and owners?

>>19034
Ah, sorry for no reply. We're going to get the bottom of this, hopefully will can say more, or fix/change how NSFW/SFW is issued.

Hello, i'm here again for more problems
lately the moderation action of spoilering images isn't working anymore

before it worked like this:
-post images inside a thread appear as spoilered right after spoilering them by moderation
-OP images didn't spoiler right away after getting spoilered by moderation, but the change appeared only after the catalog got refreshed by a new thread or an other thread bump

how it works now:
-OP images remain unspoilered after getting marked as spoiler by moderation actions, and even after a catalog refresh the OP image remains unspoilered

examples (nsfw bot spam)
>>>/dump/1122
the image in that thread op was already spoilered by moderation actions, but it's yet not spoilered even after the catalog did change
>>>/dump/1104
this same bot spammer thread had the image just deleted because this no-spoiler issue started to be noticeable yesterday
>>>/dump/432 this was the first occurrence of this same bot spammer

I know I can just delete the rule-breaking images(that still works at least), and wide range ban the bot, but I'm interested to know why this specific spoilering action isn't working anymore, I'd rather still have that tool available if possible

Are OP images no longer be spoilerable only for /dump/ or is this happening on other boards too?
Has something changed in the site-wide page structure lately, and could that change be causing this?
Or what could otherwise be the cause of OP images no longer spoilering by moderation?

>>19098
and just out of curiosity:
is there any way to unspoiler images?

>>19098
also, i'm keeping the op image of >>>/dump/1122 unspoilered/undeleted for the mean time, even if it's clearly against site rules, only so that the admins can possibly test for themselves if the spoilering actions are working as intended or not

>>19098
I'll try to make sense of that a bit later, but I have a question:
Why would you ban illegal content but not delete it? Please delete it next time. If you ban or not beyond that: whatever you like.

>>19101
>Why would you ban illegal content but not delete it?
1) in the short term, spoilering rule-breaking images allows me to extract as much information from the bot post to better fine tune the anti-spam filters, while saving my mind from having to continuosly see mindrot images
2) in the long term, every illegal image and every post feeds into the r9k filter, building up an automatic and passive resistance for the board even when i'm not around, lessening the human moderation workload (it's building up an immunity system)
2b) having an automatic immunity system for a board doesn't reduce to zero the spam, but it makes it more annoying and more burdersome for any spammer to carry on their activities, i just like to spite the *****ers
3) allowing rulebreaking content to remain undeleted on the board, but spoilered so to avoid *****/***** shock flashing and saving the eyes of the random and innocent board visitor, allows any random board tourist to evalue by themselves how much the board is currently under attack from bots or from shills; i'd rather the random visitors to see what is really going on in the board even if that means having it more messy, rather than having the board be always perfectly tidy while the visitors have no clue of the minefield they are walking on (this reason also runs on the assumption that i'm fully expecting lots of spam to come to the board later on as the board progresses, and i'm trying to anticipate it in any way possible)

There are then few other reasons of lesser importance, but those run more on wishful thinking on my part than anything, so they're unimportant compared to the first ones.
Mainly because of (2) and (3) it's /dump/ board policy to never delete any post and any image, even when they are rule breaking, but to only spoiler them (as a soft removal) and to remove the malicious links, except in extreme cases where deletion is the only reasonable option.
For those reasons, I would very much like to still have the ability to spoiler OP images, which currently seems to be bugged.

>>19102
a live example of reason (1) from the latest *****-bot-spammer: (now deleted >>>/dump/1122 )
it was finding out the ip of the bot spammer did come from sweden

and as for reason (3):
having the swedish flagged *****-spammer be openly visible was more valuable as proof for bystanders than any claim of my part that the bot-spammer was using a swedish ip

and for reason (2):
after the first bot-spam almost two weeks ago, the bot-spammer was nowhere to be seen for two weeks,
but only yesterday and today it came back after both the illegal image and the message were modified to don't be the same as the previous ones,
meaning the bot spammer was now getting forced to generate unique images and messages to get its spam to pass the filters (if the bot spammer wasn't doing it already)
meaning the passive filters were effective, in a first time in blocking the bot spammer, and in a second time in making it more burdersome for the spammer to continue the automated spam

But then again, regardless of any other options or reasons, I wish to see the OP image spoilering mod action to be properly working again

>>19102
I understand what you wrote.
Thing is we scrub the spammed images from the database, so it'll disappear from your board too. On one hand we don't want illegal stuff on the chan, and on the other we don't want users' browsers downloading them accidentally, and on the third hand occasionally we get notices from the hosting company, CloudFlare, private online csam monitoring services, and governments that they found some fishy crap and they want it gone.

>>19103
Heh, you are a cool fella.
The ***** spam is posted on most days of a week. Sometimes it rests for longer than a coupe of days, but usually it doesn't. On an average day it is posted several times, on 8-12 boards. If we are lucky we can catch it right away and delete everything. Sometimes it stay up for a while, probably these are the occasions when you notice it.
He never does the spam from the same IP. Most likely he uses Tor on one of the clearnet domains.
The spam is ongoing for years now. And he does it on several imageboards. Probably everything was tried to stop if, with filters, hashbans and whatever. It's no use. The easiest thing to do is deleting it in timely fashion.

>>19105
Your tests seem to confirm the issue is limited to /dump/
I've tried to spoiler a new thread and the op image isn't spoilered after action, so the bug on /dump/ is still unresolved
>>>/dump/1184

wonder what may have changed in the board to generate this bug,
the custom css has not been changed in a long time, and the first case of the spoiler action not working was after the last css change, so the custom css shouldn't be the reason (i'll go check any css irregularities just to be sure)

For the record, I've noticed for the first time the spoiler-mod-action not working only yesterday, but what caused this bug may have happened before that, since the last spoilered thread was some time before that
The possible timeframe in which the bug did happen should be between:
02/10/2024 >>>/dump/1104 (the first time the spoiler action didn't work)
and
02/06/2024 >>>/dump/818 (the last time the spoiler action did work)

>>19106
Ah I get it, I'll remove anything too questionable as to don't create problems for the site

>>19098
>>19107
I also did some tests. On a board I own I can spoil images just fine, OP images ditto - takes a reload of the page to change the thumbnail to the spoilered one.
I couldn't test on /dump/, I got an error, tried on /test/ where same error appeared. I assume as a global I can't spoiler images.
>Are OP images no longer be spoilerable only for /dump/ or is this happening on other boards too?
Seems to be fine elsewhere.
>Has something changed in the site-wide page structure lately, and could that change be causing this?
No.
>Or what could otherwise be the cause of OP images no longer spoilering by moderation?
I have no idea. Will think some more.

>>19105
Thanks

I've reuploaded the custom spoiler image just in case (images stored in the database getting broken wasn't new), but the bug is still present on /dump/

Currently on /dump/:
-posts inside threads can be spoilered perfectly fine
example of regular post getting spoilered by mod-action: >>>/dump/1188
-op images instead remain unspoilered after action
example of op image not getting spoilered by mod-action: >>>/dump/1184 <- pictured, the site gives the notice that the image has been spoilered, but nothing really happens, and the image remains unspoilered


I've noticed the different layouts of your screenshots, makes me think this may be a browser compatibility issue, but it's strange, the spoilering of op images did work before, so it shouldn't be a browser compatibility issue, since nothing changed on my side in that regard.
I'll test the spoilering with a different browser just to be sure

>>19113
We figured out spoilering is reserved for board staff, so that's not an error.
I don't think it's browser dependent.
What is the situation with spoilers now?
Do you have JS turned off?

>>19117
>What is the situation with spoilers now?
Nothing has changed for the better yet, OP images still can't be spoilered
>Do you have JS turned off?
I've tried to spoiler OP images both with and without JS, same result: I get a message that the image has been spoilered, but it's a false message as it remains unspoilered
I've also given a try with a different browser but it was a failure there too

If it's neither the browser, and neither the presence or absence of JS, what else could it be the reason? What other board specific settings are there which relate to spoilers?
Something has changed between 02/10/2024 and 02/06/2024 leading to this bug,
could it be a third party dependency inside the spoilering function which got updated by the third party library and which introduced some kind of incompatibility?
(i'm totally trying to guess, as i've no clue how the spoiler funcion is coded)

>>19118
Are you spoiling from "Moderate Thread" or somewhere else?

>>19119
The sequence of actions I do to spoiler an image are:
1) open the thread
2) click on "Moderate Thread", to enable the moderation actions
3) select the checkbox of the post to spoiler, in this case the OP post
4) click on the "Spoil files" button, from the actions panel at the page bottom (this action doesn't seem to require the captcha)
Then I get the "Files spoilered" confirmation message, then nothing happens
This same operation did work previously, these OP images were spoilered manually >>>/dump/432 >>>/dump/818 now it no longer works

Out of curiosity, there exist other places from where it's possible to spoiler, aside the "Moderate Thread" viewmode?

>>19123
I'll look into making this easier on Magrathea