[ art / civ / cult / cyb / diy / drg / feels / layer / lit / λ / q / r / sci / sec / tech / w / zzz ] archive provided by lainchan.jp

lainchan archive - /q/ - 11905



File: 1475712677363.png (54.71 KB, 300x300, aaa.jpg)

No.11905

any plans to get an onion for lain?

  No.11943

As far as I know, no. We are stretched donation and workwise even just with this one site.

  No.11948

The tor daemon can be run on the same infrastructure. It's basically a ten minute setup and forget about it deal.

  No.11949

>>11943
How do you/does lain feel, if another party were to setup a mirror and give yourself access along with the rest of the lainmins (I presume you're one)?

>>11948
Depends. If infrastructure as of current was as basic as just a single box with no additional's, this would have already been suggested.

  No.12134

>>11949

no thanks! the hidden service should be run by lainchain admins. 3rd party proxies are spoooooky!

  No.12135

onion is probably more of a security risk by now anyway.

  No.12150

>>12135
get out of here john doe

  No.12163

We've considered it at various points before. It would be very easy to do, barring the computational time to generate a cute vanity .onion address, but we'd obviously lose a significant amount of moderation ability. We may have to restrict posts on the onion to be only text or image if we do implement a hidden service gateway. Never say never, but I don't see it happening too awfully soon.

  No.12188

>>12163
I'm really happy to hear that you're at least considering it.

>We may have to restrict posts on the onion to be only text or image if we do implement a hidden service gateway.

A tip from someone exclusively using the 8ch .onion on the very few and obscure boards worth browsing, simply disable images. On 8ch this unfortunately also entails that thread creation is also disabled for the .onion users, due to thread creation being impossible w/o pictures. This I think was an unintended consequence, so I'm pointing it out here in hope that it won't be repeated.

The stereotypical threat of .onion access is CP images and perhaps CP hyperlinks. The first would be averted with the above restrictions.The latter, if some sort of defense isn't already in place (which would be useful) could be countered with whitelists, scripts. I think 420chan already does this IIRC.

Anyway, glad to see that Lainchan's going well. Thought it would crumble and burn forever there for a while.

  No.12449

>>12188
This. Also bump?

  No.12450

>>12163
It would be a waste of time to maintain for a handful of users.

>>12188
>The REAL threat of .onion access is allowing pedophiles to post their cancerous bullsoykaf and illegal fap material.
fixed.

Users that require privacy already know how to protect themselves. Lainchan is not here to babysit (pun intended).

  No.12574

Here's how I would do it:

- disable image posting for tor users
- allow starting thread image posting and automagically spoiler it with something that indicates it's from a tor poster
- redirect clearnet tor connections towards the onion address similar to how nextchan does this

  No.12575

>>12574
I agree.

  No.12588

>>12450
Very emotional.

>>12574
I third this, except
> - allow starting thread image posting and automagically spoiler it with something that indicates it's from a tor poster
this makes for elevated moderating efforts, as opposed to not allowing pictures (while still being able to make threads). We could have a stock Tor Poster image tho, alike the stock image for .epub/.pdf files.

  No.12590

>>12588
>this makes for elevated moderating efforts, as opposed to not allowing pictures (while still being able to make threads). We could have a stock Tor Poster image tho, alike the stock image for .epub/.pdf files.

Good point. I should have thought of this. So far:

- disable image posting for tor users
- stock tor poster image(s) for threads (using only one image might stale the lain aesthetic, a folder of low size images that point towards tor thematically might be a better idea)
- redirect clearnet tor connections towards the onion address

  No.12656

yes i agree, disable images.
Onion address would be really cool to have, not everyone has a VPN or wants to pay for one therefor Tor is free to use.

  No.12682

make an enclave site where users request acccess then give the real onion and add their user credentials to real onion's torrc

utilize builtin tor feature for authorized clients

if the user misbehaves, all it takes to ban them is deleting their username from the torrc.

obviously this would require a bit of dev work to make it so each post is authenticated or passes their username somehow, but surely you could hack something that utilized the tripcode fields?

  No.12689

I run a semi-active imageboard that has a Tor service. There will be spam, but if you have someone constantly watching the recent posts it should be fine. Obviously there's no bans and moderation would have to be done on a per-post basis.

However, if you don't have thread-ids that can be used to differentiate between normal posters and Tor posters, I wouldn't recommend it since a normal user would not know if they're replying to bait posted over Tor or not.

  No.12967

File: 1486725581363.png (34.24 KB, 200x200, hey.kid.jpeg)

I don't see any difference between posts from tor exit nodes (like this one) and from within tor with hidden services for lainchan's admin and moderators except you force tor users to expose themselves to much easier MITM, traffic and timing correlation attacks.

Nothing stops me from posting a bad picture or from spamming from most of tor's 1000 exit nodes. Except human dignity.

Anyway, there's absolutely no reason not to have .onion and .i2p hidden services for read-only access.

And assuming you have some kind of rate limiting already I would try enabling read-write and see what happens.

I doubt anything will happen at all, considering current average posting speed and unrestricted access from tor exit nodes you have already.