bradleydwyer
Instead what I'd think I'd like is just the risk assessment to be be performed by a third-party when I'm handling authentication (i.e. a third-party that has a broader view of what's happening across multiple services over time). I just send the pieces of information that I'm willing to share as an API call and they make the best risk assessment they can.
Then I can take that risk assessment result and make a final decision if authentication succeeds or not.
For example, I'd like to find a set of 3 locations across 3 providers that have the lowest latencies between them.
I live in such a house, nearby in Kedron, and we're considering doing just that.
One day I hope to see a comparable service emerge. Until then the only semi-comparable and cost effective solution is a self hosted Jenkins.
(although I'd love to be proved wrong)
I won't call it a resolution, but I will read through as many as I can this year (there are a lot)
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.
I meant to drop you guys a message a while back, but just never found a moment to do it.
There was a redesign a few months ago, notably this was when the camera became inactive if you were alone in the chat room. The issue with the busy state is, prior to this software release/version the busy flag was never removed unless you removed it or initiated a chat (after you accept the ping).
After the redesign, the busy flag was removed when any of the following conditions occurred:
1. You manually removed the busy flag.
2. A video chat is initiated (you are pinged and accept the call)
3. You became the only person in a chat room.
As I mentioned, it's been about 2 months since I last used Sqwiggle, so I'm not sure if the above is still true.
The changes meant that:
1. You can prevent somebody initiating a video call by setting your status to "busy".
2. The busy flag is removed when you are the only person in the chat room.
3. The camera indicator is disabled when nobody else is in the chat room.
4. You don't accept incoming video chats, they happen automatically.
Given that I mostly used Sqwiggle in a browser tab it was very easy for me to lose track of that fact it was running. It's one of many tabs and there is no indicator my camera is active if I'm alone. I typically have headphones in too but don't always wear them, so there is often no audio cue that a chat just initiated.
This is actually something that happened. I had an active call for 3.5 minutes that I was completely unaware of with video and audio streaming to the remote caller without my knowledge, after I had set the busy flag.
I work at home, and the ability for somebody to have a live audio/video stream into my house without my permission is unsettling. Especially as the only protection mechanism I have for that is to remember to terminate the application or close that browser tab every time I walk away from the computer or want to prevent video/audio sessions.
It's been a couple of months now since I last used Sqwiggle, so perhaps the clearing of the busy flag has reverted back to earlier behaviour, but ultimately I think unless I can change my profile to prevent automatic connection of video calls I'd never be comfortable with it.