Optimizing Vuze (formerly Azureus) for Speed


optimize-vuze-for-speed-Vuze-frog-icon-imageThis guide shows how to speed up downloads in the freeware bittorrent client,  Vuze.  All bittorrent programs need to have their incoming and outgoing communications flow freely in order to achieve the highest download speeds and that is essentially what this guide is about.

There are a series of guides for using torrents here at Gizmo's Freeware.  Vuze is one of the suggested bittorrent clients at Best Free Bittorrent Client.

See also How To Use Torrents for links to the other guides, and other helful software reviews, here at Gizmo's Freeware.

I assume that you already have the installer from the download link in the Best Free Bittorrent Client Review.  

If you do not have Vuze, you can get it from the

This guide was put together using information given by the developers of bittorrent programs at their forums, guides and FAQs.  There are no secret tricks, just the real basics of proper set up of a bittorrent program.  Following these simple steps should result in increased download speed.

These are the basic principles of optimizing a bittorrent client, like Vuze, for speed: 

  • Choose a proper port to avoid ISP blocks and conflicts with other programs
  • Forward that port through any software firewall and router to allow incoming connections
  • Adjust internal settings based upon upload capacity of the internet connection to allow room for outgoing communications and to distribute upload efficiently. 

There are some programs that claim to optimize speed in Vuze.  Such programs are a scam and generally contain adware or spyware.  I have seen it said, by the developers of all bittorrent programs, that nothing will increase your download speed in a bittorrent client more than the basic steps set forth herein.

If you are not using Vuze,  there are several other specific guides for other clients and a general guide here:
Optimizing Bittorrent Clients

Before starting the guide, in Vuze go to Tools>Options>Mode (Azureus>Preferences>Mode in Mac) and set to Advanced.


Choosing A Proper Port

To avoid messing up a network connection that is already cleared, first check and see if your communications are blocked or are already clear. 

Testing The Port

Vuze has a built in port test located at Help>NAT/Firewall test.  Before using this test disable and blocklist as the Vuze server is on some blocklists.

The test will show the TCP and UDP (they should be the same, but do not have to be) port already chosen for Vuze. You do not have to change to the port show in the images here.  You should test both the TCP and UDP, by pressing the Test button.  This image has the TCP result - you want to see OK.


This is the result that you want to see for UDP


 OK (Success)-just go to Adjusting Internal Settings.   Error- follow all steps.

If you failed the port test above, then you should first set your port to a proper one.  The most important choice here is to avoid using a port within the 6881-6999 range. This was the range originally used by bittorrent programs and is often blocked by Internet Service Providers (ISPs). (If your port was in this range, change and re-test).

The safest choice is a port in the 49160-65534 range as this will avoid ISP blocks and possible conflicts with other applications.  This range used to be 49152-65534, but apparently Vista and Windows 7 grabs some of those ports in between.   Vuze-Wiki: Port is Blacklisted

Windows users, if you want to make certain there is no conflict.  Go to the command prompt and type in netstat -a >c:\log.txt  This will check to see which ports are being used and save a log text file at C:\.  Looking at the text file, you will know which ports to avoid.

In Vuze go to Tools>Options>Connection.  Depending on your Mode setting, you may only see one number



Forwarding The Port

A router will block incoming communications unless an exception is made.  All software firewalls will block incoming communications and most will also block outgoing communications, unless an exception is made.  If you are "firewalled", then other people will not be able to initiate connections with you (see Why Is Being Firewalled Bad).
As there are many firewalls and routers, this guide can not give explanations as to each.  However, there are guides available, on the internet for most firewalls and routers and this guide will link you to them.

Software Firewall - The permission should be set to allow TCP and UDP in both directions.  Generally, you will have a choice to set permission for  the Vuze port or for the Vuze program.  Setting permission for the port is the very slightly safer choice.

If you are forwarding the port only, then you should also forward port 49001 UDP (the mainline DHT port) in addition to the main port above. You can check these options for guides:

Router - There are two choices here.  The easier way is to use UPnP.  However, this has a possible security issue.  Using UPnP allows any program to create a port mapping through the router without consent of the owner.  Note:  Given the recent findings of Rapid7 regarding security flaws in UPnP, it is generally suggested here that manual forwarding be used.  If you still want to use UPnP, then it would be a good idea to test and see if your device is vulnerable to attack through UPnP.

