Feed aggregator

Dirk Eddelbuettel: RcppCNPy 0.2.3

Planet Debian - Fri, 11/04/2014 - 02:49
R 3.1.0 came out today. Among the (impressive and long as usual) list of changes is the added ability to specify CXX_STD = CXX11 in order to get C++11 (or the best available subset on older compilers). This brings a number of changes and opportunities which are frankly too numerous to be discussed in this short post. But it also permits us, at long last, to use long long integer types.

For RcppCNPy, this means that we can finally cover NumPy integer data (along with the double precision we had from the start) on all platforms. Python encodes these as an int64, and that type was unavailable (at least in 32-bit OSs) until we got long long made available to us by R. So today I made the change to depend on R 3.1.0, and select C++11 which allowed us to free the code from a number if #ifdef tests. This all worked out swimmingly and the new package has already been rebuilt for Windows.

I also updated the vignette, and refreshed its look and feel. Full changes are listed below.

Changes in version 0.2.3 (2014-04-10)
  • src/Makevars now sets CXX_STD = CXX11 which also provides the long long type on all platforms, so integer file support is no longer conditional.

  • Consequently, code conditional on RCPP_HAS_LONG_LONG_TYPES has been simplified and is no longer conditional.

  • The package now depends on R 3.1.0 or later to allow this.

  • The vignette has been updated and refreshed to reflect this.

CRANberries also provides a diffstat report for the latest release. As always, feedback is welcome and the rcpp-devel mailing list off the R-Forge page for Rcpp is the best place to start a discussion.

This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.

Categories: Elsewhere

Mediacurrent: Meet Alex McCabe

Planet Drupal - Thu, 10/04/2014 - 22:29


1. So Alex, what's your role at Mediacurrent, both internally and client-related?

 My official title is Drupal Developer. I do site building work, custom module development, sometimes handle deployments, and an occasional bit of light theme work. I also participate in client meetings to provide technical insight where necessary.

2. We're so glad to have you!  Give us an idea of what professional path brought you here.

Categories: Elsewhere

Propeople Blog: Drupal Developer Days 2014

Planet Drupal - Thu, 10/04/2014 - 22:10

I recently had the good fortune of being a part of Drupal Developer Days 2014 in Szeged  - my first Dev Days! It was a really amazing mix of experiences for me, from visiting Hungary for the first time to meeting lots of new people and, of course, lots of Drupal.

Szeged is a beautiful city in Southern Hungary that is no stranger to Drupal (the city hosted DrupalCon Europe 2008), and was a pleasure to visit. If you’re not familiar with Drupal Developer Days, it is an event focused on bringing the Drupal community together to work on the development of the Drupal project. The event presents a great opportunity for some of the leading Drupal experts and developers to work on, and learn about, Drupal 8 in depth before it’s widely released. Dev Days featured code sprints, workshops, sessions, BoFs, after parties and was overall a great time.

Since I’m not a quite Drupal 8 ninja (yet!), I was eager to find opportunities where I could help and learn at the same time. With this in mind, I decided to pick two sprints to add to my schedule: the Drupal.org sprint and the Search API migration sprint.  

Drupal.org Sprint

