/meta/ - Meta

bugs.png
(231.4KB, 1080x1080)

Use this thread to report any issues you find while using the site. We currently have 2 known issues: 


1. Real-time post updates are not working. I still need to work out how to get websockets to go through the proxy properly. you will see the error switch back to timed refresh after a few seconds, so auto update is still semi-working.
2. Geoip flags are all inheriting the proxy server's location. I've already solved this issue with post IDs so I have a rough idea of what I need to do to fix this, but it is not high priority.

I also fully expect shenanigans immediately after launch, so if anything happens I will be working to fix it as fast as I can. Your help here is appreciated.

1920px-Acipenser_oxyrhynchus.jpg
(277.1KB, 1920x634)

Hello and welcome to zzzchan! I will be using this thread to explain how this site is set up and answer the initial wave of questions. Thread creation on /meta/ will be locked initially, I will explain how this will be handled going forward below.

Now, to answer some initial questions:

>Who the fuck are you? Who are the other mods?
I am sturgeon, I was a mod back on fat/v/ and later z/v/. fat/v/ was my first role as a moderator in any capacity. I'm happy to say that Pasta and seagull have also stuck around and will be managing /v/. r9k's BO will also be back.

>Nice namefagging
I intend to only use my name & role tag when posting something relevant to my role or the site. 

>Why have you set this up?
Because zchan was doing fairly well before the admin pulled the plug without warning. I'd been considering making my own IB since fat died but once zchan went down I decided I had to make the effort. 

>Will you abandon this after x amount of time?
I've gone through the effort of setting all this up after losing 2 previous boards. I'm doing this because I want it to, and I plan to keep this place running as long as I can. 

NeverEndingExodus.webm
(5.1MB, 853x480, 01:42)

This thread is for handling boards from other sites that wish to migrate here/have been orphaned if public thread creation is locked on /meta/. If public thread creation is open you are free to make a dedicated thread here, otherwise I will make one for you.

The rules for migration are : 
- All Migrating/orphaned boards will be considered outside of the application cycle and should contact me at the same email address listed below.
- I will require proof that you are/were the BO/mod on another imageboard, or that the moderation team for the board in question has fallen apart.
- You must agree to follow all global rules for this site.
- You must agree to actively moderate the new board.
- If accepted, you must notify anons on the old board if it still exists. I do not mind If zzzchan is used as a bunker until a migration can be coordinated/ anons are comfortable making the switch. The new board will be unlisted in this type of scenario and will not be announced util ready.

Feel free to ping me at [email protected] in case of a happening. I'll come right here.

janny_paradise.jpg
(71.1KB, 680x425)

EDIT 9/17: APPLICATIONS ARE NOW OPEN FOREVER. FEEL FREE TO SUBMIT ONE AT ANY TIME.
I will leave the rest of the post intact, please ignore the special stipulations.

Hello and welcome to the fist round of BO applications for zzzchan. I will outline the application process below, along with some special stipulations for this first round.

To apply for a board, you must submit your answers to the following questions: 

1. What will the focus of your board be?
2. What will the rules be?
3. How would you handle the following hypothetical scenarios:
    A. A user who is only breaking the rules of your board has a substantial post history that is perfectly fine up until the single instance you are reviewing. What do you do?
    B. A spammer posts CP. What do you do?
    C. A spammer has slid your catalog and all unpinned threads are gone. What do you do?
4. What time range(s) would you normally be able to keep an eye on the board?
5. If your board becomes active enough, do you agree to look for one or more vol(s) to help you? Do you know anyone already?

the_time_honored_japanese_tradition_ofseppuku.jpg
(170.7KB, 1200x676)

2/21 update 
Configs are evidently not perfect yet, I'm digging to see what exactly happened and will try to make the failover actually work as intended.

Apologies for the downtime everyone, I will outline what exactly happened (at least as much as I can) here along with my plans to prevent it from ever happening again.

1. The proxy host fucking died
This is why there was downtime at all, but n0t why that downtime was such an issue. As much as having an eastern European host that doesn't care benefits a site like, at the end of the day its still run by the cock.li guys ##it's not cockbox##. The following points will outline why I could not mitigate this and how I plan to in the future.

2. I only had one proxy
I kept putting off setting up a second proxy. There's no other explanation, I kept putting it off and eventually forgot. This paired with the not-so-reliable nature of the single proxies host was enough to fuck the site. I will be setting up a second, cheap proxy that will function more as a fall back with it's own subdomain. Balancing an array like previously is a huge pain, and often broke. I've reviewed a few different hosts that will probably not cuck out like the last ones did, and a $5 vps with them will be perfectly serviceable. 

And for the dumbest, most bullyable mistake:
3: I didn't backup my fucking proxy configs
All of the nginx config files used for the proxies have changed substantially each time I have had to make server changes, and I didn't back shit up when I set up the current one. This left me unable to rapidly set up a dirt cheap vps to work as a stop-gap in the meantime regardless of their TOS. ##We'd be off it before they could handle any reports anyway## 

1606730368235-2.gif
(1023.8KB, 857x480)

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

murrisa.png
(27.6KB, 520x390)

I'm creating this thread since the same once from >>>/v/ got deleted 2 months ago on the same day and I wanted to suggest an edit to /v/ rules.

Suggestion
Ban and delete GooberGate threads from zzz/v/. They are useless circlejerk threads and mark/v/ already has those threads anyways, so it wouldn't hurt. It might improve the quality of /v/.

Happenings
>dead >>>/a/ spinoff created, it's full of /vhs/BO samefagging
>anon.cafe is probably dead
>this site is 7 months old from the 8th of feburary

fish_torture.mp4
(5.8MB, 640x640, 00:24)

As you all know, we've been on cloudflare's "I'm under attack mode" for the last several days due to a spammer. This has gotten annoying for everyone and I am ready to pull the trigger on implementing recaptcha until a better solution can be implemented, which Tom is currently working on. This is not something I enjoy doing. Using any google service is an absolute last resort and I would be switching to whatever Tom cooks up asap. That said:

If enough of you are fine with how things are now and don't mind skipping recaptcha I won't add it

So I want to hear from you. Do I add recaptcha and we deal with it for a few days or do we just wait for something better?

1607099162554.jpg
(47.3KB, 450x487)

REMOVE BIZNNEL PEDONIGGERS

Please evict the biznnel pedoniggers that have been recently shitting up this site. After all there are global rules against their pedoshit. I'm not sure why they aren't being enforced.

REMOVE BIZNNEL PEDONIGGERS

spoiler test