>>16965 Once you pass POW on a single tab the others will load/refresh normally. Its based on a token cookie. If you're using private tabs where nothing is carried over between them then yes, it'll force you to POW for every tab but as anon said, thats a skill issue.

>>16976 N I G G E R ! ! ! ! Please troubleshoot your add-ons and make sure you're not doing something fucky with the websites cookies. If you're legit contact blahblahblah. But most likely you're a nigger. You deserve this humiliation. Xoxo.

Ok, idk what's going on. >there are pics A, B and C >pic A weighs 20MB and uploads instantly when posting >pic B weighs 1MB, upload takes forever when posting and almost always throws Connection failed error >pic C weighs 1MB too but uploads instantly when posting >try posting pics A, B, C - same case as pic B >try posting pics A and C - they upload instantly >try posting B several times in a row - always Connection failed >try posting A between the attempts - instantly uploaded >sometimes pic B passes after 20 attempts at brute forcing it and suddenly every following attempt at posting it gets it posted instantly >but then the problem happens with another pic I want to post Make it make sense. Since it only happens with some of my pics, regardless of their extension or size. Tried >posting from .st >switching location with VPN and posting again >switching location with VPN and using .moe and posting again >running ping -t for some other site to see if it's a connection issue Nothing worked.

Hi, with the new anti-faggotry measures the favicon does not appear in the tab title anymore. See the attached picture. It used to be that after accepting the TOS, the favicon would remain both while navigating inside the same tab and when opening new tabs.

Seems there's "glitch" with .moe Where backlinks wouldn't work and auto-reload stops working >>>/v/2091492

>>16984 when uploading, it checks whether the file already exists and simply reuses it instead of uploading again you cannot use files with the same hashes to test you may have that issue with all or most files that haven't been uploaded before and just aren't able to tell >>16986 the auto reload will stop working due to >>16949 refreshing the page will fix it for the next however many hours the links break because of the ?pow= in the url, remove it and hit enter or open a different page to do the POW when it invalidates before refreshing until the fix goes live

>>16987 👍

>>16966 >>16982 That was fixed but not I have a new issue, the tab that finishes now has ?pow=[NUMBER] in the URL and the page acts like it hasn't finish loading. Replys don't work, ID counts won't pop up, clicking on an image opens it in a new tab etc. Waiting does nothing and removing the pow bit from the URL forces me to do another POW check (including old tabs that were used after the first pow check )

>>16932 It's funny that you think there needs to be a reason 'why' behind it, rather than it being done simply because. Specially when a DDoS just takes pulling out your card and paying some bot herder. Closest you'll probably get is going on the assumption that it's because it's one of the bigger altchans which got it on the sights of some shitter.

>>16989 your browser must be forgetting the cookie after the next navigation for some reason or other extension maybe? tracker prevention settings? antivirus meddling? the page features breaking is a known bug >>16987

>>16981 >depends on how heavy the customization is It's very heavy, at least compared to the other custom CSS I've seen. Damn. Can you at least tell me what specific elements will be removed/changed so I can remove them in the future?

>Checking your browser for faggotry. lmao thanks admin-samas

Is there a recommendation on how to handle duplicate threads on nsfw boards if the older thread is several pages down? Merge, delete, or do nothing?

BETA TEST IS COMPLETE! THANK YOU EVERYONE FOR PUTTING UP WITH IT! We learned a whole lot. Most importantly that the program works exactly as intended, and does so under real load. Expect more involved discussions as we work out the rest of the implementation details. I'm very likely going to host a big roundtable discussion between staff and anons over on Codexx's /t/ board very soon. THANK YOU AGAIN!

Not going any further than confirmed on the agreement on .moe. Never redirects or anything.

>>16996 Chromiumfag spotted. Yeah I just found out the hard way. I built a beautiful new splash system that worked perfectly on Firefox, and broke just like that on anything Chrome. I reverted to the previous system so it should be fine again for now. I'll work on the new one to comply with Google's fucking pajeets. We're about 80% of the way through a significant node upgrade that will incorporate POWBlock fully.

>>16813 i love you, it worked

also sorry for the retarded question why are filenames now ...FILENAME.jpg can i turn it off?

>>16999 to show the extension to determine playability ideally it would be filena[...].ext but I didn't want to do the backend mod for it yet .originalNameLinkWrapper { direction: revert } you can also .originalNameLinkWrapper:hover { max-width: revert } if you don't like the hover constrained to the thumbnail area

Great, clearnet 8chan is inaccessible once again. .moe gives usual 404, .st times out. >comply with Google's fucking pajeets. In what sense?

My board is getting CP spammed. Are you supposed to do anything else besides nuking it in these cases? >>>/fast/44235 >>>/fast/44236 >>>/fast/44237 >>>/fast/44238

>>17002 More or less. Out of curiousity what does the spam look like? Is it edited into anime art?

>>17002 I can't see the images so I can't tell if it's the same kind of spam we've been seeing on /v/bag. Is it the kind where it's anime images with CP superimposed on top at a random position and rotation? We started cracking down on it harder than before on /v/bag just a couple hours ago so we may have escalated it...

>>17004 >>17003 Yeah, same one.

>>16997 Why are webp images not uploading anymore?

I already reported a lot of posts on the /sfw/ overboard. The spammer seems really active.

>>17001 gacha gig was saying that .st was unaccessible as well. But I can access it no problem though? Country or routing bullshit again?

>>17010 temporary bullshit maybe the host or something

Site is still being spam Wonder what set the asshole off.

>>17012 >Wonder what set the asshole off Desperation

>>17012 >Wonder what set the asshole off. I theorize that it's the new site security + me banning the spammer on /v/bag/ fast enough to piss him off. Just my 2 cents. He's also rumoured to be a SEAnig and nobody knows what ever goes on inside the brains of those.

>>17002 >>17012 For what it's worth, enabling per-post captcha seems to have made it stop. I'm guessing it probably went spam some other board without it.

>>17015 Nope, it's still going

Can we get some anti-spam features? This is happening on like 5 boards at once.