能否支持xcannel.com

[kukukumiko-git]

在寻找一个曲线访问x的方法，xcannel等几个站算是nitter项目硕果仅存的东西了，见https://status.d420.de/
xcannel.com ping得IP198.98.60.34 这个ip可以直接访问
cdn.xcannel.com ip 129.80.246.62 ，无法直接访问，我试图按照文档适配但没有成功，也许这个有cloudflare啥的无法支持

C:\Users\***>curl https://cdn.xcancel.com --resolve "cdn.xcancel.com:443:192.80.246.62" -v
* Added cdn.xcancel.com:443:192.80.246.62 to DNS cache
* Hostname cdn.xcancel.com was found in DNS cache
*   Trying 192.80.246.62:443...
* connect to 192.80.246.62 port 443 from 0.0.0.0 port 10134 failed: Timed out
* Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server
* closing connection #0
curl: (28) Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server

C:\Users\***>curl https://xcancel.com --resolve "xcancel.com:443:198.98.60.34" -v
* Added xcancel.com:443:198.98.60.34 to DNS cache
* Hostname xcancel.com was found in DNS cache
*   Trying 198.98.60.34:443...
* Connected to xcancel.com (198.98.60.34) port 443
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* closing connection #0
curl: (35) Recv failure: Connection was reset

在寻找一个曲线访问x的方法，xcannel等几个站算是nitter项目硕果仅存的东西了，见https://status.d420.de/ xcannel.com ping得IP198.98.60.34 这个ip可以直接访问 cdn.xcannel.com ip 129.80.246.62 ，无法直接访问，我试图按照文档适配但没有成功，也许这个有cloudflare啥的无法支持

C:\Users\***>curl https://cdn.xcancel.com --resolve "cdn.xcancel.com:443:192.80.246.62" -v
* Added cdn.xcancel.com:443:192.80.246.62 to DNS cache
* Hostname cdn.xcancel.com was found in DNS cache
*   Trying 192.80.246.62:443...
* connect to 192.80.246.62 port 443 from 0.0.0.0 port 10134 failed: Timed out
* Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server
* closing connection #0
curl: (28) Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server

C:\Users\***>curl https://xcancel.com --resolve "xcancel.com:443:198.98.60.34" -v
* Added xcancel.com:443:198.98.60.34 to DNS cache
* Hostname xcancel.com was found in DNS cache
*   Trying 198.98.60.34:443...
* Connected to xcancel.com (198.98.60.34) port 443
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* closing connection #0
curl: (35) Recv failure: Connection was reset

cf可以考虑tls分片，或者看看有没有ech

[maoist2009]

在寻找一个曲线访问x的方法，xcannel等几个站算是nitter项目硕果仅存的东西了，见https://status.d420.de/ xcannel.com ping得IP198.98.60.34 这个ip可以直接访问 cdn.xcannel.com ip 129.80.246.62 ，无法直接访问，我试图按照文档适配但没有成功，也许这个有cloudflare啥的无法支持

C:\Users\***>curl https://cdn.xcancel.com --resolve "cdn.xcancel.com:443:192.80.246.62" -v
* Added cdn.xcancel.com:443:192.80.246.62 to DNS cache
* Hostname cdn.xcancel.com was found in DNS cache
*   Trying 192.80.246.62:443...
* connect to 192.80.246.62 port 443 from 0.0.0.0 port 10134 failed: Timed out
* Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server
* closing connection #0
curl: (28) Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server

C:\Users\***>curl https://xcancel.com --resolve "xcancel.com:443:198.98.60.34" -v
* Added xcancel.com:443:198.98.60.34 to DNS cache
* Hostname xcancel.com was found in DNS cache
*   Trying 198.98.60.34:443...
* Connected to xcancel.com (198.98.60.34) port 443
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* closing connection #0
curl: (35) Recv failure: Connection was reset

cf可以考虑tls分片，或者看看有没有ech

可以参考这个非常简陋的实现

 "domains": {
        "xcannel.com": {
            "IP": "198.98.60.34"
        },
        "cdn.xcannel.com": {
            "IP": "129.80.246.62"
        }
}

你知道吗：X上了CF。
笑点：video加载用的fastly

		"video.twimg.com": {
			"CDN": "Fastly: 2024/11/13: 151.101.40.158"
                        "comment": "这句话其实没啥用，这个括号得留着让他查dns，因为fastly ip会变"
		},
		"twimg.com": {
			"IP": "104.19.112.125",
			"TLS_frag": 4
		},
		"x.com": {
			"IP": "104.19.112.125",
			"TCP_frag": 5,
			"TCP_sleep": 0.02,
			"TLS_frag": 2
		},
		"twitter.com": {
			"IP": "104.19.112.125",
			"TLS_frag": 4
		},

另外,emoji的域名abs-0.twimg.com，不知道为啥不让用CF，得用gooreplacer跳到abs.twimg.com

