debian

DruCall 1.1.0 released

DruCall 1.1.0 for Drupal has just been released.

The main improvement over 1.0.0 is that it now permits the TURN servers to be configured instead of using hard-coded STUN server addresses. TURN servers (such as reTurn from reSIProcate or TurnServer.org) provide the ability to relay media streams on a public IP to ensure guaranteed NAT traversal. Support for ICE/STUN/TURN is a mandatory part of the WebRTC specification.

Enabling spam-free comments on this blog (Updated)

I'd like to enable commenting on this blog, but I've seen blogs flooded with spam in the past.

Due to my work and other commitments, I can't monitor the blog constantly to filter out spam.

Can anybody suggest a viable solution? Should I ask people to register by SMS, like getting a Facebook account? Should I try the Mollom network-based service discussed in the Drupal site? Will Captchas cause more frustration than adding value?

Understanding the WebRTC architecture from a free software perspective

WebRTC is here, now.

Google launched Chrome 25 with built-in WebRTC support on Monday, 25 February. Within 24 hours, DruCall, an easy-to-use WebRTC module for Drupal was available Free as a shiny new GPL project.

While this technology offers a level of convenience for end-users that is unprecedented, just what is involved for the keen server administrator who wants to deploy this today?

Announcing DruCall, the WebRTC module for Drupal blogs, CMS and e-commerce sites

Building on my previous work to put convenient WebRTC solutions into the hands of the free software community, I've just created the DruCall WebRTC module for Drupal.

DruCall makes it easier than ever to put click-to-call functionality into virtually any Drupal powered web site, whether your run a personal blog or the United States Government (the White House really does use Drupal)

Pages