>>2268 It wasn't down. Boards with lots of loli and shota content (like this one) have a special block that makes them accessible only within the site, either from crosslinks like >>>/rule34/, from the board list page, or from the top navbar (which changes depending on each board's activity). Anyone using direct links like https://8chan.moe/rule34 will get a fake 404 page, forcing them to first visit an "unblocked" part of the site. Check >>>/site/4482 for a more detailed explanation. My advice is to bookmark the board by pressing the star next to its name (like in pic related). This will place the board in a special area of the navbar that is independent from the main one and let it remain visible regardless of its current activity.

>>2269 Or just go to the board directory. That's how i got back here. https://8chan.moe/boards.js Also, a funny observation: >>>rule34 has this block, but >>>zoo does not. It's kind of funny how cartoon wankers have more restrictions than people who actually fuck animals.

>>2269 Probably explains why the activity on the boards has decreased recently.

>>2277 Blame burger laws. Zoo porn is legal in a federal level, while loli/shota porn is in a grey area that each judge interprets differently, so hosting companies are pickier about the later than about the former and demand weird shenanigans like the blocks applied to this and other boards. By the way, to use crosslinks you need to put the name of the board between slashes, like this: >>>/rule34/ >>>/zoo/. >>2278 Yeah, the blocks make difficult to use and advertise the boards, so the activity is low, but it was doing that, hiding the boards by making them Tor-only (effectively killing them) or risk being shut down by the hosting company, CDN and/or registrar again over loli.

>>2288 Damn they're thicc for lolis.

>>2289 maybe just a bit

>>2288 >Blame burger laws. Zoo porn is legal in a federal level, while loli/shota porn is in a grey area that each judge interprets differently, so hosting companies are pickier about the later than about the former and demand weird shenanigans like the blocks applied to this and other boards. That would mean this board, /delicious/, /loli/, and /sm/. Would've gotten the boot. In reality they're protected under the first amendment and obscenity laws would be unconstitutional such as the 2003 protect act.

>>2297 If you go by the first amendment all of it should be legal but SCOTUS was like "eh that seems controversial let's just infringe on rights bro" when it mattered as usual.

This board (among several others) will without a doubt die a slow death if the admin doesn't implement a better solution. Disabling hotlinking not just to images but entire boards is not a "minor hurdle" but a major one. 8moe I believe has the same host as Gelbooru. Here's how they work around this same issue: by having people toggle on an option to see the content (without having to sign in to an account) which saves a cookie to bypass the block. https://gelbooru.com/index.php?page=account&s=options I think you can do even simpler than what Gelbooru does (where they have people go to a separate page to flip a toggle) while still maintaining the "minor hurdle" definition. I propose for the "contentious boards" disabling hotlinking to all images as they are right now, re-enabling hotlinking to these boards, and changing the way thumbnailing works such that there are two sets of thumbnails: blurred or mosaic pixelated thumbnails (whichever algorithm is faster, don't remember) and normal thumbnails. For all users by default they see the blurred/pixelated thumbnails. When a user clicks a thumbnail a dialogue box should appear stating that contentious content is blocked by default and asking if the user would like to enable it by flipping a toggle. After the user flips on the toggle, a cookie is saved with this information, he can see the normal thumbnails and full images and visiting hotlinks to these images is also enabled. Or in other words, it's like having an account on Sad Panda / Sankaku, but using Gelbooru's approach of using a cookie instead of an account. Ask the admin about this. If the admin refuses to simplify this hurdle I suggest finding a new home for /rule34/, maybe talk to the other board owners like >>>/loli/ , >>>/ss/ and so on about it too. I would suggest banding together and chipping in to hosting your own imageboard for these boards (and also ask for BTC donations on this new site to help cover hosting) with the same web host. Use vichan instead of Lynxchan, the first one is very easy to code in custom features from my experience, the latter is extremely overengineered and difficult to add new features like the above I mentioned. If you folks go ahead with this idea and need help with server/site administration, general PHP/vichan development, caching, security, etc. let me know.

>>2317 Scratch the two sets of thumbnails idea, a client-side Javascript filter that blurs thumbnails would be infinitely easier. Then it would work the same way, you click the blurred thumbnail, and you get a dialogue box as I mentioned showing you a toggle that would get you a cookie that removes the blur filter and enables hotlinking. This would still follow the "minor hurdle" requirement. I believe Derpibooru also uses the same web host, you don't need an account, Gelbooru is not the only site that uses the cookie approach, see: https://derpibooru.org/filters Let the admin know I can write this for him if he's too busy or w/e, this ain't rocket science, don't want money etc. I already offered helping make the webring with no response >>>/site/4709 . I might just install Lynxchan soon on a VM to implement this and show a working example and source code.

>>2317 There's very very few places that will take us.