Notices tagged with webrtc

@wyatwerp like the author said, FOAF was a product of a time when it was normal for most web users to have personal and professional homepages. I can't see how it would be helpful for chat, maybe for finding the chat address of a user by entering their email address or homepage? But you'd still need a chat app using a realtime protocol like #IRC, #XMPP, #Wave, #Matrix, or #WebRTC.
(1/2)
@alcinnz

@Blort the only thing that worries me about NextCloud Talk is it uses #WebRTC and works in-browser, so it might suffer from the same issues as #JitsiMeet, #PalavaTV etc. On the WebRTC stacks I've tried, you need a fairly late model computer and a pretty fast internet connection to get them to do anything beyond text chat.

@dyamon
> i don't seem to be able to fully understand what #jitsi #videobridge is.

Here's how I understand it. A #WebRTC server performs the initial introductions between peers who want to chat, then gets out of the way and lets them chat peer-to-peer. But if it's a video chat, between 3 or more peers, that's a lot of video streams being sent by each peer to all the others. So #VideoBridge relays the video stream sent by each peer to all the other peers.

(Feel free to correct me on this!)

@ohyran @dyamon Jitsi, like most #WebRTC stacks, leans heavily on the client-side computers. The #VideoBridge helps share the load of the streaming video to some degree, but it's not really practical on older computers, and I'm not sure how well it handles mobiles. If you've all got reasonably recent 64-bit hardware (I'd say less than 5 years old), it could work for you. I don't think it supports any encryption, but you could self-host to reduce your visibility compared to the hosted service.

@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

@clacke group chat is all #JitsiMeet does. The voice/ video uses #WebRTC and their own #VideoBridge software. It's a totally separate thing from the #Jitsi #XMPP client. AFAIK it doesn't support XMPP and if it supports #SIP that's news to me.
@xj9

@wiktor What I'm wondering is, why does #RocketChat not implement XMPP? As least as a plug-in, as they do with their #WebRTC support. In fact, imagine the net effect all the projects listed here would have it they all did the same (the ones that haven't that is):
https://www.coactivate.org/projects/disintermedia/slacking-off/
@jcbrand @stevenroose

@skipfordj @jcbrand
> after GTalk/Hangouts/Whatever goes away

I thought #GTalk was already dead, and that #Hangouts never supported #XMPP, because it's not compatible with what they wanted to do with #WebRTC. Was I wrong? In either case, yes, you can definitely carry on using XMPP withou gOgle. There's a list of suggested servers discussed here:
https://ecodigital.social/@adfeno/101232941345420566

@djsumdog yes, that's currently how WebTorrent works, a mash-up for #BitTorrent and #WebRTC protocols. There has been some discussion of implementing a fallback using #WebSockets, particularly in the context of making it easier for desktop torrent clients to support WebTorrent swarms.

@js technical question; does #Jingle work a bit like #WebRTC? What I mean is, does the server using Jingle help the two clients handshake, then leave them to send voice/ video packets directly to each other?

@LinuxSocist @LibertyPaulM the only downside is that your PC needs to be powerful enough to work smoothly with #WebRTC, which #WebTorrent uses to do in-browser BitTorrent. My old lappy usually can't handle WebRTC stuff :( But the PT devs are really cool and doing everything they can to improve performance for as wide a range of devices as possible.

@lightweight I've had a few plays with Jit.si, turns out my poor old PC can't handle anything that relies on #WebRTC (can't play #PeerTube videos either so I presume it's that). Would love to try chatting on #Wire though. I've tried text chat on the web app, but I'm planning to install the beta desktop app, and hoping my PC can cope with at least a voice chat ;)

@ignitionigel that was meant to be *shameless* self-promotion, oops! Anyway, I've been looking into this for a while, as I'd love to have Skype / Hangouts replacement for talking to my family back home, and #WebRTC stuff (eg Jitsi Meet) is too CPU heavy for my poor old netbook. At present I'm leaning towards #Wire so I can install desktop client but family can use web app.

Hey @lightweight have you heard of anyone using #RocketChat as a web client for a private Mumble server? It just occurred to me that this is a potential solution to both a) #WebRTC being an uber resource hog and b) geeky IRC-like Mumble UI

#Angular and #WebRTC, all the downsides of running a desktop client, and doing all the processing on the client end, without any of the benefits of better performance and greater configuration freedom. Yay #JavaScript!

@Shufei @david_ross would be good if #WebRTC can be turned on and off as needed, with the user explicitly giving permission for each site trying to us it, like #Firefox does with cam and mic

@lnxw48a1 ok. #Wire keeps coming up. Definitely going to try it next, as #WebRTC stuff in the browser just isn't going to work on this PC

@david_ross @Shufei I've initiated a community discussion in the #Trisquel forums about the implications of endorsing free code software that depends on #WebRTC
https://trisquel.info/en/forum/webrtc-and-browser-security