I ran through the instructions:
ps ax | grep weaved
2444 ? S 0:00 /usr/bin/weavedConnectd -f /etc/weaved/services/Weavedweb80.conf -d /var/run/Weavedweb80.pid
2493 ? S 0:00 /usr/bin/weavedConnectd -f /etc/weaved/services/Weavedweb8080.conf -d /var/run/Weavedweb8080.pid
2517 pts/0 S+ 0:00 grep --color=auto weaved
grep proxy /etc/weaved/services/*.conf
sudo netstat -apn | grep tcp | grep LISTEN
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1986/uv4l
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2353/sshd
WeavedConnectd built Feb 26 2015 at 10:53:39 Now Starting Up
Version 2.11 - (c)2015 Weaved, Inc. All Rights Reserved
Built with UPNP NATPMP ALIGN BCASTER MALLOC_POOL LINUX RESOLVE BIGBUF pool=262144
Weaved Development Kit Version based on Rasberry Pi Version
Running Weaved Network Diagnostics
Checking if DNS works ... .[OK]
Checking TCP connectivity to weaved.com... [OK]
Checking UDP connectivity to weaved.com...
Send to 18.104.22.168:5959  [mip=22.214.171.124] [oport=59612 mport=59612] [preserve port]
Send to 126.96.36.199:5960  [mip=188.8.131.52] [oport=59612 mport=59612] [no remap] [preserve port] [OK]
Checking if UPNP Router is found ... [FOUND]
Checking if NAT-PMP Router is found...[NOT FOUND]
This router preserves ports, this is optimal.
This router doesn't remap new connections to new ports, this is optimal.
UPNP is enabled on this router, this is optimal.
Static Pool Free
Endian : Little
SHA1 calculated is D29B143379C5F1E62CB89CE0B45246EE5CC4D3DA
Should Be D29B143379C5F1E62CB89CE0B45246EE5CC4D3DA
RC4 Calulated is 9A03817B144F1610AB94FDA75BD8
Should Be 9A03817B144F1610AB94FDA75BD8
XXTEA Calulated is 5164FC5FEA483B7158883A98277C2CCE
Should Be 5164FC5FEA483B7158883A98277C2CCE
Now, using Flask or any other RaspiCam program, I am able to access the camera through the UV4L interface on my LAN using raspiIP:8080, easily enough.
When I use Weaved, I can get to the interface as well... but the video stream shows up as a white screen. (The browser (Chrome or FireFox) has a spinning cursor as if it's trying to do something, but nothing happens.
I've checked if the port was forwarded properly and it can be seen by external sites.