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

Can't see whether a group is public or private unless I am the owner #26923

Open
php4fan opened this issue Oct 12, 2023 · 2 comments
Open

Can't see whether a group is public or private unless I am the owner #26923

php4fan opened this issue Oct 12, 2023 · 2 comments
Labels

Comments

@php4fan
Copy link

php4fan commented Oct 12, 2023

Steps to reproduce

  1. be a member of a group or supergroup
  2. be an admin of a group that I'm not an owner of (I guess that necessarily makes it a supergroup? Not sure)

Expected behaviour

In both cases, I should be able to easily tell whether the group is private or public. I don't care if I can deduce it by some of the features that it has, like, "it has an easy-to-read url therefore it must be public", or "it has unreadable invite links therefore it is private" (whether or not that's true) or "it has admins so it must be a supergroups and supergroups with whatever are always whatever". I cannot be expected to know all the rules and sit down and think to figure out whether a group that I'm in must be public or private. It should show up in "View group info" or "Manage group" or both, regardless of whether I can change it or not.

Actual behaviour

I can't find it anywhere.

I am admin (but not owner) of a bunch of groups and I genuinely don't know which ones are public and which ones are private. Let alone the ones where I'm not an admin.

Only when I'm the owner, in "Manage group" there's "Group type: private/public" (which in that case I can change).

Operating system

Manjaro Linux

Version of Telegram Desktop

4.9.7

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

@php4fan php4fan added the bug label Oct 12, 2023
Copy link

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

@github-actions github-actions bot added the stale label Apr 10, 2024
@php4fan
Copy link
Author

php4fan commented Apr 10, 2024

This issue was inactive for a long time and will be automatically closed in 30 days

This is idiotic. Is this something that comes by default from GitHub or did you set it up?

@github-actions github-actions bot removed the stale label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant