What’s going on?
Tornevall Networks are now live with following upgraded platforms:
- Primary Portal and components
Primary portal and components
Site changed to what was supposed to be TornevallWEB v6. As many visitors already seen, we’ve left the API-WEB creation to speed up projects that is more important to fix, than sites that requires too much time and work too finish. Therefore, most of the site is now in the root based on WordPress and all API integrations are being primarily made with this platform. In the same time, we win a community compatible platform. However, WordPress is not the only part built here.
First of all https://tornevall.net has now become https://www.tornevall.net to somehow support a standard webaddress naming. It is used to comunicate news and happenings, whatever that might be. Besides of this, there is a community forum located under https://www.tornevall.net/portal. The purpose with this forum is supposed to be supportive when there are bigger needs of communication. This is still a work that has to be processed a bit more.
The DNSBL removal tool used on this site is currently completely based on WordPress and available for download here. Just remember, to get everything like delisting etc to work, it is important to have an API key (read below).
This is a replacement of the less known site AUTHv3, which was supposed to host API based configuration. That project, aswell as the main portal, became too big. So in the same way, this site is built around WordPress. However, the big difference here – compared to the primary above – is that this authentication service also serve other users (meaning, it is possible to register an account there, to get API keys etc). So, to get API keys that handles DNSBL requests, this is the place to be. This service is a frontend gui to APIv3.
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.