Open tarantonio opened 10 years ago
Good idea! Added to 1.5 milestone. May be pushed to 1.6 if Mark suddenly decides to release TFS 1.0 sooner than expected.
I'll probably host a sentralised blacklist and use cURL, self reminder as teaching resource: http://thehungrycoder.com/general/how-to-submit-a-form-using-php-curl-fsockopen.html
Also checking for DNS or just a normal IP blocker?
Good idea @Alvaritos. I was thinking of a plain IP reporting & validation service, but checking the DNS may be useful as well. Tho I am pretty new to this so I am not very sure how to do it.
This will be a pretty complicated service so I will create it in a separate repository, and it will communicate with Znote AAC through a JSON api.
/offtopic: You can look at Znote AAC API sample here: https://github.com/Znote/ZnoteAAC/blob/master/api/modules/samples/blank.php Live sample module: http://napes.zapto.org/api/modules/samples/blank.php Live basic info and installed modules: http://napes.zapto.org/api/
A simple IP checker - reporting system could do the job I think but would be also nice to check for DNS aswell, never used Znote API so no idea whats for :dancers:
Originally intended for communication with otlist -> AAC. So etc otservlist.org could fetch live information such as online list and display it there. How it looks with debugger: http://otland.net/threads/znote-aac-1-4-tfs-0-2-13-tfs-0-3-6-0-4.166722/page-38#post-2021761 Where I got the initial idea: http://otland.net/threads/otlist-net-a-revolution-for-creators-players.201378/page-9#post-2009458
And how should the IP Blacklist work with the API?
@Znote should we remove or push this matter to the 1.6 milestone since we rely on you to host the centralized blacklist?
@Pwntus yes, done.
My proposal is to add a IP blacklist to AAC, very useful to add paypal scammers for example.