Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Federated calls #21

Open
jancborchardt opened this issue Sep 20, 2016 · 19 comments
Open

Federated calls #21

jancborchardt opened this issue Sep 20, 2016 · 19 comments

Comments

@jancborchardt
Copy link
Member

@jancborchardt jancborchardt commented Sep 20, 2016

You should be able to call someone via federation through cloudname.com/username or something similar. Like on Spreed.me

@LukasReschke LukasReschke added this to the backlog milestone Oct 17, 2016
@jancborchardt jancborchardt modified the milestones: backlog, 1.1.0 Oct 17, 2016
@nickvergessen nickvergessen changed the title User links Federated calls Nov 22, 2016
@jancborchardt jancborchardt modified the milestones: 1.1.0, 1.3.0 Dec 13, 2016
@nickvergessen nickvergessen mentioned this issue Mar 27, 2017
37 of 59 tasks complete
@nickvergessen nickvergessen modified the milestones: 1.3, 3.0 (Nextcloud 13) May 22, 2017
@netluxe

This comment has been minimized.

Copy link

@netluxe netluxe commented Aug 9, 2017

Curious as to the progress/potentiality of this being integrated? What realistically would be necessary in order for it to work? Could a third-party integration (something akin to a security-hardening add-on like Google Authenticator or another TOTP provider for 2FA) plugin, setup strictly on a domain meant for linking participating separate nextcloud instances (i.e. nextcloudcalls.com or something like that) and write a script that generates an one-use authentication token upon the request to communicate via the video chat plugin? Kind of a trusted middleman service that facilitates the connection requests between the participants in a video or voice call. Would have to be something that kept the connection ultimately between the actual end-users' nextcloud servers themselves obviously.

There's a bunch of existing frameworks for videochat/voice chat, videochat + text-based chat simultaneously that shouldn't be too difficult to look into in terms of what might be best used to integrate into the existing architecture. Admittedly, I only recently deployed my own nextcloud server and have only had a few hours over the past couple of days to poke around the code. Been mostly busy setting up the essential stuff, and of course, transferring over a ton of files and obsessively setting up the filesystem/folder structure.

