An Occasional Inkompatible Report
After seven years, I guess it's a start.
So after 7 yrs., Gab has finally blocked public access to some very specific API's that allowed analysis of the entire user base (registered user accounts public data) as a whole.
That doesn't solve the issue (as you'll see below).
After the creation of a 'sock' account, randomization of the user agent and the ability for the 'sock/bot' account to actually log-in and start a session. The 'block' is defeated and all the information is still available.
I guess it's a start, but it's clearly just a part of any forthcoming solution.
The plot thickens...



Upon further investigation, this seems to be a Cloudflare mitigation and not actually anything Gab 'did', other than perhaps requesting it. Interstingly enough, none of the 'suggested violations' apply.
PS; Don't think we can't randomize MAC and Hardware Serial fingerprints as well as IP's....
Also, make note of the fact that 'submitting a certain word or phrase' is among the violations that could trigger the block. I wonder what those words and phrases might be?
* I love a good challenge, just sayin'
Thanks for stopping by!