>>16502 >>16500 >>16501 This is another reason Cloudflare sucks.

>>16503 Platforms that made it their SPOF aren't much better. You'd think that over several hours of this outage bigger companies would switch to something else, but very few (Valve) actually did. The rest, apparently, would just lie down and die if there's nobody to rescue them.

How long it takes to resive a confirmation email? I have hit the "request confirmation email" a few times, and waited over 24hrs and still nothing. I'm using protonmail, not sure if that may be the issue.

>>16506 It's been broken for as long as I can remember.

Will we ever get a copy text function? To make it easier to make generals

>>16509 So that means coming soon? Neat, thanks anon

>>16506 As >>16507 said that shit hasn't work in years. Though at some point recently you stopped needing email verification to do anything board related if I recall correctly so it stopped being much of an issue. Either way you need to manually email codexx to get verified, it's retarded.

Overboard is giving me error 404, anything going on we should know about?

A reminder that tor address is dead. As usual.

I'm like 40% certain there's been some sort of watchlist regression where now it shows watchlist unreads for your own posts after you leave the thread even though their your own post and you've clearly already seen it. I don't remember it doing this until recently. There's a chance it's always been this way and I just memory holed it because I've used this place less but either way it's driving my fucking crazy and it's an annoying bug.

>>16514 I can't remember if it was always that way, but it's been that way at least since the last update months ago, and yeah, drives me nuts, too it should be a quick fix

>>16514 I think you gotta scroll to the bottom after posting to prevent this from happening

Anyone else seeing .moe pulling this sadpanda bullshit after the terms of service page?

>>16518 What's this about? All I get is the typical 404. Oh hey, .se is for once not shitting itself. But tor is down. (still)

Thoughts on this, Acid/Codexx?

>>16520 Let's ignore for a second how disgusting and antithetical to chans the whole proposal is, and how incentivizing users to keep a single ID for a long time is basically doing the glowies' job for free, and let's look at the more practical problems. >A new ID's posts have to be manually approved before going live That would require an ungodly amount of work for vols, and would introduce massive latency (at least hours, likely days) for non-whitelisted posters (which include every single new user). >Only 3 posts can be queued at a time So not only would latency be terrible, throughput would be shit as well. >An ID had to make however many posts, say 15, before a vol can approve the ID to whitelist them 15/3 = 5 cycles of manual approval at a minimum, which could easily translate to a week of IRL time. No vaguely sane user will ever put up with that shit, you'd be stuck with the dregs that accumulate in private trackers and super sekrit discords. >inb4 the post counts were just there as examples They still show how little thought was put into this garbage suggestion.

>>16520 Every one of these convoluted ideas is more retarded than just giving individual board owners control over bypass generation and PoW bypass difficulty. A board owner should be able to decide it takes an hour to generate a bypass and then that bypass can last indefinitely or for only a week. Then each individual community can dictate what suites their level of board activity and the kind of malicious mitigation they require. You're over-complicating shit when the dev's clearly barely have enough time to tweak the already existing systems and fix basic issues with the overboard. It took years before they even hinted at being open to the idea of bypasses per board, and that still isn't even implemented yet. Your convoluted ideas will never get developed even if they weren't retarded and unnecessary.

>>16520 not worth their time reading that post doesn't understand anything at play >>16524 update after this will tackle some of the bypass stuff, there's a lot of space to improve them what's wrong with the overboard?

>>16522 >you'd be stuck with the dregs that accumulate in private trackers The worst fate possible. Unrelated but I hate when people in any media community recommend joining a private tracker, most people do not have the time or patience to put up with that bullshit. >>16524 >>16525 As far as I can tell, the PoW hasn't actually affected /v/'s spammer at all. He's brute forcing everything with sheer autism, what's realistically to stop him just toughing it out if the hash is made ten times harder?

>>16526 >Unrelated but I hate when people in any media community recommend joining a private tracker, most people do not have the time or patience to put up with that bullshit. What time or patience? 80% of the shit on torrentleech is free leech anyways. You just make an account and torrent shit and within a few months you have infinite ratio. The hardest part of private trackers is just getting invited to them.

>>16527 I'm speaking from my experience on a PT, about 15 years ago, where it was nothing but circlejerking and abusive mods and having to navigate some of the most annoying people you will ever talk to. You had to be active in the IRC and if one person in whatever the groups of seeders were called got in trouble the whole group got banned. Pirating is different now to how was then, the "scene" massively fell off in relevance and everything is public P2P, so maybe PTs have chilled the fuck out since.

>> 16520 It would be significantly easier on both parties to add captcha-per-post though Cspammer doesn't seem affected by captchas Only part that's correct are the current approaches not working >>16528 If your timeline is correct there was unfortunately a lot of awful gatekeeping and sekrit klubbing at that time but even for the era it sounds like you got into a remarkably shitty tracker LARPing as topsite

>>16529 captchas are almost a dead technology when anyone can train a local model in no time flat and per post captchas suck for many reasons bypass captchas could be more adversarial given solving them should be somewhat rare

>>16526 >spoiler Those posts are made by members of the tracker, like all internet cabals the most important perk is the prospect of having power over lower tier members. >PoW It doesn't work the way Acid thinks it works: can't blame him either, it's cryptomemetech so the surrounding discourse is maybe 1% factual. PoW hurts spam for profit without annoying legit users too much, that's all it does: it won't stop schizos who feel a deep urge to let everyone know about their hypercube, it won't stop rival sites spamming your to kill the competition, it won't stop anyone posting CP for the evulz... And if you raise the difficulty you'll piss off Average Joe long before significantly slowing down bad actors. >>16529 >captcha-per-post Stacking copies of the same faulty security layer on top of each other is a feels-good measure that doesn't accomplish anything of value and most notably does not plug those faults. In simpler terms: the spam that can get through the bypass captcha would get through the per-post captcha in the same way.

>>16425 I use VPNs and Tor regularly because there is no harm doing it and it protects against ip grabbers and data breaches so that's good.

>>16531 PoW or not, arbitrarily and reactively time gating bypasses is the simplest approach to dealing with shitters without impacting regular consistently active users.

>>16480 Where is .se hosted? It used to be faster than moe for me, several months ago, but now I doubt it still is I think European anons prefer it over moe

>>16534 >prefer it lol that's a funky way to put it

>>16534 I prefer .moe. It's what I've been using ever since this imageboard was part of the webring. But .moe has been made inaccessible.

>>16534 I prefer .onion, but it's always down. .moe is the second option because it's fast. I have no interest in .se whatsoever, and it's only a matter of time before 'Europe' blocks it too along with the rest of the internet. I'm not sure why 'European anons' still confine themselves to their censorship-states and whine about a honeypot not being accessible without tor.

>>16539 been a rough month for .se users huh

im here to complain about one of the nodes for .moe being down, the only fix so far is to repeatedly clear my dns cache until it connects to a working one, there's also no way to know that this is the issue without being spoonfed from a different site by someone who knows about the issue and how to fix

>>16542 tor doesn't work either and dince .moe is blocked by my faggot ISP i have to access .moe through fucking tor

>>16546 Which is how you should be accessing it anyway. Seriously, with the constant CP spam imageboards without anime captcha shouldn't even have clearnet addresses.