Whoever you are whose crawler this is, fix your thing already. You're supposed to use nodeinfo instead of hardcoded API paths with typos. And maybe Mastodon's /api/v1/instance, but that's debatable.
Whoever you are whose crawler this is, fix your thing already. You're supposed to use nodeinfo instead of hardcoded API paths with typos. And maybe Mastodon's /api/v1/instance, but that's debatable. 17 comments
@grishka Oh yeah ... 3.6. is really old. These versions don't even speak AP at all. I guess we introduced AP in 2019 or late 2018.
@heluecht it's a native REST client for macOS, a very nice one. They were giving away licenses for retweets a while ago. @grishka We should have published everything. If something isn't working, please tell.
@heluecht everything that's in this tab https://pirati.ca/profile/heluecht/profile in your profile isn't returned anywhere in the AP actor. @grishka You wrote "everything" - which confused me. The variable profile texts can't be exported though, since they are freeformat.
@grishka Or do you mean that it isn't included in the activities? We only provide the URL there, since this is just a waste of space to provide this info with each and every activity.
|
In newer versions we now use a different order of requests to reduce the amount of needed queries per server. BTW: All the queried endpoints are valid in some versions of Friendica (which at one point hat the name Friendika) and GNU Social (which had the name Statusnet before).
The current server detection looks like this: github.com/friendica/friendica…
In current versions we search for "/.well-known/nodeinfo" first. And we only query those endpoints above only when this query hadn't been successful (and also when the "host-meta" path is present). This seems to work fine with Smithereen (I just did a quick test against a known server).