@aaron

Earlier today I attempted to follow my own account on infosec.exchange, but never received a notification on my account there, which partially explains why my requests to follow a couple of accounts there haven't been accepted. My own request still shows an option to "Cancel Request."

Anyway, I contacted the admin (Jerry) over there to ask if he knows why, but figured I'd follow-up with you too just in case there's some sort of safe or block list that infosec.exchange is/n't on.

@konstantine @aaron
Replying here since this seems to work. I am trying to sort out what is going on. I'm not sure yet.

@maliciouslink @konstantine

Thanks for the heads up - I"ll take a look and see if there is anything I can find

@aaron @konstantine I've been working with the Mastodon development team to try to figure out what's going on. We've hit a dead end and so I want to confirm that chattrbx.com isn't blocking or limiting infosec.exchange?
@maliciouslink @konstantine correct - chattrbx.com is not blocking or limiting infosec.exhange
@aaron @konstantine I think we figured it out - we just realized chattrbx is behind cloudflare and cloudflare's bot protection will block certain types of inter-instance activitypub traffic.
@aaron @konstantine this has apparently been a common problem lately, but I assumed something was wrong on my end - being cached or whatnot

@maliciouslink @konstantine got it - I"ll take a look at that and see about whitelisting infosec.exchange

That's good to know about Cloudflare though - I appreciate it

@aaron @konstantine be aware that outbound traffic for infosec.exchange is behind Fastly and so if Cloudflare might not recognize if you whitelist by domain name since the traffic originates from a different set of IP addresses, etc

@maliciouslink @aaron

Thank you both for taking time out of your day(s) to look into this.