It feels like this is more about "how working across timezones fails in practice, for this team".
"From 9-10am, I was often unable to work much because the team was on lunch."
I don't understand why the team being at lunch would cause someone to stop working..
They wont allow a single account to be part of multiple teams. For each client I guess I have to create a new DO account, less than ideal. But still better than before.
Wow I started to read this, then started thinking oh just another "leave me alone while I program" post from 5 years ago.
After reading the comments here I went back and read the complete post. Glad I did. That was a great way to describe how interruptions kill the processes.
Why do FreeBSD users always have to 'defend' their choice. I wonder if every time someone tells me that they run some distro of Linux I should ask them why they don't use FreeBSD.
I don't have access to a system with the root kit, but something like comparing the reported size of the file and the number of bytes you can read might work
if ls -l /etc/rc.local | awk '{print $5}' != \
cat /etc/rc.local | wc -c
Also looks like you might be able to see it running with a ps also.
I think that is also why managers don't like off site employees.
Upper management might think a remote employee is the same as and outsourced Person.
And decide to outsource due to your successful remote employees.
Won't people just start creating 2 accounts. One with only "approved" content, then a second account where all their real friends are also connected via their second account.