I knew Drupal user @tvn before the event and had some experience with Drupal.org stuff, so I figured this sprint would heat up to be llots of fun. We started with 89 open issues and 5-6 people in our team. Tasks ranged from “the tiny ones” (https://drupal.org/node/2046683) to “the big problems” (https://drupal.org/node/2130537). But is anything really a problem if you have @tvn, @jthorson, and @jessebeach around? These guys spent a week and closed nearly 50 issues! Yep, some of them are still in review or RBTC, but the majority are resolved. You can find more info here.

Search API Migration Sprint

If you’re familiar with Drupal, you probably know the ApacheSolr and Search API modules and their maintainers: @nick_vh and @drunken_monkey. I was lucky to have a chance to be here with them and merge these two monsters into one single pretty baby! The code is currently inside an external sandbox now (https://drupal.org/sandbox/daeron/2091893) but will be released as a new version of Search API module soon! It was here where I spent most of my days in Szeged, and was in the great company of some talented geeks: @mollux, @aspilicious, @Andrew_l, @Andre-B and others. Before Szeged Dev Days, SearchAPI 8.x was almost clean repo, but now you can already come and try the feature contrib search solution for Drupal 8. We have migrated almost all the code from 7.x version - most of it is already ported to new standards, and some of it has been covered with web and unit tests.

Szeged Drupal Dev Days was awesome, and a great opportunity to learn more about Drupal 8. I would definitely recommend attending any upcoming events like this. Where else can you meet such amazing teams, learn lots of new  stuff about Drupal 8, phpunit, symfony, etc. and feel the spirit of Open Source?

See you there!

 

Tags: DrupalDrupal Developer DaysDrupal eventsCheck this option to include this post in Planet Drupal aggregator: planetTopics: Community & Events
Categories: Elsewhere

Chapter Three: Pick on Your Performance Issues

Planet Drupal - Thu, 10/04/2014 - 19:53

Performance should be in the mind of every Drupal developer and site builder as they are building a site. But let's be honest, while getting everything to just plain work and look good speed doesn't always get to hold that #1 spot in your mind.

Freeing up brain energy from potential performance issues is not necessarily a bad thing. Predicting which issues will have the biggest impact once a site launches is a task best left to wizards and sages. The best way to analyze and then tackle a site's performance issues is with data from the live production site. There are plenty of tools to help simulate that data, but nothing replaces good hard production data.

Luckily Views Cache Bully has come to the rescue of distracted developers everywhere. Set it, forget it and rest easy knowing that you now have one less reason for why your site might be crawling.

Why views caching?

Most the views on your site display the exact same information over and over, they just display it to different users. I know, I know you are a prolific blog writer, but do you really publish a new post every 5 minutes?

If you are feeling conservative, set the defaults to a short value and keep bumping them up as you come to realize how little these things change. Even if you only serve the cached results to five users that means five less trips through PHP and the database for those visitors.

Categories: Elsewhere

AGLOBALWAY: Death to Lorem Ipsum! Content First!

Planet Drupal - Thu, 10/04/2014 - 19:52
Have you ever build a beautifully designed responsive website? You followed mobile first design principles and carefully analyzed the small screen to big screen transition.  It scales magically and works beautifully on IE8 and IE10 at the same time.  All the bugs have been squashed.   Now, it is ready for the client to enter the content.  HOLD on!  What?  Yes, I said it.   You are ready for the client to enter the content.  I suspect you are going to guess what happens next, the beautifully design website with placeholder text buckles.   Lorem Ipsum brings you down.   Of course this never happens to you.     Reality of how the client is actually is going to use the site emerges.   You thought they would give you nice uniform images.  That beautiful pinterest style blog listing now looks like malformed swiss cheese.  Who knew!  The client loves to speak in 100 character bursts that make Twitter look wordy.  Your article listing looks sparse.  Although it may be tempting to blame the client for their writing style or lacking the appropriate reverence for your beautiful design, but that would be a big mistake.  It is time to start thinking about designing websites around content first.     As developers, recognize that the longer it takes to get real content into the system the more risk you are taking on.  As clients, bringing your content to the developer at the start of the project you will more likely have a website that works well for you.  Not only it is important to have a sense of the content, knowing what the bare bones minimum and high priority content can help you small screen design.   When you are doing a content review think of the following:  
  • What business message are you trying to convey?
  • What languages are you using?
  • Are there any regulations that you have to abide by?
  • How quickly can the content be created?
  • Who is creating the content?
  These questions can help you determine your minimal viable content (MVC).  The faster you can create your MVC and get into your developments hands the more successful your responsive multi-platform website will be.  Don’t let lorem ipsum bring you down.   Tags: responsivemobile firstcontent firstwebmutli-platformdrupal planet
Categories: Elsewhere

Steve Kemp: A small assortment of content

Planet Debian - Thu, 10/04/2014 - 17:34

Today I took down my KVM-host machine, rebooting it and restarting all of my guests. It has been a while since I'd done so and I was a little nerveous, as it turned out this nerveousness was prophetic.

I'd forgotten to hardwire the use of proxy_arp so my guests were all broken when the systems came back online.

If you're curious this is what my incoming graph of email SPAM looks like:

I think it is obvious where the downtime occurred, right?

In other news I'm awaiting news from the system administration job I applied for here in Edinburgh, if that doesn't work out I'll need to hunt for another position..

Finally I've started hacking on my console based mail-client some more. It is a modal client which means you're always in one of three states/modes:

  • maildir - Viewing a list of maildir folders.
  • index - Viewing a list of messages.
  • message - Viewing a single message.

As a result of a lot of hacking there is now a fourth mode/state "text-mode". Which allows you to view arbitrary text, for example scrolling up and down a file on-disk, to read the manual, or viewing messages in interesting ways.

Support is still basic at the moment, but both of these work:

-- -- Show a single file -- show_file_contents( "/etc/passwd" ) global_mode( "text" )

Or:

function x() txt = { "${colour:red}Steve", "${colour:blue}Kemp", "${bold}Has", "${underline}Definitely", "Made this work" } show_text( txt ) global_mode( "text") end x()

There will be a new release within the week, I guess, I just need to wire up a few more primitives, write more of a manual, and close some more bugs.

Happy Thursday, or as we say in this house, Hyvää torstai!

Categories: Elsewhere

Joey Hess: Kite: a server's tale

Planet Debian - Thu, 10/04/2014 - 17:17

My server, Kite, is finishing its 20th year online.

It started as kite.resnet.cornell.edu, a 486 under the desk in my dorm room. Early on, it bounced around the DNS -- kite.ithaca.ny.us, kite.ml.org, kite.preferred.com -- before landing on kite.kitenet.net. The hardware has changed too, from a succession of desktop machines, it eventually turned into a 2u rack-mount server in the CCCP co-op. And then it went virtual, and international, spending a brief time in Amsterdam, before relocating to England and the kvm-hosting co-op.

Through all this change, and no few reinstalls from scratch, it's had a single distinct personality. This is a multi-user unix system, of the old school, carefully (and not-so-carefully) configured and administered to perform a grab-bag of functions. Whatever the users need.

I read the olduse.net hacknews newsgroup, and I see, in their descriptions of their server in 1984, the prototype of Kite and all its ilk.

It's consistently had a small group of users, a small subset of my family and friends. Not quite big enough to really turn into a community, and we wall and talk less than we once did.

Exhibit: Kite as it appeared in the 90's

[Intentionally partially broken, being able to read the cgi source code is half the fun.]

Kite was an early server on the WWW, and garnered mention in books and print articles. Not because it did anything important, but because there were few enough interesting web sites that it slightly stood out.

Many times over these 20 years I've wondered what will be the end of Kite's story. It seemed like I would either keep running it indefinitely, or perhaps lose interest. (Or funding -- it's eaten a lot of cash over the years, especially before the current days of $5/month VPS hosting.) But I failed to anticipate what seems to really be happening to it. Just as I didn't fathom, when kite was perched under my desk, that it would one day be some virtual abstract machine in a unknown computer in anther country.

Now it seems that what will happen to Kite is that most of the important parts of it will split off into a constellation of specialized servers. The website, including the user sites, has mostly moved to branchable.com. The DNS server, git server and other crucial stuff is moving to various VPS instances and containers. (The exhibit above is just one more automatically deployed, soulless container..) A large part of Kite has always been about me playing with bleeding-edge stuff and installing random new toys; that has moved to a throwaway personal server at cloudatcost.com which might be gone tomorrow (or might keep running for free for years).

What it seems will be left is a shell box, with IMAP access to a mail server, and a web server for legacy /~user/ sites, and a few tools that my users need (including that pine program some of them are still stuck on.)

Will it be worth calling that Kite?

[ Kite users: This transition needs to be done by December when the current host is scheduled to be retired. ]

Categories: Elsewhere

Acquia: DrupalCon Training with the Acquia team! UX and Security

Planet Drupal - Thu, 10/04/2014 - 16:02

The Acquia team is getting ready for DrupalCon Austin. We're excited about the official announcement of training at DrupalCon which is held on the Monday before the conference on Monday, June 2. We have two courses on offer which we think you'll love. One will get you started evaluating your designs with users, and how to conduct usability testing. One will help ensure your site or application is secure which is increasingly important for sites of all sizes.

Categories: Elsewhere

Craig Small: WordPress update needed for stable too

Planet Debian - Thu, 10/04/2014 - 15:10

Yesterday I mentioned that wordpress had an important security update to 3.8.2  The particular security bugs also impact the stable Debian version of wordpress, so those patches have been backported.  I’ve uploaded the changes to the security team so hopefully there will new package soon.

The version you are looking for will be 3.6.1+dfsg-1~deb7u2 and will be on the Debian security mirrors.

Categories: Elsewhere

Code Karate: Responsive Navigation Module

Planet Drupal - Thu, 10/04/2014 - 14:22
Episode Number: 142

In this episode of the Daily Dose of Drupal we go over the Responsive Navigation module. This module can be used to make your Drupal menu "responsive" so that it displays nicely on mobile and tablet devices. If you are trying to build a responsive Drupal website or a responsive Drupal theme, this module can help.

Tags: DrupalContribDrupal 7Drupal PlanetUI/DesignResponsive Design
Categories: Elsewhere

Blair Wadman: Top 10 Drush commands - follow up

Planet Drupal - Thu, 10/04/2014 - 13:54

I recently posted my top 10 Drush commands. In the blog post comments, over email and Twitter, a bunch of people let me know their top commands and tips. This was such great feedback, I decided to write up the list as another post. Here is the top 10 Drush commands from the fine folk who contributed.

Tags: DrushPlanet Drupal
Categories: Elsewhere

Michal Čihař: Heartbleed fun

Planet Debian - Thu, 10/04/2014 - 10:00

You probably know about heartbleed bug in OpenSSL as it is so widespread that it got to mainstream medias as well. As I'm running Debian Wheezy on my servers, they were affected as well.

The updated OpenSSL library was installed immediately after it has been released, but there was still option that somebody got private data from the server before (especially as the vulnerability exists for quite some time). So I've revoked and reissued all SSL certificates. This has nice benefit that they now use SHA 256 intermediate CA compared to SHA 1 which was used on some of them before.

Though there is no way to figure out whether there was some information leak or not, I have decided to reset all access tokens for OAuth (eg. GitHub), so if you have used GitHub login for Weblate, you will have to reauthenticate.

Filed under: English phpMyAdmin Weblate | 0 comments | Flattr this!

Categories: Elsewhere

Andrew Pollock: [life] Day 72: The Workshops, and zip lining into a pool

Planet Debian - Thu, 10/04/2014 - 06:38

Today was jam packed, from the time Zoe got dropped off to the time she was picked up again.

I woke up early to go to my yoga class. It had moved from 6:15am to 6:00am, but was closer to home. I woke up a bunch of times overnight because I wanted to make sure I got up a little bit earlier (even though I had an alarm set) so I was a bit tired.

Sarah dropped Zoe off, and we quickly inspected our plaster fish from yesterday. Because the plaster had gotten fairly thick, it didn't end up filling the molds completely, so the fish weren't smooth. Zoe was thrilled with them nonetheless, and wanted to draw all over them.

After that, we jumped in the car to head out to The Workshops Rail Museum. We were meeting Megan there.

We arrived slightly after opening time. I bought an annual membership last time we were there, and I'm glad we did. The place is pretty good. It's all indoors, and it's only lightly patronised, even for school holidays, so it was nice and quiet.

Megan and her Dad and sister arrived about an hour later, which was good, because it gave Zoe and I a bit of time to ourselves. We had plenty of time on the diesel engine simulator without anyone else breathing down our neck wanting a turn.

The girls all had a good time. We lost Megan and Zoe for a little bit when they decided to take off and look at some trains on their own. Jason and I were frantically searching the place before I found them.

There was a puppet show at 11am, and the room it was in was packed, so we plonked all three kids down on the floor near the stage, and waited outside. That was really nice, because the kids were all totally engrossed, and didn't miss us at all.

After lunch and a miniature train ride we headed home. Surprisingly, Zoe didn't nap on the way home.

Jason was house sitting for some of his neighbours down the street, and he'd invited us to come over and use their pool, so we went around there once we got back home. The house was great. They also had a couple of chickens.

The pool was really well set up. It had a zip line that ran the length of the pool. Zoe was keen to give it a try, and she did really well, hanging on all the way. They also had a little plastic fort with a slippery slide that could be placed at the end of the pool, and the girls had a great time sliding into the pool that way.

We got back home from all of that fun and games about 15 minutes before Sarah arrived to pick Zoe up, so it was really non-stop day.

Categories: Elsewhere

Christine Spang: a tuturial about search

Planet Debian - Thu, 10/04/2014 - 05:46

Today I gave a tutorial at PyCon 2014 entitled Search 101: An Introduction to Information Retrieval.

It was an experiment of sorts: the first workshop I've run primarily by myself, my first tutorial at PyCon, my first paid teaching gig. It was an opportunity to take some of the lessons I learned from teaching the Boston Python Workshop and apply them to a new situation.

The material itself is a distillation of many hours of frustration with the documentation for various open source search engine libraries, frustration that they didn't tell me where to start or about the big picture, they just jumped straight into the details.

Here's what worked:

  • IPython Notebook. Oh em gee. I started writing the class's handout using IPython Notebook because it was a simple way to easily embed syntax-highlighted code into a markdown document that was viewable in a browser. Not only was it a super quick and fun way to write the handout, but many students used the interactive execution features to play around with the example code.
  • Not having a paper handout. Saved trees, printing hassle, and no one seemed to mind.
  • Putting everything in a git repo... git is sufficiently ubiquitous these days that students didn't really have trouble getting a copy, and appreciated having everything in one place, with simple setup instructions. I brought a clone of the repo on a USB stick as a backup plan.

Here's what caused problems:

  • Mostly, the IPython dependency pyzmq, which requires compilation. I don't know what the current landscape is for Python distribution, but installing these libraries through pip is still a pain. I've heard rumour that more ubiquitous wheels may solve this in the future.
  • Some people aren't used to using virtualenv everywhere. Even seeing that, I still think it's worth the confusion to put it forth as the recommended setup method.

Intermediate students are a different crowd than beginners. There was less of an air of discovery in the room, though I organized the class around open-ended tasks. Since the material allowed for folks to take it in the direction of their interest, I found it a bit difficult to gauge whether people were following or not. Overall though, everyone was attentive and studious. I had fun.

Ruben and Stuart, the PyCon tutorial organizers, had logistics running super smoothly, AV, lunch, everything. Thanks for that you guys, you rock. And thanks as well to my helpers: Leo, the tutorial host, Eben, my TA, and Roberto, on AV. It's impossible to pay adequate attention to 20+ people as a single person, couldn't have done a decent job without y'all.

Categories: Elsewhere

Steinar H. Gunderson: Movit 1.1 released

Planet Debian - Thu, 10/04/2014 - 01:15

I just released version 1.1 of Movit, my GPU-based video filter library. This is basically for two things: A bunch of accumulated small fixed and tweaks, and support for GLES 3.0 (think mobile).

So, what now? Well, perhaps unsurprisingly, releasing a library does not bring an army of interested developers to your door, so as a library writer, most of my time actually goes into projects further up in the hierarchy. In particular, when you start imposing unreasonable demands such as “working OpenGL” onto end users who like to use Gentoo but don't know how to install a package, there is some fallout.

However, it also exposes you to a lot of scenarios you never really thought about, which can be frustrating, but in the end also increases the quality and robustness of your code. In particular, I know there's some issue (probably in Kdenlive's Movit support and not Movit, though) where NVIDIA's OpeNGL drivers are much stricter than Mesa's with regards to multithreading, and it's damn near impossible to track down without having one in a desktop machine myself. (I have one in my HTPC, but it's Atom-based and only has the TV for monitor, so debugging there is something I'd rather not do.)

So, what's next? The answer is pretty simple: Probably a break. I have to go to travel now (vacation and work) for the next month or so, so I fear Movit will get less attention for a little while. Then again, it's in fairly good shape, so I'm not that worried that the world will be screaming for me when I come back. :-)

Categories: Elsewhere

Drupal Association News: Building the Future of Drupal

Planet Drupal - Thu, 10/04/2014 - 00:18

If Drupal adoption is going to increase, we’ll need to grow the community— and that means continuing to bring developers, web designers, and digital experts into the Drupal fold. For the finale of our series on Drupal training options, we spoke to several of the many experts in Drupal training, and wanted to share their thoughts with the community.

When it comes to increasing the amount of Drupal talent in the market, there are more options to learn the platform than ever before.

Categories: Elsewhere

Thorsten Glaser: Heartbleed vs. Startcom / StartSSL

Planet Debian - Wed, 09/04/2014 - 21:51

First of all, good news, MirBSD is not vulnerable to The Heartbleed Bug due to my deliberate choice to stick to an older OpenSSL version. My inquiry (in various places) as to what precisely could leak when a vulnerable client connected to a nōn-vulnerable server has yet to be answered, though we can assume private key material is safe.

Now the bad news: while the CA I use¹ and a CA I don’t use offer free rekeying (in general), a CA I also use occasionally² refuses to do that. The ugly: they will not even revoke the certificates, so any attacker who gained your key, for example when you have been using a certificate of theirs on a Debian system, will be able to use it (e.g. to MITM your visitors traffic) unless you shell over lots of unreasonable money per certificate. (Someone wrote they got the fee waived, but others don’t, nor do I. (There’s also a great Twitter discussion-thingy about this involving Zugschlus, but I won’t link Twitter because they are not accessible to Lynx users like me and other Planet Debian authors.)

① I’ve been using GoDaddy privately for a while, paid for a wildcard certificate for *.mirbsd.org, and later also at work. I’ve stopped using it privately due to current lack of money.

② Occasionally, for nōn-wildcard gratis SSL certificates for HTTP servers. Startcom’s StartSSL certificates are unusable for real SSL as used in SMTP STARTTLS anyway, so usage isn’t much.

Now I’ve got a dilemma here. I’ve created a CA myself, to use with MirBSD infrastructure and things like that – X.509 certificates for my hosts (especially so I can use them for SMTP) and possibly personal friends (whose PGP key I’ve signed with maximum trust after the usual verification) but am using a StartSSL certificate for www.mirbsd.org as my GoDaddy wildcard certificate expires in a week or so (due to the aforementioned monetary issues), and I’d rather not pay for a limited certificate only supporting a single vhost. There is absolutely no issue with that certificate and key (only ever generated and used on MirBSD, only using it in Apache mod_ssl). Then, there’s this soon-to-be tax-exempt non-profit society of public utility I’m working with, whose server runs Debian, and which is affected, but has been using a StartSSL certificate for a while. Neither the society nor I can afford to pay for revocation, and we do not see any possible justification for this especially in the face of CVE-2014-0160. I expect a rekey keeping the current validity end date, and would accept a revocation even if I were unable to get a new certificate, since even were we to get a certificate for the society’s domain from someplace else, an attacker could still MITM us with the previous one from Startcom.

The problem here is: I’d really love to see (all of!) Startcom dropped from the global list of trustworthy CAs, but then I’d not know from where to get a cert for MirBSD; Globalsign is not an option because I will not limit SSL compatibility to a level needed to pass their “quality” test… possibly GoDaddy, ISTR they offer a free year to Open Source projects… no idea about one for the society… but it would solve the problem of not getting the certificates revoked. For everyone.

I am giving Startcom time until Friday after $dayjob (for me); after that, I’ll be kicking them off MirBSD’s CA bundle and will be lobbying for Debian and Mozilla to do the same.

Any other ideas of how to deal with that? I’d probably pay 5 € for a usable certificate accepted by people (including old systems, such as MSIE 5.0 on Win2k and the likes) without questioning… most of the time, I only serve public content anyway and just use SSL to make the NSA’s job more difficult (and even when not I’m not dealing with any payment information, just the occasional login protected area).

By the way, is there any way to access the information that is behind a current-day link to groups.google.com with Lynx or Pine? I can’t help but praise GMane for their NNTP interface.

ObFunfact: just when I was finished writing this wlog entry, I got a new eMail “Special offer just for you.” from GoDaddy. Sadly, no offer for a 5 € SSL certificate, just the usual 20-35% off coupon code.

Categories: Elsewhere

Lucas Nussbaum: speedtest.net, or how not to do bandwidth tests

Planet Debian - Wed, 09/04/2014 - 21:23

While trying to debug a bandwidth problem on a 3G connection, I tried speedtest.net, which ranks fairly high when one searches for “bandwidth test” on various search engines. I was getting very strange results, so I started wondering if my ISP might be bandwidth-throttling all traffic except the one from speedtest.net tests. After all, that’s on a 3G network, and another french 3G ISP (SFR) apparently uses Citrix ByteMobile to optimize the QoE by minifying HTML pages and recompressing images on-the-fly (amongst other things).

So, I fired wireshark, and discovered that no, it’s just speedtest being a bit naive. Speedtest uses its own text-based protocol on port 8080. Here is an excerpt of a download speed test:

> HI
< HELLO 2.1 2013-08-14.01
> DOWNLOAD 1000000
< DOWNLOAD JABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFG

Yeah, right: sequences of “ABCDEFGHIJ”. How course, extremely easy to compress, which apparently happens transparently on 3G (or is it PPP? but I tried to disable PPP compression, and it did not see any change).

It’s funny how digging into problems that look promising at first sight often results in big disappointments :-(

Categories: Elsewhere

Acquia: Sensio Labs UK - Lessons and chances from Drupal 8 early adoption

Planet Drupal - Wed, 09/04/2014 - 20:02

Part 2 of 2 - I spoke with Richard Miller and Tom Kitchin, software engineers at SensioLabs UK and its parent company Inviqa respectively, via a Google Hangout on Air recently. Here, I learn the inside story on one of the first Drupal 8 sites online, www.sensiolabs.co.uk, what their goals were, how they built it and have kept it running since May 2013, and how Drupal 8 will change the way they design applications for clients going forward.

Categories: Elsewhere

Drupal core announcements: Help unblock Drupal 8.0-beta1 at the NYC Camp Drupal 8 sprint

Planet Drupal - Wed, 09/04/2014 - 18:42
Start:  2014-04-10 (All day) - 2014-04-12 (All day) America/New_York Sprint Organizers:  xjm Event url: 

http://www.nyccamp.org/event/d8-core-sprint

After three years of Drupal 8 development, we are finally closing in on a Drupal 8.0-beta1 release. Of about 150 critical issues that have blocked the first Drupal 8 beta release, only 32 beta blockers remain. Most of these remaining issues are too complex for any one developer to resolve alone, but we need help on numerous tasks that will accelerate them. Join us at the NYC Camp D8 Core Sprint to see firsthand the work that's in progress and contribute to our momentum. Look for the "IRL issue queue" on colored construction paper at the sprint. :)

(New to Drupal 8 or core contribution? Check out the Get Involved with Core sprint instead.)

Categories: Elsewhere

Pages

Subscribe to jfhovinne aggregator