Tor

I am talking about some way to report it (without exposing my identity - using Tor browser) or let it be shutdown. Related Tor FAQ: https://support.torproject.org/abuse/#abuse_remove-content Report1: https://report.cybertip.org Report2: https://www.iwf.org.uk/en/uk-report/ Report3: https://www.inhope.org/EN#hotlineReferral **Here is how to report bad site, in case you find any clearnet traces on the .onion site, incl. email address.** In this particular case, I have been able to spot the ODER/BUY NOW link which lead to a clearnet site. Within a second, it then redirected to a onion site, where I have found an e-mail address. So i had 2 ways to report this (clearnet website and an e-mail). So run whois lookup (for example at https://who.is/whois/ for mentioned clearnet redirect domain name) and inside the output, discover which nameservers/hosting company it is using. Since it has been using Cloudflare, I have submitted the [report form on Cloudflare site](https://abuse.cloudflare.com). Second thing is that e-mail address the paedopile worm provided on the site. I could visit that email service domain to find abuse contact. I have written steps on how i have discovered the initial link and found the e-mail so they can verify the case. **Do you know other way when you do not find any clearnet traces?**

beside this one

It opens maximized by default now, and I can't figure out how to turn that off. Does anybody know? I don't need the window to be nearly that big (this is not a small display) and I've become used to looking at things next to it.

forum.torproject.org

We’re excited to announce WebTunnel, a new bridge pluggable transport (PT) for the Tor ecosystem. It is a censor resistant proxy that try to imitate HTTPS traffic, based on HTTPT research. We are currently operating a trial soft launch for WebTunnel, and encourage bridge operators to set up WebTunnel bridges to discover issues within the implementation of this new pluggable transport.

forum.torproject.org

You might recall that Tor has been restricting the possible amount of Tor relays per IP address to 2, mainly for Sybil prevention reasons.[1] We bumped that limit to 4 earlier this year[2] to make better use of available resources and considered back then bumping that limit further to 8 relays per IP address. I've good news for everyone looking forward to raising that limit further: after an investigation into the effects of allowing 4 relays per IP address[3] we think it is overall beneficial for the network and our users to raise it further to 8.

blog.torproject.org

This release updates Firefox to 102.13.0esr, including bug fixes, stability improvements and important security updates. There were no Android-specific security updates to backport from the Firefox 115 release.