Closed tassoman closed 1 year ago
It seems that requests from the joinmisskey API are not getting through, bot protection or something else may be at fault.
Allowing the following UserAgent may solve the problem:
JoinMisskey/0.1.0; +https://join.misskey.page/instances
I can't grep -i joinmisskey
bot inside reverse proxy nginx access log.
Which server's endpoint is asked?
We are not filtering bots as far I know
robots.txt is allowing everything
misskey.de also was blacklisted as dead, but we're both alive and competing as beautiful Misskey European servers 🥺
Listed in deads.txt doesn't mean blacklisted. It means the bot couldn't access to the servers.
Which server's endpoint is asked?
/.well-known/nodeinfo
I was able to curl nodeinfo paths (well-known and 2.0) but no evidence of joinmisskey client.
While I was reading logs, got istantly a ping:
58.96.yyy.xxx - - [24/Jul/2023:23:47:48 +0000] "GET /.well-known/nodeinfo HTTP/1.1" 200 114 "-" "mint/1.5.1"
58.96.yyy.xxx - - [24/Jul/2023:23:47:48 +0000] "GET /nodeinfo/2.0 HTTP/1.1" 200 1300 "-" "Akkoma 3.9.3-28-g9d7c877d; https://fedi.worf.win <me@worf.win>"
Misskey Social went into deads.txt API file by mistake.
No italian server is listed.
Please remove from api
deads.txt
any PR can't be issued, must be done by hands.