Wikipedia talk:WikiProject on open proxies
| This is the talk page for discussing improvements to the WikiProject on open proxies page. |
|
Archives: 1, 2, 3, 4Auto-archiving period: 31 days  |
 | WikiProject on open proxies was featured in a WikiProject Report in the Signpost on 27th June 2021. |
Corporate VPNs
[edit]We have been quite inconsistent with blocks on corporate VPNs like McAfee WGCS or Zscaler. Sometimes they are blocked, sometimes they are not. I wonder what are your thoguths on this? I think a few of the options would be:
- Block all of them.
- Block all of them, anon. only.
- Block only when abused.
The rationale for treating them in a different way is that these are sometimes the default connection option at some workplaces, and their usage is beyond control by the user when they are connecting from that location, so I think hardblocks might be undersirable. I would lean towards blocking all of them as anon. only if we have regularly seen them abused, but I'm not sure that happened. MarioGom (talk) 22:51, 25 September 2023 (UTC)
- If we're to block em, my preference would be to softblock. It reduces the risk of disruptive edits by anon editors, while still allowing established accounts to edit from the same connection. I also think it would be beneficial to have some consistency here. I know the corporate VPN providers like Zscaler have a lower risk when compared against other more consumer oriented services, but there is still disruption that occurs there. 165.225.192.0/18 has a few recent examples of disruptive edits from individual IPs within the range, despite first being reported here back in May 2023. Sideswipe9th (talk) 00:32, 19 December 2023 (UTC)
- I think softblocks where there has been disruption is the way to go, which will permit logged-in editors to edit using a corporate gateway while preventing disruptive edits from anons. Malcolmxl5 (talk) 01:08, 25 April 2024 (UTC)
Help with Teahouse/Help desk abuse
[edit]For the past two days, we've had to temporarily semi-protect the Teahouse and Help desk due to a proxy-hopping vandal. My savviest approach has been to block the proxy IPs and implement one-hour protection. We'd generally prefer to not protect those pages, since they're places for new and unregistered users to get support. Can those with more know-how suggest a better approach? List of IPs in the collapsed section below.
Extended content
|
|---|
|
Firefangledfeathers (talk / contribs) 15:06, 28 June 2024 (UTC)
MEGA VPN
[edit]A few days ago, MEGA launched its own VPN service. See their website.
I went through all their locations, and here's what I found:
(NB: according to the WHOIS, the Japanese IP is in fact from New Zealand, not Japan.)
I tried all locations multiple times over a period of several hours. I didn't find a place that has more than two IPs. But this VPN is just starting up, and compared to other VPNs, it's all quite limited. So they'll likely add more servers in the future.