Notices tagged with ring, page 2

@kawaiipunk I've been thinking about these for years, like #Serval, #GNU #Jami (formerly #Ring), #Tox, and others. But I struggle to find people to test them with, and when a "secure" chat app only has clients for iOS and Android, I struggle to take them seriously.
@bob @gentoorebel @noorul

@bikecurious AFAIK #GNU #Jami (formerly #Ring) is a serverless/ #P2P app, not a #SIP client. However, I do seem to have a knowledge gap when it comes to the relationship between SIP and #WebRTC. Any good links for filling that gap?
@gentoorebel @noorul @fdroidorg @finn @clacke

@greenjon if you want a similar service to Signal that isn't US-based, is planning to implement server>server federation, and is more friendly to the software freedom movement, I suggest trying #Wire. #GNU #Jami (formerly #Ring) is also worth a try, but much less user-friendly (at least last time I tried it).

@switchingsocial I know you've addressed this in your FAQ but I really want to challenge not listing #Wire on your list of messenger apps. It's much easier for non-technical people to understand and use than #Jami / #Ring (I've got my family using Wire with me). Also, unlike Signal, Wire can be used without supplying a phone number, and they have plans to implement server>server federation:
https://github.com/wireapp/wire/issues/160#issuecomment-446551908

I wonder if #Bitmessage protocol could be used to implement offline text messages in #GNU #Ring?
https://github.com/Bitmessage

@clacke I agree with everything @sir says about #Signal, having come to pretty much the same conclusions reading most of the same old discussion threads he did. The only thing that makes my brow wrinkle is not suggesting #GNU #Ring along with #Matrix, and suggesting #Tox. Doesn't it have some unresolved security concerns?https://github.com/irungentoo/toxcore/issues/121

@clacke I agree with everything @sir says about #Signal, having come to pretty much the same conclusions reading most of the same old discussion thread he did. The only thing that makes my brow wrinkle is not suggesting #GNU #Ring along with #Matrix, and suggesting #Tox. Doesn't it have some unresolved security concerns?
https://github.com/irungentoo/toxcore/issues/121

Pre-Black Friday deal alert: #ring Video Doorbell 2 and Echo Dot for $140 #theverge https://www.theverge.com/good-deals/2018/11/19/18103207/best-buy-black-friday-deals-sale-ring-video-doorbell-2-free-echo-dot-2018

Anyone using #gnu #ring?

How has your experience been?

Ring’s new indoor and outdoor security cameras are its cheapest yet #theverge https://www.theverge.com/circuitbreaker/2018/9/20/17883394/amazon-ring-stick-up-cam-smart-home-security-cameras-price #ring

I figured out I'd accidentally followed the #Ring installation instructions for 18.04, not 16.04, so now Trisquel 8 is finding the files for install. But it seems to be having trouble actually getting them downloaded. Not sure if it's my network connection (location / speed), or the fact I'm browsing the #fediverse while trying to do the downloads.

@danyspin97 @TheOuterLinux
> In the end #Matrix still seems the most promising one to me, due to the presence of both a public community and a IM.

#Matrix is client/server, so quite a different beast from #Tox / #Ring, which are serverless. Matrix seems like a good candidate for replacing both #IRC and #Slack, given that it's federated by default (unlike IRC which needs a bunch of extra stuff to support federation), and it's an open protocol (unlike Slack which is a #DataFarm).

@danyspin97 @TheOuterLinux
> #Ring is really interesting, I've downloaded it but I've never tried it.

I've only used it once. The distro I have been using up until recently was too old to support it. Ring did a reasonable job of a one-to-one voice call (bit of echo at my end that I could work out how to fix), but it doesn't seem to support delivery of messages if the receiver was offline when it was sent. If you're keen to test, my Ring ID is 'strypey'

@danyspin97 @TheOuterLinux
As the TokTok devs make it clear, they know there are issues with the #Tox protocol, and have a plan to address them. They clearly state the limits of Tox on their TokTok website, and all the clients have "alpha software" disclaimers. Most of the projects the critics claim they should all work on instead of client/server, not #P2P. Tox, like #Ring or #Ricochet or #Briar, are attempting a totally different thing from #Signal / #Noise.

@TheOuterLinux @danyspin97 have you tried #Wire and #Ring? Wire relies on a centralized server, but Ring is #P2P (like #Tox). They're both #FreeCode and both work pretty well for text chat, one-to-one voice calls (although I had persistent echo on Ring the one time I've tesed it so far). I've also tested file-transfer and image sharing on Wire, which work fine. Haven't test conference calling or video chat on either yet.

I wonder if it would be possible for #XMPP clients to implement the #P2P voice/video calling protocols used by #Ring and #Tox? This might work better than the current solution(s), and take a lot of stress off the servers in the XMPP network.