What’s going on?
Release Notes – WP_DNSBL – Version 2.0.1
- [DNSBLWP-37] – MODULE_BITMASK does counting even if there are no valid array
We’re about to finish the long work of WP-DNSBL v2.0.0 which is a WordPress based plugin that will from this new release support and run with TorneAPIv3. APIv3 has much better documentation of how to use the DNSBL API (here). From this release, the API can also be configured via TorneAUTH v4, which will be located on https://auth.tornevall.net very soon, where API keys can be created automatically. All this together is planned to be a huge facelift (so the forum will hopefully also be updated in the same time and work as an extra support for the portal visitors).
Finishing this plugin has been very welcome by both me and other visitors, that during a long period have had a lot of problems with delisting themselves from the blacklist. For the moment, much of this is handled manually when the standard dnsbl site does not coorporate with us.
- One big update for the new interface is that visitors can do CIDR-lookups (to see their entire network from a blacklist perspective).
- Another update is that it should be more user friendly. Instead of impossible interfaces, there will be a raw, plain POST-form, with captcha support so system admins can run their delisting requests from another computers (where console is not supported)
- The delisting and blacklist views are handled from a wordpress plugin, which means it might not be necessary to use the regular dnsbl server for delistings. By requesting special permissions, other servers might be able to communicate with the remote API too
- The API is documented with more details than APIv2 was. This also means that own implementations of the DNSBL is made easier
- Since we’re using a plugin for this, protecting admins from being banned from their own site is extra important
- All bugs from DNSBLWP v1.x is hopefully fixed and removed
A complete CHANGELOG of what’s been fixed will be released soon. If you can’t wait for a status update you can take a look here. If you feel that something is missing, feel free to join the project and add requests!
When all this is done, there will be a whole new view for what could come next…
Release Notes – WP_DNSBL – Version 2.0.0
- [DNSBLWP-30] – IPtype in helpers.php has no effect anywhere (and is translated into arpas instead of iptypes)
- [DNSBLWP-33] – Do not use HTTP Post when sending DELETE (it fails)
- [DNSBLWP-4] – API Key for handling of blacklists
- [DNSBLWP-18] – Instead of using TorneLIB-curl, use internal WP functions where it is possible
- [DNSBLWP-21] – Clean up database during deactivation/uninstall
- [DNSBLWP-22] – Configuration menus
- [DNSBLWP-25] – Reinstate the commentblock
- [DNSBLWP-26] – Reinstate page redirection
- [DNSBLWP-27] – Reinstate listcontrol
- [DNSBLWP-28] – DNS Lookups in plain mode
- [DNSBLWP-29] – Currently the lookups is based on API – make it resolver-based when single addresses are being requested
- [DNSBLWP-31] – Remove test hosts from project
- [DNSBLWP-32] – Use API instead of DNS when running delisting requests
- [DNSBLWP-34] – Delist in ajax mode
- [DNSBLWP-35] – Allow enter in search form (ajax)
- [DNSBLWP-36] – readme.txt for 2.0
During a very long period some of us has been waiting for a web browser based plugin, that makes it possible to block/remove unwelcome text and content, on for example Facebook. In the beginning, this was all about tests, chainletters, and stuff that was only irritating, for the people reading it.
Time flies by and requests for other filtering functions have starting to pop up that, instead of stupid chainmail, is about politics that only affects the content and not the user (meaning, only the content are blocked and the friend spreading it is not blocked). Still, the content filter is quite free to control, so this is eventually not a problem as the filtering are completely controlled by the user.
However, another aspect of this flow are currently taking form: Is it morally OK to block material with a political agenda? Should you really allow this kind of propaganda be left alone in silence? Even if you and I as persons choose to remove the information from our timelines/flows, the information will still be left there for others to read (and in that form it will become unstoppable). It is with a bit of caution I touch this area, as it might be a very sensitive matter. Therefore I’m looking for questions and feedback for this case.
The plugin is still planned to be built and the work, even if it hasn’t really started yet, can hopefully close up to a start in short. So as said, some kind of feedback would be very great to get here, since things that is left alone in silence, tend to grow big. And soon, it becomes too big to gain control over again.
Currently there’s a few steps left before we can release the new portal system (as shown via the test site at https://www.tornevall.net) and the new portal configurator (Test site located at https://auth.tornevall.com). The old platform for handling DNS Blacklists became deprecated as the development of NetCURL (https://www.netcurl.org) have been highly upgraded to fit other (ecommerce) needs. The behaviour of netcurl is backward compatible, but the DNS blacklist and portal software really needed a facelift anyway.
I’ve been looking for a platform that I can handle easier than the self built, and got stuck into a million of alternatives. However, the forum platform is still there, since there are too many posts and history behind. So those parts can’t be replaced (yet). Besides, if everything goes well, there might be no need of doing so.
So what’s left before a release? Actually, TorneAPI (3.0) is ready to go live and the applications built in the API is also very dynamic. As I proceed more things will be added to it and currently, the big focus is the DNS Blacklist, FraudBL and NETFILTER.