LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-26-2017, 12:38 PM   #1
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2-Multilib XDM/FVWM3
Posts: 780

Rep: Reputation: 260Reputation: 260Reputation: 260
Jitsi or Wire - Which is using P2P and will install on Slackware Stable


I've been looking for an open-source replacement to proprietary Skype for video-conferencing. Since Skype v8 isn't building and working correctly on my stable install I'm looking elsewhere, which I probably should have done sooner. I've seen a number of articles that recommend Wire and Jitsi. I have been to both web-sites.

Jitsi: https://jitsi.org/
Jitsi's entrance web site is confusing, since they have Jitsi-Meet and Jitsi-Videobridge, while Jitsi Desktop (for Windows, MacOS, Linux, Android and iOS) is buried under a dropdown titled Jitsi Projects. Go to https://slackbuilds.org/repository/1.../?search=jitsiSlackbuilds.org for the Jitsi Desktop, or use sbopkg, sbotools. I used sbotools and it built and worked fine.
Jitsi Desktop is a frontend. Jitsi-Meet is a P2P and Jitsi-Videobridge is a bridging program on a centralized server(s). Jitsi-Meet also is started on the central server, and it also stays "semi"-connected in order to allow others to join the video-conference. A centralization and intrusion point passed as a feature (:. The only exception might be that the encryption is maintained and the bridge is simply rebroadcasting the stream, maybe... Jitsi SlackBuild is of the 2015 desktop version 2.8 which builds and installs on Slackware stable. Jitsi's latest version 2.10 from 2017 will build but then doesn't connect with your old profile and throws no error codes to figure out why (at least Google XMMP wouldn't connect after upgrade). Jitsi documentation is sparse and you can no longer use the Jitsi XMMP server as it is shut-down. I also saw notes that it isn't compatible with Google's XMMP any longer which might explain the connection problem with latest desktop, probably because Google has it's own videoconferencing with "Hangouts", which runs in Chrome and Chromium. With Jitsi you and those you want to convert must know what you are doing with protocols and new login names. I suspect that some users were on jitsi when it was compatible with Google XMMP, because they already had a google account and you only had to add a Google Talk connection under Accounts then you were good to go. In essence you were using Jitsi as a frontend to Google servers.

Wire https://wire.com/en/
Wire is another video conferencing program along the lines of Skype. Wire is available for Linux, Windows, MacOS, Android, and iOS. The download is on the home page above. Wire can also be run within a browser. Wire is P2P, no central servers are mentioned, other than to get and register a @username. Wire is built for those who believe their connections are private and should stay private. Wire has a Slackbuild https://slackbuilds.org/repository/14.2/network/wire/ which also works and installs. However, after installation I've been unable to start it without going directly to the link. The KDE menu simply pulls up wire.desktop but will not start it. After starting the program you are presented with the preference screen and a first time login, which is combined with a email confirmation to actually register. Wire is moving over to @usernames rather than emails and it allows you to change that after login as long as the new username is still available.
I found wire very straight forward and simple, very similar to Skype. Like Skype to get others to join you they must have a @username. Because no other family are on Wire yet I'm not able to see if they appear like Skype as on-line.

Wire is using fewer protocols than Jitsi, but that allows it to be more straight forward to non-technical types (for ex. the Windows, Mac, iOS user). I'm going to leave WIRE installed and see if I can get my kids and grand-kids to convert. I also plan to further explore the features, since my grandson really wants to share the desktop for chess games.

Hope I've presented features and installation correctly. If not please post corrections. Also if you experience is different please post here. Cheers BrianA_MN
 
Old 09-26-2017, 01:58 PM   #2
matusz
LQ Newbie
 
Registered: Feb 2013
Distribution: Slackware64-current
Posts: 19

Rep: Reputation: Disabled
There's also https://tox.chat/. Voice chat and instant messaging work well (I had some issues with group voice chat on qTox), I haven't tested video.
 
Old 09-26-2017, 04:51 PM   #3
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2-Multilib XDM/FVWM3
Posts: 780

Original Poster
Rep: Reputation: 260Reputation: 260Reputation: 260
Quote:
Originally Posted by matusz View Post
There's also https://tox.chat/. Voice chat and instant messaging work well (I had some issues with group voice chat on qTox), I haven't tested video.
I am specifically looking for a video-conferencing tool. Slackware already has Pidgin, KDE's Kopete, and Seamonkey's IRC clients included and they work just find. I don't know that qtox even supports video as cleanly and easily as Skype.
 
Old 09-26-2017, 09:38 PM   #4
drgibbon
Senior Member
 
Registered: Nov 2014
Distribution: Slackware64 15.0
Posts: 1,217

Rep: Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942
Another possibility is Jitsi's web service: https://meet.jit.si/

The advantage is that there's no new software to install, everyone just visits the URL of the room. Might not suit your needs though.
 
1 members found this post helpful.
Old 09-26-2017, 09:43 PM   #5
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
A centralization and intrusion point passed as a feature (:.
You have to provide a way to get past the firewalls that almost everyone should have in place by now as well as a way for other people to find you. (I used to work in this field at Nortel Networks.)

The Wikileaks person uses Jitsi to communicate with people. Whatever you feel about him (and for the love of God don't use this thread to do so, pro or con), you can imagine that he takes his communications security pretty seriously.
 
1 members found this post helpful.
Old 09-27-2017, 10:45 AM   #6
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware64-Current
Posts: 871

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
Quote:
Originally Posted by bamunds View Post
However, after installation I've been unable to start it without going directly to the link. The KDE menu simply pulls up wire.desktop but will not start it.
Hope I've presented features and installation correctly. If not please post corrections. Also if you experience is different please post here. Cheers BrianA_MN
You need to edit the desktop file. I did and it works fine now

Change
Code:
Exec="/opt/wire-desktop/wire-desktop" %U
to read
Code:
Exec="/opt/Wire/wire-desktop" %U

Last edited by Gordie; 09-27-2017 at 10:49 AM.
 
Old 09-27-2017, 03:14 PM   #7
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2-Multilib XDM/FVWM3
Posts: 780

Original Poster
Rep: Reputation: 260Reputation: 260Reputation: 260
Quote:
Originally Posted by Gordie View Post
You need to edit the desktop file. I did and it works fine now

Change
Code:
Exec="/opt/wire-desktop/wire-desktop" %U
to read
Code:
Exec="/opt/Wire/wire-desktop" %U
@Gordie, thanks it works. I hadn't had a chance to check what was happening when I was writing the update.
What I actually did was as root open /usr/share/applications/wire.desktop and make the change you suggested PLUS change to icon=/opt/Wine/resources/app/img/wire.png which should also address the Icon for the desktop file. I'll also send this to the slackbuild package maintainer.

I also want to let everyone know that when you are ready to start a video call, all you do is tap the small person image in the lower right and then search for a name and you'll be presented with many matches. In my case there were many Brianxxx numbers.

@Richard Cranium Do you want to correct anything that I've stated about the centralization issue? My understanding is that Wire only sends you the IP connection cached number of the user you wish to conference with and otherwise stays out of the actual connection. Do you know differently?
Your comment about jitsi is a little debatable, only from the aspect that I don't believe Wire has been available as a release for as long as Jitsi and was perhaps not available three years ago when more secure video was being looked for, just maybe.
 
1 members found this post helpful.
Old 10-02-2017, 03:40 PM   #8
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2-Multilib XDM/FVWM3
Posts: 780

Original Poster
Rep: Reputation: 260Reputation: 260Reputation: 260
Closing as solved, since no comments in last five days.
 
Old 10-02-2017, 03:49 PM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by bamunds View Post
@Richard Cranium Do you want to correct anything that I've stated about the centralization issue? My understanding is that Wire only sends you the IP connection cached number of the user you wish to conference with and otherwise stays out of the actual connection. Do you know differently?
Your comment about jitsi is a little debatable, only from the aspect that I don't believe Wire has been available as a release for as long as Jitsi and was perhaps not available three years ago when more secure video was being looked for, just maybe.
Did you open a hole in your firewall to let someone in to connect to you? tcp/5061 or tcp/5060?

If you didn't then you are very probably talking to the server where you registered (since most firewalls allow you to create new outbound connections) which in turn knows how to connect the person who wants to talk to you to the pipe you used to get there.
 
Old 10-02-2017, 08:09 PM   #10
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2-Multilib XDM/FVWM3
Posts: 780

Original Poster
Rep: Reputation: 260Reputation: 260Reputation: 260
No I didn't open a firewall opening. However, I did run a few quick "ss" and did not see any tcp or udp connection to any remote hosts while WIRE was running and without a connection to another users. Is there another test you'd like me to process to confirm the "no connection" when waiting for one?
 
Old 10-02-2017, 08:56 PM   #11
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by bamunds View Post
No I didn't open a firewall opening. However, I did run a few quick "ss" and did not see any tcp or udp connection to any remote hosts while WIRE was running and without a connection to another users. Is there another test you'd like me to process to confirm the "no connection" when waiting for one?
Not really, but how do you think the connection is made? (BTW, you don't have connections with UDP; it's a connectionless protocol.) You are going to have to open a hole in your firewall to allow traffic to pass; normally that's done by either
  1. You open a port in your firewall to allow traffic in.
  2. You set your firewall to allow you to connect out to anywhere you want.

If it's the second one and the person you want to talk to is doing the same, then both of you need to talk to someone who's done the first one and knows how to connect you two together.

If you are running a firewall somewhere, you should check it to see if it allows traffic through 5060 or 5061 (assuming that wire uses SIP).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
What is more stable: Slackware or Debian Stable ? Xeratul Slackware 100 11-14-2015 10:07 PM
LXer: How to install Jitsi in Fedora LXer Syndicated Linux News 0 04-07-2012 01:10 PM
LXer: Install Jitsi 1.0 in Debian, Linux Mint and Ubuntu LXer Syndicated Linux News 0 04-05-2012 08:10 PM
How do I Install Lime Wire? applefox Linux - Newbie 5 03-22-2009 09:18 PM
Help Trying To Install Lime Wire lil213 Linux - Software 4 05-10-2004 11:36 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:11 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration