You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was fooling around a bit, trying to better assess my site's performance, and then noticed, in NGINX's access logs, that I receive hundreds of GET requests from Pleroma and Akkoma instances whenever I use my main Mastodon account to boost or reply to a comment.
And it's all the same instances (from actual followers of my Mastodon account) and all the same GET requests (for the one specific comment I was interacting with).
Was wondering if this is known behavior, if maybe these servers are incompatible with /?c=1234 URLs, or if there's something else we could do?
My server seems to respond with a 200, and when I myself do curl -H "Accept: application/activity+json" http://example.org/?c=1234, let's say, I get properly formatted (I think :-D) JSON. And clicking the link sends me to the correct post and #comment-1234, so that part, too, looks like it's working fine.
Might have to introduce some rate limiting or something otherwise ...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was fooling around a bit, trying to better assess my site's performance, and then noticed, in NGINX's access logs, that I receive hundreds of GET requests from Pleroma and Akkoma instances whenever I use my main Mastodon account to boost or reply to a comment.
And it's all the same instances (from actual followers of my Mastodon account) and all the same GET requests (for the one specific comment I was interacting with).
Was wondering if this is known behavior, if maybe these servers are incompatible with
/?c=1234
URLs, or if there's something else we could do?My server seems to respond with a 200, and when I myself do
curl -H "Accept: application/activity+json" http://example.org/?c=1234
, let's say, I get properly formatted (I think :-D) JSON. And clicking the link sends me to the correct post and#comment-1234
, so that part, too, looks like it's working fine.Might have to introduce some rate limiting or something otherwise ...
Beta Was this translation helpful? Give feedback.
All reactions