The other choice is to manually forward the port through the router.  This does not have that security issue, but involves going through several steps to accomplish.  Using the guides linked herein, this should not be that difficult and is the preferred method.

You should set a rule for the port number chosen above and then you should set a separate rule for Port 49001 UDP as this is the port that the mainline DHT uses. 

UPnP (NAT-PMP in Apple) - The Easy Way Enable UPnP (NAT-PMP for Apple) in Vuze and router.
Automatically refresh mappings when NAT status is "firewalled"  should also be enabled.



Manual Forwarding

  1. UPnP (NAT-PMP) must be disabled in Vuze (see Images above). 
  2. Use the Static IP Guide.
  3. Set permission for Vuze port you have chosen, This should be set to allow both TCP and UDP communications.. Port 49001 should also be forwarded, but  for UDP only.
    You can check these options for guides: 

Click Here to Re-Test Port    Success-Proceed to next step.   Error- re-do steps or seek help in Forums.

Adjusting Internal Settings

The  most important setting here is to cap upload in Vuze to 80% of your overall upload capacity.   Setting upload in Vuze is a fine line.  The more upload you give, the more download you will get from other peers. However, if upload is set too high, or to unlimited, then download speeds will suffer as outgoing communications (acknowledgment signals, resend requests etc) will be interfered with. Other adjustments are made here to distribute your upload so that you receive back the most download from other peers.
This section of the guide is based on the Vuze-Wiki: Good Settings page.

You should be in Mode = Advanced.as stated at the begining of this guide.

Speed Test: Speedtest.net (Click for Test)
First the upload capacity of your internet connection must be determined by taking an online speed test.  Speedtest.net has test locations worldwide and will highlight the one closest to you.
To take the test you must have Flash installed and javascript enabled.

Before taking the speed test, press Settings in the upper right of the speedtest.net page.  This will take you to another page.  At the bottom of that page is the "Global Settings" options.  Set "Speed Measurement" to kilobytes and press "Save" .  This will facilitate entry into the calculator below and will lessen confusion as qBittorrent shows speeds in kilobytes.





You should stop all internet activity, including torrents, before taking the test and the test should be taken a few times to obtain a reliable average. Results will now show in KiloBytes. It is the upload rate that is important here.


Another Way To Test Upload Speed
For most people these test results will be reliable (Comcast users see Note).  However, you may wish to do a double check on real life upload speed.  When you are seeding a torrent with a good number of peers and you are using your upload cap, set upload to unlimited and watch for about 5-10 minutes and see where upload settles in at.  Then input that number into the calculator in the kiloBytes section. 

Note:  Some ISPs will show inaccurate results on the speed test.  If your ISP has anything like Comcast's PowerBoost, then your results will show higher than the actual speed of your connection.  PowerBoost provides a burst of download and upload speeds above your provisioned download and upload speeds for the first 10MB and 5MB respectively.  Since the speed test involves relatively small files, this will skew results upward. 
If you have PowerBoost, or something similar, my findings from my own results and those of others is that the actual speeds are 60% of the test result.  So if you get 200kB/s for upload at the test, you should enter 120 in the kB/s box in the calculator.  Using Google ("speed result" x .6) will get the proper number to enter in  the calculator and this actually turns out to be very accurate.  You should end up with the calculator showing a cap that is about half of the test result.

Calculator Azureus Upload Settings Calculator
Once you have an average upload speed for your connection go to the online Azureus Upload Settings Calculator. Although designed for Azureus, this calculator will work for all bittorrent clients.
This calculator was created by the8472 a contributor to Vuze (fka Azureus) and part of the team that created Bittorrent Protocol Encryption.

Enter your average upload speed in the appropriate box


The calculator will automatically give the proper figures to adjust various options in µTorrent.


Input Results Into Vuze - Screen shots of locations in Vuze of settings to be adjusted

Tools>Options>Transfer            Azurues>Preferences>Transfer


Do not enable the "Auto" setting


Tools>Optoins>Queue                Azureus>Preferences>Queue


Peer Sources & Encryption

Having the proper peer sources enabled, such as Peer Exchange (PEX) and Distributed Hash Table (DHT), will help download speeds as they will help you find additional seeds and peers for a torrent. 
Encryption was primarily designed to thwart Internet Service Providers interference with bittorrent.  Having encryption enabled and allowing incoming legacy (non-encrypted) connections will provide you with the largest pool of seeds/peers to select from.

The settings for peer sources are at Tools>Options>Connection and should be set as in the below image:


The settings for encryption are at Tools>Options>Connection>Transport Encryption.  The settings shown in the image below will provide the highest encryption level and still allow connection with the most seeds/peers:


Mainline DHT Plugin

I now suggest the use of the Mailine DHT plugin in setting your Vuze up to get the best possible speed.  The DHT enabled in the step above is the Vuze implementation of DHT and is used by a minority of users.  The vast majority of users utilize the DHT implemented by µTorrent.  Installing this plugin will allow you to connect to both the Vuze DHT network and the µTorrent (or Mainline) DHT network.  This most likely will not make a difference on very healthy torrents, but on smaller torrent swarms may be a great help.

Since this guide is getting long enough, I decided to put the instructions for installation of this plugin on a separate page.  Please go to Vuze Help:  Installing The Mainline DHT Plugin for instructions.  It is a very simple installation process.

Good Torrents

The general rule here is to choose torrents that have a high seed to peer ratio. Seeds have 100% of the content associated with the torrent and are only uploading to peers. Peers also upload to other peers, but are also looking for other peers to upload to themselves and their download capacity is almost always higher than their upload capacity.

This applies even though one swarm has significantly more active users than another. For example, a torrent with 30 seeders and 70 peers (30% seeders) will generally be faster than one with 500 seeders and 2500 peers (20% seeders) as the average upload capacity available to the peers will be higher. (TorrentFreak).

For more information see Good Torrents

Related Articles

Gizmo's Best Ever Freeware Forums

If you still have issues after using this guide and would like some assistance, you may post here or our Forums.  The comments section here is not well set up for ongoing discussions, so the forums are a better place.

When posting on a speed issue, please provide

  • Your speed test result for both upload and download speed in kiloBytes per second (kBps)
  • Your result at canyouseeme, both before taking any steps and after.  Just indicate Success or Error do not post your IP address.

If you have a suggestion or correction for the guide, please post here.

Those who wish to post a thanks may post here or in the forums. I always appreciate hearing from those who this helped and I do read the posts regularly. I used to respond to each thanks, but realized it was clogging up the comments section. I thank all those who have posted their appreciation and all those who will.

So, to those who post a "Thanks", I appreciate it.



Share this
Average: 4.5 (277 votes)
Your rating: None


by Rajam on 9. May 2013 - 0:26  (107574)

This guide is great. My speed in a given torrent rised from like ~ 100 kb maximum to ~ 350 kb average. Thanks a lot!!

by Rajam on 9. May 2013 - 17:30  (107604)

mmm something weird happened to me now... yesterday I followed this guide and it worked wonders, but today, the smiley face is yellow again, speed cap back at ~ 100 kb/s, and when I do the NAT/Firewall test it throws errors... I tried changing the port (both in Vuze and forwarding it in the router configuration) and do the test again, but still the same... btw this is what the NAT/Firewall test says:

"Testing port TCP XXXXX ...
NAT Error - Connect attempt to yyy.yy.yyy.yyy:XXXXX (your computer) timed out after 20 seconds. This means your port is probably closed.

Testing port UDP XXXXX ...
Sending outbound packet and waiting for reply probe (timeout=5000)
Sending outbound packet and waiting for reply probe (timeout=10000)
Sending outbound packet and waiting for reply probe (timeout=15000)
Sending completion event
NAT Error. Inbound test failed, timed out."

Any help? Went throw the full guide again and idk what's wrong :(

by rockytt on 13. June 2013 - 13:19  (108503)

Feeling like an idiot, but can't get an open port.
Home DSL, so I should only have to configure my NetGear router. Followed steps (I think!) to open port 49388 (which I set on the Vuze program), as well as the router:
1) Add Custom Service
2) Firewall Rules > Add
-but still get that dreaded "timeout" when checking.
Any tips/hints/tricks??

by patlepiraat on 28. June 2013 - 17:48  (108785)

Keeps on having the same problem, Vuze is blocked now. I have the same msg:

Testing port TCP 49185 ...
NAT Error - Connect attempt to XXX.XXX.XXX.227:49185 (your computer) timed out after 20 seconds. This means your port is probably closed.

