Rename the “unlisted” visibility to “quiet public”

naskya commented

2025-02-05 20:52:12 +09:00

Owner

What type of issue is this?

label: Client

label: Locale

label: Discussion

What do you think needs to be discussed?

Rename the “unlisted” visibility to “quiet public”

Recently, Mastodon changed the term “unlisted” to “quiet public” in the official web client, and I’m in favor of this change (note: it was super controversial https://github.com/mastodon/mastodon/discussions/28887)

“unlisted” posts may be listed in many places, especially because other implementations may handle this visibility differently (e.g., unlisted posts show up in Misskey’s post search results). So I don’t think “unlisted” is correct, but I don’t know how “unlisted” and “quiet public” sound to native/good English speakers.

What do you think? I think “quiet public” is wordy but more descriptive.

At least in my native language, “unlisted” is translated into an incomprehensible word (that was borrowed from Mastodon’s translation when Calckey renamed “home” to “unlisted”), and new users always say “What is unlisted?”. I wonder if the same thing is happening in other languages.

Also, the term “unlisted” is used for hidden content in other popular web services like YouTube and Pastebin, but that’s not the case here (unlisted posts are listed on the profile page)

(Copied from the Matrix chat room)

Relevant information (optional)

In Mastodon, “quiet public” is translated as

ひかえめな公開 (in Japanese)
悄悄公开 (in Simplified Chinese)

to me, this makes a lot of sense than 未収載 (Japanese) or 不公开 (Simplified Chinese).

edit: I just realized that the Simplified Chinese translation is already updated in Firefish

Version

v20240725

Instance

What browser are you using? (client-side issues only)

What operating system are you using? (client-side issues only)

How do you deploy Firefish on your server? (server-side issues only)

What operating system are you using? (Server-side issues only)

Contribution Guidelines

By submitting this issue, you agree to follow our Contribution Guidelines

I agree to follow this project's Contribution Guidelines
I have searched the issue tracker for similar issues, and this is not a duplicate.

Are you willing to open a merge request? (optional)

Yes, I will open a merge request that closes this ticket.

## What type of issue is this?    * label: Client    * label: Locale      * label: Discussion ## What do you think needs to be discussed?  Rename the “unlisted” visibility to “quiet public” > Recently, Mastodon changed the term “unlisted” to “quiet public” in the official web client, and I’m in favor of this change (note: it was super controversial https://github.com/mastodon/mastodon/discussions/28887) > > “unlisted” posts may be listed in many places, especially because other implementations may handle this visibility differently (e.g., unlisted posts show up in Misskey’s post search results). So I don’t think “unlisted” is correct, but I don’t know how “unlisted” and “quiet public” sound to native/good English speakers. > > What do you think? I think “quiet public” is wordy but more descriptive. > > At least in my native language, “unlisted” is translated into an incomprehensible word (that was borrowed from Mastodon’s translation when Calckey renamed “home” to “unlisted”), and new users always say “What is unlisted?”. I wonder if the same thing is happening in other languages. > > Also, the term “unlisted” is used for hidden content in other popular web services like YouTube and Pastebin, but that’s not the case here (unlisted posts are listed on the profile page) (Copied from the Matrix chat room) ## Relevant information (optional) In Mastodon, “quiet public” is translated as - ひかえめな公開 (in Japanese) - 悄悄公开 (in Simplified Chinese) to me, this makes a lot of sense than 未収載 (Japanese) or 不公开 (Simplified Chinese). edit: I just realized that the Simplified Chinese translation is already updated in Firefish ## Version  v20240725 <details> ### Instance  ### What browser are you using? (client-side issues only) ### What operating system are you using? (client-side issues only) ### How do you deploy Firefish on your server? (server-side issues only) ### What operating system are you using? (Server-side issues only) </details> ## Contribution Guidelines By submitting this issue, you agree to follow our [Contribution Guidelines](https://firefish.dev/firefish/firefish/-/blob/develop/CONTRIBUTING.md) - [x] I agree to follow this project's Contribution Guidelines - [x] I have searched the issue tracker for similar issues, and this is not a duplicate. ## Are you willing to open a merge request? (optional) - [x] Yes, I will open a merge request that closes this ticket.

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: naskya

Both unlisted and quiet public make sense in Firefishverse because it’s hidden in local/global timelines, post search results, antennas (unless you are a follower), etc., but I don’t think unlisted makes sense in the Fediverse in general. Since we don’t have much control over federated posts, I think we must explicitly tell users that it’s public. We can only make a (not very reliable) promise that your quiet public posts will be somewhat quieter than “public”. (There’s no “unlisted” thingy in the bare ActivityPub protocol. It’s just Mastodon that treats it differently; other implementations may or may not respect that.)

My main concern with quiet public is the sense (feel) of the term.

*Author: naskya* Both unlisted and quiet public make sense in _Firefishverse_ because it’s hidden in local/global timelines, post search results, antennas (unless you are a follower), etc., but I don’t think unlisted makes sense in the Fediverse in general. Since we don’t have much control over federated posts, I think we must explicitly tell users that it’s public. We can only make a (not very reliable) promise that your quiet public posts will be somewhat quieter than “public”. (There’s no “unlisted” thingy in the bare ActivityPub protocol. It’s just Mastodon that treats it differently; other implementations may or may not respect that.) My main concern with quiet public is the sense (feel) of the term.

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: sophia krusniczky

idea: "quiet public" replaces the current "unlisted" visibility option. then, add a new visibility option called "unlisted" which would actually be unlisted in the full sense of the term; posts appear on the timelines of followers, but they are not cataloged on the timeline in a profile page (and are only visible to admins/mods/the user themself (don't know how to make this federate though lol (this likely negates the whole idea)))

*Author: sophia krusniczky* idea: "quiet public" replaces the current "unlisted" visibility option. then, add a new visibility option called "unlisted" which would actually be unlisted in the full sense of the term; posts appear on the timelines of followers, but they are not cataloged on the timeline in a profile page (and are only visible to admins/mods/the user themself (don't know how to make this federate though lol (this likely negates the whole idea)))

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: sophia krusniczky

personally i am against this change (for the english language at least). i have observed a precedent that 'unlisted' is the correct term for this sort of visibility across various platforms. "quiet public" makes sense as the term for mastodon, giving how they are implementing their algorithmic features, but it feels wrong for the fish (unless we're implementing something like #9697) as what we have now is not broken thus does not need fixing. again, in terms of the english translation, i am in no position to speak for other languages.

*Author: sophia krusniczky* personally i am against this change (for the english language at least). i have observed a precedent that 'unlisted' is the correct term for this sort of visibility across various platforms. "quiet public" makes sense as the term for mastodon, giving how they are implementing their algorithmic features, but it feels wrong for the fish (unless we're implementing something like #9697) as what we have now is not broken thus does not need fixing. again, in terms of the english translation, i am in no position to speak for other languages.

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: naskya

Thank you for that. In Mastodon, “Unlisted” was “不公开” until recently 😑

I think the same thing is happening in other languages

*Author: naskya* Thank you for that. In Mastodon, “Unlisted” was “不公开” until recently 😑 I think the same thing is happening in other languages ![](/uploads/f4069e868be3fd44cee65f431082e68f/2024-07-30-23_15_48.png)

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: laozhoubuluo

In simplified Chinese, the word "Unlisted (未列出)" is controversial, and some people think that such posts are only visible to the poster.

In order to ease the controversy, I refer to Mastodon translation to change it to the more appropriate "Quiet Public (悄悄公开)" at simplified Chinese.

*Author: laozhoubuluo* In simplified Chinese, the word "Unlisted (未列出)" is controversial, and some people think that such posts are only visible to the poster. In order to ease the controversy, I refer to Mastodon translation to change it to the more appropriate "Quiet Public (悄悄公开)" at simplified Chinese.

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: naskya

changed the description

*Author: naskya* changed the description

naskya commented

2025-02-05 20:52:13 +09:00

Author

Owner

Author: naskya

changed the description

*Author: naskya* changed the description

Rows
Columns

Rename the “unlisted” visibility to “quiet public” #173

What type of issue is this?

What do you think needs to be discussed?

Relevant information (optional)

Version

Instance

What browser are you using? (client-side issues only)

What operating system are you using? (client-side issues only)

How do you deploy Firefish on your server? (server-side issues only)

What operating system are you using? (Server-side issues only)

Contribution Guidelines

Are you willing to open a merge request? (optional)