Live data from Hacker News

Building a walkie-talkie for remote work

pragli.com

151–160 of 168 posts

Re: Building a walkie-talkie for remote work

#151
post #53

Earlier quoted context omitted.

Yeah I saw that but it's not as fluid yet. I am thinking of 3d faces with realistic facial texture and expressions. Btw, nice product!

Oh yeah that would be awesome... I definitely think that's the future

You note in the article that the detection occasionally causes some lag in your overall application. Have you looked into a background worker for the task?

Re: Building a walkie-talkie for remote work

#152
post #45

Earlier quoted context omitted.

I'm trying to convince my team to adopt a opt-in, voice only watercooler like that for some time, without success so far. I makes a lot of sense to me, who have been doing this for over a decade with my friends. Are you busy, don't join / mute yourself / go to the afk channel. Are you waiting for a long build, just reading HN, between tasks? Join the channel and people can bond and talk about work/life.

Do you know a voice chat like this where I could get real-time information whether or not someone is there without having to join? We use Hangouts and WhereBy (formerly appear.in) for some projects, but when you're in the "about to join" screen, the list of other people in the room isn't updated past initial load.

Yes, mumble has an API that can provide that info without having to join.

Re: Building a walkie-talkie for remote work

#153
post #128

My business partner and I have been working remotely with each other for the last 5 years, after a previous 7 years in a shared office. To make it work, we bought dedicated iPads and put them on stands next to our computer monitors on our desks. We start a FaceTime call at the beginning of each day and literally leave it running all day. We mute when not actively talking, so we can listen to music (and not listen to…

If every broadband connection had its own public IP, that would be trivial to implement in a point to point way using any IP phone software out there (linphone for example) without any need for a central server. IPv6 once widely implemented might solve the problem, since new fixed IPv4 addresses are unobtanium for non corporate networks; I'm not holding my breath though.

> IPv6 once widely implemented might solve the problem, since new fixed IPv4 addresses are unobtanium for non corporate networks; I'm not holding my breath though.

I have this strange feeling that we (the general public) are, in some manner, being segregated away from full implementation if IPv6 for precisely this reason.

That the limitations of IPv4 have benefitted the centralization of our internet access; IPv6, due to its sheer size of address space, turns that space into a commodity that is easily shared. ISPs would (or should) cease to be "gateways" and instead become mere infrastructure.

Assuming efficient network bandwidth allocation, it would allow for easy p2p or "peering"-like arrangements, which isn't easy or as scalable with IPv4 today.

But of course, that isn't in their business interest.

I can't think of any reason why IPv6 isn't "fully deployed" today; I'm sure there's a lot of legacy hardware out there that doesn't support it, but I would think it would be a minority amount in the whole "grand scheme" of the internet. Certainly the "end points" - our workstations and phones and such - are all IPv6 capable today. There's no real good reason for the rest of it not to be - except for control over access.

Just my opinion, of course...

Re: Building a walkie-talkie for remote work

#154
post #151
post #53

Earlier quoted context omitted.

Oh yeah that would be awesome... I definitely think that's the future

You note in the article that the detection occasionally causes some lag in your overall application. Have you looked into a background worker for the task?

We actually discovered that the CPU increase was not caused by the detection, but rather by the CSS animation of the SVG moving around.

It turns out that the detection itself is very fast and lightweight, so there was no need to optimize (background workers would've been a good idea though).

We somewhat optimized the CSS animation, but it's still not where we'd like to be... if anyone on here knows how to improve CSS animation performance beyond dropping frame rate / shortening the animation, I'd love to know. Tried some obvious things (z index, will-change).

Re: Building a walkie-talkie for remote work

#155
post #110
post #105

Earlier quoted context omitted.

They also mention that what finally made it feel nice is automatically setting DND mode when there is a calendar event (including any “focus time” blocks you create).

A big problem is that many people will ultimately ignore DND anyway.

The caller cannot ignore it, it will simply cause audio to not be accepted automatically.

Re: Building a walkie-talkie for remote work

#156
post #145

Earlier quoted context omitted.

That would require a very special, intimate relationship with someone to work. There is no way I could have a random coworker/boss' mug staring at me all day to my left. I wouldn't even want that with my wife/girlfriend.

Do you have a private office at work? It is like sitting in the same pod as a teammate. But I agree you wouldn't want it with a wife and girlfriend. Could get awkward with them both there.

>Do you have a private office at work? It is like sitting in the same pod as a teammate.

And therein lies the problem: we should all have a private office wherever we work, preferably without crappy lighting and with suitable heat / cold temps and a comfortable chair and so forth. Instead we get open offices with the guy three feet away feasting away on his boogers all day and the guy next to us whose headphones leak noise everywhere.

This is such an issue for me that it is one of the top five reasons why I went freelance - so that I can work in enjoyable professional settings with good hardware.

Re: Building a walkie-talkie for remote work

#157
post #128

My business partner and I have been working remotely with each other for the last 5 years, after a previous 7 years in a shared office. To make it work, we bought dedicated iPads and put them on stands next to our computer monitors on our desks. We start a FaceTime call at the beginning of each day and literally leave it running all day. We mute when not actively talking, so we can listen to music (and not listen to…

That would require a very special, intimate relationship with someone to work. There is no way I could have a random coworker/boss' mug staring at me all day to my left. I wouldn't even want that with my wife/girlfriend.

> I wouldn't even want that with my wife/girlfriend.

My partner moved in full time last year, such that we now share an office in addition to the rest of the house. We're coping, but it is honestly more problematic than I expected as we both are on the phone part of the day and need focused work time at other points. A 1984-style telescreen of some remote colleague staring at me all day work drive me nuts, but more power to the parent poster if it works for them.

Re: Building a walkie-talkie for remote work

#158
post #143
post #21

I have worked remotely for 10 years and raised VC funding for an idea very similar to this in the past – we failed to build a sustainable business, although the product did have a couple of hundred teams that swore by the product. In hindsight I believe it's because we were following the startup mythology of "building a solution for the problem that you have" a little too closely. We failed to realize that this is re…

We used Squiggle for a little while and really really wanted it to work for us. But the audio and video quality (and connection reliability) was just not nearly as good as FaceTime, and we were/are a two-man team, so we just switched back to FaceTime. I actually think Squiggle 2.0 but with the reliability and audo/video quality of FaceTime would be a different proposition. Audio feedback, background noise, broken con…

Indeed, AV is _hard_ – just look at how much people continue to complain about Google Hangouts despite all the resources they have. Quality of connection beats everything else which is probably why Zoom made it to IPO despite terrible UX

Re: Building a walkie-talkie for remote work

#159

Earlier quoted context omitted.

This is very common in some industries to have always-on two-way screens connected to workers in another office. A company called Tandberg was the main maker of them. It’s owned by Cisco now but everyone still calls them Tandbergs. Typically you would have one at the end of a row of desks to “extend” that row to another row physically located in another office and vice versa

That doesn't sound bad at all. Having a webcam pointed at my face all day and showing on some monitor would be very discomforting.

Set it up right and you could look all the way around the globe at the back of your own head :-)

Re: Building a walkie-talkie for remote work

#160
post #137
post #121

Earlier quoted context omitted.

I'm not an extrovert and I'd like this for people asking me questions. Want to disturb me for 2 minutes and ruin my concentration losing me half an hour? If it's going to save you your afternoon - just do it. If you're probably going to send me a message on slack or call me there anyway I'd find this a lot less annoying. My goal should never be to get through the most work myself it's to move the company forwards. Ha…

> If it's going to save you your afternoon - just do it. That's the thing, will it actually be used like that? This feel so casual that it doesn't feel like it has to be used in urgent matter only. I guess the important thing isn't about the tools but mostly about the training the user got around the tools. It's important to show what each one is used for and in which context. It's so easy to just believe something i…

I think the key thing is that tools won't make people good at communicating. That needs to happen as either a life lessons or job training.

Something tooling can do though is help give cues. If I'm wearing headphones in an office frowning at the screen that's likely to change how people come up to me compared to if I'm clearly having a break. When remote those aren't around so you can't tell if I'm knee deep in diagrams and code or (say) hitting unsubscribe from as many emails as I can. Making those things clear to others is something tooling can improve on - but there's not much that can stop people contacting you if they're determined.

Post reply on HN