|
|
|
|
|
|
by spectre256
4545 days ago
|
|
|
Both the author of this post and the commenters here are correct for taking note of the privacy implications of Sqwiggle, but to completely dismiss the entire product seems to be both silly, and missing the point. Proclaiming "I won't use Sqwiggle because then people could see me" is exactly the same as saying "I won't work at my desk because people can see me". Both traditional offices and Sqwiggle allow one to achieve privacy if they'd like. For an office, you go into a conference room or something similar. To achieve the same effect with Sqwiggle, you simply close the program or browser tab. Sqwiggle's stated goal is to replicate the ease of determining colocated team members' status/activity when you are not colocated. No one is insisting you run it 24/7, just like no one insists you live your life at your desk at work. A very strange and dismissive article overall. The paragraph starting with "I don’t think Sqwiggle will be around long though" seemed especially cynical. |
|
|
I don't really see my comments as silly. I work for a startup and Sqwiggle was used exclusively while I was in my home. Apart from completely terminating the application/tab I had no way to prevent a live video and audio stream that happened to be able to look into my living room and pick up audio from anywhere in my house (it's a small house).
It wasn't 24/7 but the team did have a strong insistence that it be running while working and that is somewhere between 12 and 16 hours a day, 6 days a week.
That's not much private time in my home for me or the rest of my family. I liked the product and a few tweaks would probably make it acceptable to use.
Fix the busy flag clearing and allow my profile to disable auto video call connection. The other strategy that might solve it while keeping the spirit of instant chat would be to default to the busy state and have a timed non-busy state. e.g.:
/Here 3H
Which disables the busy state for 3 hours.