/operate/ - Endchan Operations

Let us know what's up

Posting mode: Reply

Check to confirm you're not a robot
Drawing x size canvas

Board Rules

Max file size: 350.00 MB

Max files: 5

Max message length: 4096

Manage Board | Moderate Thread

Return | Magrathea | Catalog | Bottom

Expand All Images

(82.90 KB 766x698 New russian.jpg)
Wipe in /rus/. Again. Anonymous 09/08/2021 (Wed) 05:26 [Preview] No. 11764
We need customization of posts(not only threads, all posts) quantity limit in a hour, added from one IP address.

And we need customization of posts(not only threads, all posts) quantity limit in a hour, for all /rus/ board.

Wipe with deleting threads. Anonymous 09/08/2021 (Wed) 06:55 [Preview] No.11767 del
This night >>>/rus/ was attacked by wiper.
He tried to delete our actual threads by bumping ALL old threads on the board, and then creating new garbage threads.
But thanks to only small thread creation limit, he can not delete too many our threads by this way.

Wipe cleaned. But now we know, wipers can make attack any other board on Endchan, with deleting all live threads on it, if thread creation limit to hour will not be setted.

In order to prevent such a situation, we need more customization limits >>11764 for defending our boards and threads on it from wipers. Thank you for attention.

Anonymous 09/11/2021 (Sat) 23:11 [Preview] No.11773 del
I think I know who it is. He hits other boards here, so you're not the only one that gets to deal with him /rus/ BO

Still, sucks to hear what happened to your board. At least you still have it

Anonymous 09/28/2021 (Tue) 18:54 [Preview] No.11784 del
We need more "flood detected" delay between post messages.

odilitime Board owner 09/28/2021 (Tue) 20:09 [Preview] No.11785 del
more delay between posts or more delay between getting those errors?

Also TOR or non-TOR because there's different timers.

WIPE DEFENDING Anonymous 02/07/2022 (Mon) 03:54 [Preview] No.11945 del
Today, and week ago, our board once again attacked by wiper.

We need moderators table list page with unique IDs (include Tor IDs), sorted by quantity of posts/per one ID for last time.
With IDs who wrote too many posts for 72 or 24 hours ago.

In this tab, board owner should have choose via check boxes Wiper's IDs, and could fast and easy ban and delete most spam posts leaved from this unique ID for last 24 (or may be 72) hours.

For example:

ID who leave 37 posts for last 24 hours, - Check box.
ID who leave 32 posts for last 24 hours, - Check box.
ID who leave 26 posts for last 24 hours, - Check box.
ID who leave 20 posts for last 24 hours, - Check box.
ID who leave 17 posts for last 24 hours, - Check box.
ID who leave 8 posts for last 24 hours, - Check box.
ID who leave 6 posts for last 24 hours, - Check box.
ID who leave 5 posts for last 24 hours, - Check box.
ID who leave 3 posts for last 24 hours, - Check box.
ID who leave 1 posts for last 24 hours, - Check box.
[BAN and DELETE] button.

Or may be special button in the end of the page, which can simultaneously ban and delete all recently posts leaved from this IDs(choosed by board owner in check boxes) at current board.

Think about wipe defending please.

Anonymous 02/07/2022 (Mon) 09:51 [Preview] No.11946 del
rus BO might have wiped his board himself to gain these >>11945 new mass surveillance and censorship privileges. Classical problem-reaction-solution. If the real damage is deleted threads, then increasing page limit is obvious solution that does not require arming oppressor with tools of oppression.

Anonymous Admin 02/08/2022 (Tue) 20:53 [Preview] No.11947 del
I'm sorry but we have no time to sink into upgrades for the old engine. Our focus is on magrathea, the new frontend. Since that is our code, the possibility to add something like that is good. However I can't give a date when this will be available.
We can add more threads as puffer like suggested here: >>11946
>increasing page limit
But we can only do that globally. I'll ask.

If there is a pattern to the wipe, maybe I could slap together some shitty JS script for Greasemonkey, which would select certain posts/threads on a page based on some criteria with a click of a button. Problem is: what if someone else's post falls into that criteria? And then, the attacker just needs to change the pattern or drop all patterns, and that's it. If he opens a new thread hourly, he can do it easily. So I don't think there is much sense in this.

Furthermore: there are no individual Tor IDs. All posters with Tor look like one person. If you are a BO you can see posts without IDs if you open the moderate page of the thread, those are Tor posts.

Anonymous Admin 02/08/2022 (Tue) 21:05 [Preview] No.11948 del
Frankly I would suggest to put forward the idea to the users of the board to tinker with Greasemonkey. I thought all Russians are essentially hackers and can decide the outcome of US elections single handedly.

odilitime Board owner 02/08/2022 (Tue) 22:58 [Preview] No.11949 del
> Today, and week ago, our board once again attacked by wiper.
That's the worst, sorry to hear that. Make sure you use the early404 feature, that helps defend against this.

>include Tor IDs
Tor doesn't have IDs which makes your suggestion harder. We did implement a feature for BOs to disable TOR, that can help stop attacks.

>For example
It's a good interface for this case, and we will consider adding to Magrathea. However we also have to consider how that tool could be abused. It would make it easy for a BO account to wipe their own board and ban everyone.

We have added another page worth of threads

yes, greasemonkey maybe a good workaround if you really need this.

