nextcloud / nextcloud/talk-android

Add ability to join public calls without an account

Open
#261 65 comments 30 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: authentication 🔑 help wanted
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

To get a wider spread of Talk, and enhance the usability it would be nice to somehow generate automatic guest accounts that users could use with Talk.

So for example, if I choose a contact from the telephones contacts (full contact book) a link would be generated that automatically creates a guest user that are valid for let's say 1 hour.

That way anyone with Nextcloud and Talk installed could use Talk for private chats or video calls - not depending if they have Talk or not.

Maybe my idea isn't so thought through, but I would really like to make it easier for anyone using Talk without the need for a Nextcloud Server. I know that we have public conversations, but it would be nice to invite anyone using a guest account so that the external user could get the full benefit of using Talk on their Phone as well.

Maybe send something automatically generated per SMS like:

Hey! [Full Name] wants to talk to you on Nextcloud Talk. Download the app from Play here: [Link]
Your temporary credentials are:

Username:
Password: 

The credentials are valid for 1 hour.

The server address is: [Address of the senders server based on what's used for Talk in their config]

My proposal would need some work on the server side as well I guess.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how Talk currently handles public conversations and invitations in the Android app. Clarify the server-side guest-account, temporary-credential, SMS, and one-hour validity requirements before identifying the Android entry points; done would mean a settled cross-project design rather than an isolated client change.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.