qprimed

always cool to see routing by rumour in meatspace.

they are. props, however, for system76 branching out into their in-house hardware.

AFAIK, most of the community dropoffs are now coordinated with state and local relief. and yes - stay out of the areas, its a mess and coordination over the next few days rather than ad hoc scramble is what will save the most lives.

I have persoanlly heard a steady stream of millitary large transport helicopters over my area, so I know materials and personnel may be getting through.

this is not being discussed and actioned on nearly enough.

from friends in NC... and example of what is desperately needed in all affected areas. things are really, really bad. first aid kits are also in demand. at this point a cut can kill you.

wow! this must be the most "fuck you in particular" moment ever.

my undaeratanding is that lens material is so optically tuned for weight that removal of any amount of material makes a difference to the focusing - not to mention the possible coatings on the lens. this is what I have been told, I have no other evidence.

politics - americas original reality game show. they tune in for the lolz.

trump seems to have figured this out a while ago and managed to zombify 20% of the population, idiot savant style.

edit to say: a badly broken system allows a trump to threaten the rest of us.

happy that shes pounded on pads. not happy with that ring finger knuckle being involved.

that will work. always test your FW rules after a change. never just trust it.

netcat is your friend for a quick test to port 9050/TCP from a different PC if you are listening on more than just the loopback. careful with the loopback source addy AFAIK there is no guarantee that local host traffic to 127.0.0.1 will be sourced from 127.0.0.1 - I may be wrong here, but be safe.

regardless, depending on your rules, you will either get a timeout, instant connection reset or connect. obviously connect is bad if you think the traffic should be blocked, refusal is ok as long as the daemon is actually running (FW on a non-listening port can generate a TCP RST so its somewhat ambiguous), timeout is best as you know as long as the host is up, the FW is likely dropping traffic.

a more comprehensive test against any local host would be done with nmap.

sounds like you are poking things with a stick - thats awesome! happy to help :-)

edit: clarify loopback.

more than a few actors may (likely?) have very low yield devices. only takes a few to panic people and governments into stupid actions.

...and this ensures it will happen again. with greater magnitude. the machine needs more meat.