I followed the instuctions, have a list of Port numbers, how should I choose? These are the various types of output. Thx for any hint, I tried the combinations but gives same result.

TCP XXX.0.0.0:49155 Pat-PC:0 LISTENING
TCP XX.XXX.177.55:52227 baymsgr2011203:https ESTABLISHED
TCP XXX.0.0.1:24901 Pat-PC:0 LISTENING
TCP XXX.0.0.1:52265 Pat-PC:52266 ESTABLISHED
UDP *:*
UDP [::ffff:10.XXX.XXX.55]:54967 *:*

by mr6n8 on 29. June 2013 - 18:18  (108817)

What is important is whether exceptions have been made in the firewalls on your system for the port number chosen.

Have you set exceptions for Vuze, or its port, in the software and hardware (router), firewalls on your system?


by mr6n8 on 29. June 2013 - 18:21  (108818)

Sorry I was on the road when this was posted and unable to respond.

If you are still having issues (and get this reply), what is the model number of your Netgear?

Have you set exception in your software firewall?

It is also possible that the DSL hardware has a firewall built in. What is the make and model of this hardware?


by mr6n8 on 29. June 2013 - 18:24  (108819)

I am sorry for not getting back to this sooner. I have been on the road without internet access most of the time.

If you are still having the issue, the first thing that comes to mind when a router is involved and the connection was open and then closed, is that a Static IP was not set. If a static IP is not set, then the rule will become useless if the IP changes.

Did you set a static IP?


by Rajam on 29. June 2013 - 21:01  (108824)

Honestly I don't remember what I did, but I solved the issue somehow and I have a working Vuze now; thanks anyways :)

by mr6n8 on 29. June 2013 - 21:22  (108826)

That is good to hear (no matter how it got done).



by rockytt on 30. June 2013 - 15:46  (108845)

No worries Steve - appreciate the follow up!

Got a Netgear DGN-2200 and (AFAIK) set the exception properly for the firewall.

This piece is both Router and DSL modem, so I don't think that there's a second firewall hiding anywhere - yes?

by mr6n8 on 30. June 2013 - 16:06  (108847)

Looking at this guide at PortForward, it looks like you need to go to the Port Forwarding / Port Triggering link and select Port Forwarding.

The guide forwards port 6881, but you should use one of the ports within the range mentioned in this guide.

Also, be sure to set a static IP first.

Did you set exception in your software firewall (if any)?


by rockytt on 1. July 2013 - 17:28  (108876)

I thought I managed to figure it out - although my router/modem didn't have the same options as shown at portforward.com. (Supposed to click on "Port Forwarding / Port Triggering" - which wasn't even there!)
Went through "Services>Inbound Services>Add" and was able to enter the Static IP there. Applied the changes and now Vuze is downloading at 275 kB instead of around 60kB - which is a vast improvement.
However, an hour or so later I'm back down to 80 kB again -
When I run the NAT/Firewall test from Vuze I get a 'fail' and am told 'Connect attempt to 172.12.22.xx:xxxxx (your computer) timed out after 20 seconds. This means your port is probably closed" - The IP address shown isn't even in the same realm as the static one I setup.

I probably need to call NetGear and find out how THEY recommend someone do port forwarding since "Port Forwarding / Port Triggering" doesn't appear on my CP at all...

Thanks for your help Steve - much appreciated though!


ps - logs show "[DoS attack: TCP SYN Flood] multi-source syn flood attack in last 20 sec , Monday, Jul 01,2013 10:27:16" repeatedly does this make any sense?

by mr6n8 on 1. July 2013 - 21:53  (108892)

Was this provided by your internet provider? If so, it may have a different interface. Who is your ISP?

Does your screen match the one on page 21 of the user manual here?

Not sure where that log is from, but it most likely is just a result of the test attempting to get through (if the times match).


by rockytt on 1. July 2013 - 22:00  (108893)

It does match the one on the user manual - which is missing the "Port Forwarding / Port Triggering" link/option as described on portforward.com. http://portforward.com/english/routers/port_forwarding/Netgear/DGN2200/A...

by mr6n8 on 1. July 2013 - 22:40  (108894)

They have changed over at PortForward recently and I am not a big fan of the new look and it appears that their screens are outdated (or just wrong) in your case.

Anyhow, we can work through the manual now.

From what I see, you first have to create a service and then set an inbound and outbound rule allowing the service.

To set a "Service" for Vuze, see page 48. You can name the service "vuze" and allow TCP and UDP. The start and finish port should be the same port number you have chosen for Vuze.

Then go to page 44 to set up an outbound and then an inbound rule for "vuze". Basically the same info will go into both rules, enable = yes, service = vuze, action = allow always, LAN and WAN options = any, logging = never.

Also, I forgot to mention that the IP Vuze will return is your public IP that is shown on the internet. The Static IP is just between the router and your computer.

Hopefully, this will get you going. (fingers crossed). If not, then you can try UPnP (page 85) enabling on the router and in Vuze (see above).


by rockytt on 5. July 2013 - 14:41  (108996)

Thanks again for your help Steve - I think we've got it working as well as it can now with my (less-than-steller) ISP. Hitting speeds up to 200kBs, which is probably the best I can hope for these days.


by mr6n8 on 5. July 2013 - 18:57  (109000)

Well I hope it sticks this time.


by patlepiraat on 28. July 2013 - 9:12  (109691)

Thank you very much Steve and sorry for my late reply.

I have never done that an exception and I noted that "Windows Firewall cannot be started". It is probably my Bitdefender AV but never had issues before. I have set exceptions with the .exe files.

Will check again and revert

by mr6n8 on 28. July 2013 - 20:26  (109714)

Well if you need help, then post back.

But I think if you set the rules (exceptions), you will be OK


by VBR on 3. August 2013 - 10:30  (109880)

I have a windows Xp computer
i followed all the steps, but i have an external modem
do i still need to get a static IP address?

by mr6n8 on 3. August 2013 - 21:21  (109887)

What is your result on the Nat/Firewall test?

Have you set exceptions for Vuze in your software firewall?

Most modems do not have a firewall, but some do. If the hardwware has a firewall, then a Static IP would make it so you do not have to redo the rule in that firewall. The static IP is not necessary for a software firewall.


by VBR on 4. August 2013 - 15:57  (109894)

hi steve,

i really have no idea whether my modem has a firewall or not, but i have created exceptions for vuze in windows firewall.

i decided to re install vuze and do everything all over again.

my results on the NAT test for TCP and UDP after changing the port as stated were OK!

But even after creating an exception for port 49001 (UDP),and testing, the NAT test failed
It said that transport was unavailable.

Please help me solve my problems

Thanks in advance


by mr6n8 on 4. August 2013 - 18:30  (109897)

I have a feeling you are OK as is.

The 49001 is for the Mainline DHT. This is a plugin that is not included in the basic Vuze, you have to add it in. I have an article here on adding it in as I think it does help speeds (it is referenced at the end of this article):

Even if you have added the Mainline DHT plugin, there is no real way to test the connection. You just have to see if you get the kind of numbers connecting on the DHT network as set forth in that guide.

Since the other ports tested OK, there is no issue with the modem and no static IP is needed.

Did you set an exception for the program Vuze in the Windows firewall? or for the specific ports?

For a torrent to test down speed, you can try the main installer torrent for the free office suite LibreOffice. You should get up to your max within a couple of minutes:


by VBR on 5. August 2013 - 9:38  (109902)

Hi again steve

Thanks for the reply. I have encountered another problem.
I installed Vuze and followed the steps, after that, my download speed was about 20kb/s, which was previously 3.5-5kb/s.

every time i restsrt the computer, i test the listening ports again, but the TCP fails so i have to keep changing the listening ports each time. what should i do about this?

Also i could not get a static ip address because i dont have the numbers for the DNS servers.


by mr6n8 on 5. August 2013 - 12:39  (109912)

The port issue is a strange one. That is usually due to a hardware firewall and a dynamic IP (which is why an internal static IP is used for hardware firewalls).

As I understand it, you did not make any rule in the hardware (modem) and only in the Windows firewall.

How did you set the rule in Windows firewall - for the program Vuze or for the port Vuze uses?

Not sure what is going on here though.


by VBR on 7. August 2013 - 8:00  (109946)

Hello Steve,

My apologies for my delayed reply.
Thanks very much Steve, I managed to overcome these problems thanks to your help.
I finally managed to download a movie from VUZE, but it is a large movie and still needs to seed, but i am in urgent need to watch that movie. so i want to move it into my external hard disc, but it says that another program is using the file.