[jonm58]

你知道吗：X上了CF。

Twitter宣布改名成X时,x.com就是CloudFlare的.
x.com正式使用时又改了回去.

笑点：video加载用的fastly

还有pbs, abs, abs-0 都是.而且之前 pbs, abs, abs-0, video 的 fastly cdn 还可以用ipv6的IP,不过现在用 fastly cdn IPv6的IP会404

你知道吗：X上了CF。

Twitter宣布改名成X时,x.com就是CloudFlare的. x.com正式使用时又改了回去.

笑点：video加载用的fastly

还有pbs, abs, abs-0 都是.而且之前 pbs, abs, abs-0, video 的 fastly cdn 还可以用ipv6的IP,不过现在用 fastly cdn IPv6的IP会404

怼cloudflare v4都可以，但是不知道为什么至少我这里要把abs-0转成abs
至少暂时不用曲nitter线救国

在寻找一个曲线访问x的方法，xcannel等几个站算是nitter项目硕果仅存的东西了，见https://status.d420.de/ xcannel.com ping得IP198.98.60.34 这个ip可以直接访问 cdn.xcannel.com ip 129.80.246.62 ，无法直接访问，我试图按照文档适配但没有成功，也许这个有cloudflare啥的无法支持

C:\Users\***>curl https://cdn.xcancel.com --resolve "cdn.xcancel.com:443:192.80.246.62" -v
* Added cdn.xcancel.com:443:192.80.246.62 to DNS cache
* Hostname cdn.xcancel.com was found in DNS cache
*   Trying 192.80.246.62:443...
* connect to 192.80.246.62 port 443 from 0.0.0.0 port 10134 failed: Timed out
* Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server
* closing connection #0
curl: (28) Failed to connect to cdn.xcancel.com port 443 after 21032 ms: Could not connect to server

C:\Users\***>curl https://xcancel.com --resolve "xcancel.com:443:198.98.60.34" -v
* Added xcancel.com:443:198.98.60.34 to DNS cache
* Hostname xcancel.com was found in DNS cache
*   Trying 198.98.60.34:443...
* Connected to xcancel.com (198.98.60.34) port 443
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* closing connection #0
curl: (35) Recv failure: Connection was reset

cf可以考虑tls分片，或者看看有没有ech

可以参考这个非常简陋的实现

 "domains": {
        "xcannel.com": {
            "IP": "198.98.60.34"
        },
        "cdn.xcannel.com": {
            "IP": "129.80.246.62"
        }
}

你那里测试怎么样？

[jonm58]

你知道吗：X上了CF。

Twitter宣布改名成X时,x.com就是CloudFlare的. x.com正式使用时又改了回去.

笑点：video加载用的fastly

还有pbs, abs, abs-0 都是.而且之前 pbs, abs, abs-0, video 的 fastly cdn 还可以用ipv6的IP,不过现在用 fastly cdn IPv6的IP会404

怼cloudflare v4都可以，但是不知道为什么至少我这里要把abs-0转成abs 至少暂时不用曲nitter线救国

你twimg.com,x.com,twitter.com的IP都不是Cloudflare的,你可以查一下IP的ASN

你知道吗：X上了CF。

Twitter宣布改名成X时,x.com就是CloudFlare的. x.com正式使用时又改了回去.

笑点：video加载用的fastly

还有pbs, abs, abs-0 都是.而且之前 pbs, abs, abs-0, video 的 fastly cdn 还可以用ipv6的IP,不过现在用 fastly cdn IPv6的IP会404

怼cloudflare v4都可以，但是不知道为什么至少我这里要把abs-0转成abs 至少暂时不用曲nitter线救国

你twimg.com,x.com,twitter.com的IP都不是Cloudflare的,你可以查一下IP的ASN

我知道，查cf DNS也是返回twitter IP。
但我拿到的故事是这样的：为了封巴西所以用了一会儿CF
来自：https://www.v2ex.com/t/1087699#reply1
所以怼CF现在仍然可行……

你要不信自己套一个TLS+TCP分片用一下。我这里环境上海电信还是移动来着

不知道X会不会把CF撤掉，但先凑合着吧。
话说要v6是因为v6的sni墙没修好是吗？那我不建议直接怼，不然墙太容易机器审查了，至少套个域前置或者分片，ipv6封的比v4还会狠

现在确实不是cf(help.x.com是)，但是cf就是能用

[jonm58]

现在确实不是cf(help.x.com是)，但是cf就是能用

x.com 可以用(使用GhosTCP)
v4 可以,v6 也可以

如果accessor不考虑支持分片或者tcb之类的化，close as not planned？

[maoist2009]

twimg的cf撤掉了。

[maoist2009]

但是可以扫ip

[jonm58]

twimg的cf撤掉了。

什么意思?
pbs.twimg.com 还可以使用.