Hi Taylor,
You are right - development on libproxy has gone down badly and a new motivated maintainer is desperately needed.
Are you willing to step up here? There are ideas on what is still needed to be done (besides integrating it into more and more client tools of course).
The currently 'most critical' issue is the linking to Qt4: whenever an app is linked to Qt5 AND making use of libproxy, we have a library clash... so the idea would be to get the library on the dbus, out of the application process space.
Can we count on you? :)
Dominique