Anyway, just some thoughts. Will take a look on the nextcloud forums as well, perhaps I shall see some of you there (I'll have the same username) Cheers 👍

@nickvergessen nickvergessen modified the milestones: 3.0 (Nextcloud 13), 4.0 (Nextcloud 14) Nov 2, 2017
@nickvergessen nickvergessen added this to To do in October Release via automation Aug 8, 2018
@nickvergessen nickvergessen self-assigned this Aug 8, 2018
@klundry

This comment has been minimized.

Copy link

@klundry klundry commented Nov 15, 2018

This is great to see! Once implemented would federated messaging work as well?

@nickvergessen nickvergessen added this to the 💛 Following Major milestone Dec 7, 2018
@pwFoo

This comment has been minimized.

Copy link

@pwFoo pwFoo commented Dec 12, 2018

Federated Chat would bei awesome!

@mistergibson

This comment has been minimized.

Copy link

@mistergibson mistergibson commented Dec 21, 2018

This feature will be indispensable to a federation. Organizations can split up their servers by region yet have them all tied together in communications. Is it not in essence a binding to the user list at play here? Federated servers swap that data so it should be available to Talk. Really WANT this feature - kudos to those pushing for it. 👍

@mjjzf

This comment has been minimized.

Copy link

@mjjzf mjjzf commented Mar 7, 2019

I am thinking about using Chat in a Slack-style fashion - it then becomes very important to be able for an invited user to pick up from before and have unique ID on ongoing conversation.

@weiss

This comment has been minimized.

Copy link

@weiss weiss commented Mar 7, 2019

I'm trying my best not to troll this issue, but I really don't grasp why you'd reinvent features such as federation and history sync (which are anything but trivial to get right) rather than building on top of existing solutions which already solved these and other problems based on open standards.

@nickvergessen

This comment has been minimized.

Copy link
Member

@nickvergessen nickvergessen commented Mar 7, 2019

XMPP in PHP is far from trivial, but you can be sure it is one of the options on the plate while looking into this.

@poVoq

This comment has been minimized.

Copy link

@poVoq poVoq commented Apr 2, 2019

See headless ConverseJS for convenient Javascript only XMPP client library.

Movim.eu codebase might also be a good place to look for relevant php based XMPP code as it implements most of Talk's wanted features such as federated calls over XMPP / WebRTC.

@e-alfred

This comment has been minimized.

Copy link

@e-alfred e-alfred commented Apr 28, 2019

This is such an important feature for Talk because it enables people with their own Nextcloud systems to chat without the need to invite a guest using a public link or creating an account on the other system as well as preserving the chat log with each Nextcloud instance that is taking part of a call.

@derfabianpeter

This comment has been minimized.

Copy link

@derfabianpeter derfabianpeter commented May 18, 2019

Federating chat would be the go-to solution (besides Matrix) to re-think communication in larger enterprises and non-profits with complex organizational structures. Talk being able to have consistent, non-guest chats between different Nextcloud-Domains would basically end the stupid "What messenger to choose" conversation. For most people, Chat-Ops and all the stuff Slack does doesn't really matter. But being able to talk safely and first and foremost with low entry-barriers with other people also believing in Nextcloud being the best thing to run when it comes to data privacy - that would make a severe difference :) And it would help to migrate people to the platform. Chat is currently the only thing that's not living up to the decentralization-ideal. So just a bump to not forget this. Maybe this can be solved by integrating with Matrix as the underlying protocol and then just bridge with Talk internals.

@mwild1

This comment has been minimized.

Copy link

@mwild1 mwild1 commented May 20, 2019

If your goal is a "go-to solution" for federated communication between business, you can't tie such a thing to a single implementation. As much as we all like NextCloud, it needs to be possible for other projects to also support it which means it needs to be openly documented, and ideally openly developed too.

Such standard protocols already exist, Matrix and XMPP being great examples with numerous existing implementations. Projects such as Movim (also written largely in PHP) are good examples of this approach.

In reality if NextCloud grew a nice clean documented API for federated chat, Matrix and XMPP would probably grow gateways for it pretty easily.

@nickvergessen nickvergessen mentioned this issue Jun 26, 2019
@pwFoo

This comment has been minimized.

Copy link

@pwFoo pwFoo commented Jul 15, 2019

Talk federation chat / calls would be awesome

@pwFoo

This comment has been minimized.

Copy link

@pwFoo pwFoo commented Jul 17, 2019

Talk federation would be needed because of external contacts.

@nickvergessen

This comment has been minimized.

Copy link
Member

@nickvergessen nickvergessen commented Jul 17, 2019

Yes, thanks for your comments, we know the usecases for federation.
You can also upvote existing comments or the initial post.
Notifying the developers with pushing replies without new content will not help to get it in faster.

@teotikalki

This comment has been minimized.

Copy link

@teotikalki teotikalki commented Dec 31, 2019

So I just read through this and I feel like this HAS to have come up SOMEWHERE before but... why not just integrate Matrix as the comm layer for Nextcloud? They're already doing a really good job at making federated slack-style chat with voice and video (by integrating Jitsi.. this is a thing ;).)

It would be much more the 'unix way'. I feel that 'elegant integration' is better than 'monolithic bloat' (the most frequent criticism I find about NC in reviews lately). Also, while lacking the coding expertise to say for sure, I really feel like NC devs coding an integration would be an order of magnitude less work than coding from scratch. I'm thinking here about how NC devs collaborated with LibreOffice devs to bring about Collabora as an OPTIONAL INTEGRATION rather than trying to 'write NC office'.

@markuman

This comment has been minimized.

Copy link

@markuman markuman commented Jan 25, 2020

@teotikalki collabora is a memory nightmare. for every document which will be opened, a new libreoffice is opened in background. that's something no one wants to have on its rpi.
in onlyoffice everything happen in the client side. and onlyoffice is not written bei NC itself. onlyoffice is a different company which has build this open source office suite and what is sponsoring its integration.
so at the end you have the choice between collabora and onlyoffice - both is open source and not made by nextcloud.

but in case of nextcloud talk - a agree.

@Ornias1993

This comment has been minimized.

Copy link

@Ornias1993 Ornias1993 commented Feb 2, 2020

Notifying the developers with pushing replies without new content will not help to get it in faster.

@nickvergessen
Same could be said about responding without anything to go with as a developer.
People tend to get worked up about that and that causes people to go push for more info.

But trying to be somewhat constructive:
Considering your last flags (next major (19), Following Major):

  • What are the goals (or preferences) for Talk: Expanding your framework to include federation and such (https://xkcd.com/927/), expanding the current framework to support multiple frameworks (like some social apps are playing with) or Moving to another framework (Matrix, XMPP, Matermost)
  • What is the pseudo-timeframe (months, about a year or a year+ ) to have enough features to call it "feature competitive" (in comparison with other frameworks) when it comes to communicating outside a single server instance?

I'm going to be fair:
People are willing to sacrifice some features, if it means heaving everything under one roof and in some cases the solutions others provide may be too-much out of scope (such as bitwarden when it comes to passwords, a totally different philosophy).

But for talk, users (including corporate) basically want: Mattermost (light) with federation.
Mattermost has great plugin support for other protocols but (also) just lacks federation itself.

If you guys get both of those two functions working: connectivity and federation, Nextcloud Talk would push itself to the top-part of the communication suite-pack.
Those are not easy features code wise and hard to do solid. But if you can, you're in... if you don't it would always stay a "meh" niche solution.

@tuxfy

This comment has been minimized.

Copy link

@tuxfy tuxfy commented Mar 19, 2020

I think now is the perfect time to take further look at this! Please implement the federation function 🙇‍♀️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.