Anonymous 08/06/2022 (Sat) 22:23 [Preview] No.12069 del
Can you hide seconds in time of posts? It can be used for timing attack to tor users.
May be it can be via checkbox in moderators settings page.

It about /rus/. /bb/. /ca/. /polru/, /brchat/ boards.

Anonymous Admin 08/09/2022 (Tue) 07:48 [Preview] No.12070 del
How about now?

Anonymous 08/10/2022 (Wed) 16:49 [Preview] No.12071 del
i'm another guy
can you make this more coarse?

Round hours to every day random value at about 6 hrs.

for example: posted at 9:12 (and minutes will be added in random for every message in small fraction like 1-10 minutes) 9:12 9:13 9:20, but sent at 6:46-11:16 (4,5hr) - it helps to hide your timezone from observing cached pages

there is some corporations in russia, who scrap social media every day into big storage and shares it with law authorities and fsb

reports say that some people was caught with telegram post tracking, for example, so it's serious problem and not everybody thing about it

or round to 12 hrs, or remove all hours


Anonymous 08/15/2022 (Mon) 15:34 [Preview] No.12073 del
Problem is if a government agency wants to identify you they are gonna have more sophisticated ways to do that. They could do it with the size of the data or log when the post shows up or whatever, they sure will have great ideas.

Anonymous 08/16/2022 (Tue) 08:45 [Preview] No.12075 del
Good. Thank you!

Anonymous 09/25/2022 (Sun) 18:53 [Preview] No.12112 del
Can you remove names of uploaded files?

Anonymous 09/25/2022 (Sun) 19:03 [Preview] No.12113 del
They can just make a hash of the pics and compare if they want to identify you. Renaming won't do any good.

Anonymous 09/26/2022 (Mon) 20:28 [Preview] No.12114 del
Compare hash with what?

Anonymous 10/07/2022 (Fri) 16:51 [Preview] No.12124 del
This should be an option for the poster or the board, not enforced site wide if implemented.

The culture I'm used to has a habit of leaving messages commenting on the image in the filename. Removing it for everyone would remove a feature.

Anonymous 11/15/2022 (Tue) 21:36 [Preview] No.18260 del
This still could be important.

Anonymous 04/20/2023 (Thu) 16:47 [Preview] No.18476 del
(943.91 KB 1600x1200 Cedrus.jpg)
Hello from /polru/.
Can you restrict Board Volunteer role? Or create new role with fewer rights?
Unfortunately, we have to give Board Volunteer role to people not personally known.
We need:
1. Disable possibility of removal OP posts by Board volunteer.
2. Restrict possibility of removal (quantity/hour) regular messages by Board Volunteer. Customizable by Board owner.

We think Board Volunteer role have too much rights. It can remove our board in a couple of minutes.
May be that changes can help to many other boards on Endchan.
Can you make these changes?

Anonymous Admin 04/20/2023 (Thu) 18:31 [Preview] No.18477 del
That's a no.
We can't really promise it could work even on Magrathea, since it's just a frontend.
On Wrongthink, maybe.
We understand why you suggest these.
The quantity/hour removal might not be a good idea, because floods happen.

I suggest telling the chipmunks to brace themselves. Save everything they want to have, and archive threads with services such as:

Anonymous 04/23/2023 (Sun) 19:40 [Preview] No.18478 del
>The quantity/hour removal might not be a good idea, because floods happen.
Ok. Quantity/day better.

Why banners start moving?

Anonymous 05/02/2023 (Tue) 12:52 [Preview] No.18484 del
Is it possible to set reply limit and bump limit separately?
It appears that the only parameter you can set in the board settings is reply limit, and bump limit is always set to half the reply limit, i.e. if the reply limit is 1000, a thread will be autosaged after 500 posts.
But what if we wanted it to be bumpable up until 1000 posts and become locked at say 1100 posts?

Anonymous Admin 05/02/2023 (Tue) 14:17 [Preview] No.18485 del
Banners fixed.

The amount of posts in a thread the engine can handle comfortably is 500. This is the highest amount before the autosage kicks in, which do so to discourage from more posting. The highest amount of posts is 1000. Both were Lynxchan feature I think originally, just like Mongodb.
I see a board with 100+ users can fill a 500 post thread pretty quick. How about separating out certain topics that should go into dedicated threads so they won't take up space in the main thread? Or dedicate the main to one specific topic. Maybe I'm thinking of the wrong board now.
Perhaps cyclic thread could be tested.

Anonymous 05/11/2023 (Thu) 08:03 [Preview] No.18496 del
My idea was to make both autosage limit and threadlock limit the same 1000, so that the thread doesn't sink from the front page after it goes beyond 500 posts (a new thread is only made when it reaches threadlock). I didn't know it was hardcoded in the engine. But it's probably not necessary, now that we have an active BO, the main thread is always pinned to the top anyway, so it doesn't sink. Anyway, thanks for the help.

odilitime Board owner 06/02/2023 (Fri) 01:37 [Preview] No.18534 del
It's not the engine but users with low-end browsers. Too many DOM elements make browsing content very hard on older computers. The engine can handle a lot more than 1000 and as the site admin, I control these maximums, they're not hardcoded.

We want people to make a new thread after 500 posts.

Top | Catalog | Post a reply | Magrathea | Return