How can i stop the file from seeding in Vuze's user interface?


by itwontworkgrrr on 7. August 2013 - 16:21  (109954)

Hello, I'm using Vuze on XP, with Sky broadband (in England).
Vuze has worked with Sky on the same settings for over a year, but only in the mornings during the week. After about 5pm weekday or at weekends download speeds dropped from morning max of 650kB to almost nothing (flick up to maybe 1 or 2kB, then stop again).
Recently it's like that the whole time, almost no speed. I have torrents with many seeds and green smily face (sometimes, though it's always worked fine - if the face is green, yellow or blue). The NAT test is timing out on both TCP and UDP (port around 33500). I've sat and watched the peers, it keeps connecting to the same people over and over, but cuts off without ever reaching any speed.
Glasnost test says ports 6881 and 44350 are blocked, but I'm not using them.
Azureus/Vuze is set as an exception in Windows firewall.
Transport encryption is on, RC4. Turning it off doesn't make any difference.
Another piece of strangeness is that with Vuze running on my laptop, Firefox doesn't work. It takes minutes just to bring up Google search page, and most sites time out without opening. I have to close Vuze, and restart the laptop to get the internet to work again.
Also, for several months I can't access the Vuze.com or wiki.vuze.com websites. It just times out without reaching the site.
Has Sky just completely locked out Vuze? I accepted that P2P was throttled in peak times (evenings and weekends) before and just used it in the mornings, but I'm getting nothing now!
Any ideas? I've used Vuze for years and had very few problems, and always been able to fix any that did come up. But this has me stumped. I'm going mad here, coz I'm weeks behind on my favourite anime!!

by mr6n8 on 7. August 2013 - 17:04  (109955)

There are 3 options:

1) If you want to keep seeding, then you can just copy the movie over.

2) If your external HD is going to remain connected to the computer with Vuze, then you can move the content and continue seeding - right-click on the torrent in Vuze and select Advanced>Files>Move Data Files and browse to where you want to move.

3) To stop the torrent and move the movie, you can highlight the torrent in Vuze and press the "Stop/Start" button above the torrent library listings. On the latest version it is two arrows in a circle (next to the red X).
If you move the content out, then it will show as an error when you restart the torrent. You would have to move (or add) the content back in to continue seeding.

by mr6n8 on 7. August 2013 - 17:14  (109957)

I did some searching on this as I have not seen any Sky users complaining and I did not find any other users complaining (other that the fair usage/network management you reference).
That does not mean they are not doing anything, but it is not likely that they would be interfering as with you and no complaints at the Vuze fora or elsewhere.

Have you changed any hardware (modem or router) lately? security software?

You could try qBittorrent just to see if the issue is related solely to Vuze.

The page loading issue usually results from either too many open connections or too much upload being used by Vuze. Since your Vuze is not using bandwidth it might be connections. Anyhow, try with qBittorrent and see if you still have the issue. At least that way, we can try to narrow the possible reasons.


by itwontworkgrrr on 8. August 2013 - 14:59  (109985)

Thanks for the advice.
I haven't changed anything for security, I have AVG free 2013 and Spybot Hardware has been the same since I've been on Sky, a Sagemcom F@ST2504n router.
With Vuze, I never bothered with the static IP and port forwarding, because it has always worked fine without.
But I just installed qBittorrent, following the optimising for speed guide here, with static ip and manual port forwarding in the router software. It's still just the same, it connects to seeds, but never gets any speed and they cut off after a short while. Firefox is the same with qBit running, not working.
When I run the canyouseeme port check, I get a connection timed out message for any port I try, including my qBit forwarded one. (It was the same before changing any settings).
Dunno if it's normal, but the IP address the port checker website gives me is the one listed as 'broadband port' on the router, instead of my static one (that's listed in ipconfig now). Only the broadband port page had the DNS listed to put in for the static IP settings. Putting the broadband port IP into the router firewall rules instead of my static IP changes the port check error message to Connection Refused instead of timeout. Sorry if that's a stupid thing to try, this IP stuff is a bit over my head :o)

Gizmo's Freeware is Recruiting!

Gizmos Needs YouShare your knowledge of free software with millions of Gizmo's readers by joining our editing team.  Details here.