If the content settings specify their own post settings and override the
instance settings, a hint (and link to the content settings) is added to the
instance settings (infos) since that setting might introduce confusion (As
happened in #1677).
The pending-button can now be shown in any corner the user prefers. This is
accomplished by allowing the user to move the counter left in addition to the
already present option to move it down. Fixes#1637
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
The "Translate with DeepL"-option is removed to make the app better understandable for the average user. A person who wants to use DeepL can still insert their own API key to always use DeepL.
Fixes#1583
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
- Replacement of the term "Bottone" in "Pulsante", the first term is mainly connected to clothing, instead the use of "Pulsante" identifies more precisely the concept of using a physical or virtual button.
- Maintaining the Boost term: on Twitter, in Italy, it's usual to use terms such as "tweets, retweets, and others". Therefore, the maintenance of the Boost word has been preferred rather than the total change to "Condividi".
- Reference buttons should eliminate the use of the word "Enable" as the visual switch is the element that confirms to the user whether the action is enabled or not. Further advice is to place the information icon "i" next to the switches, which allows the user to better understand the use of these features.
- Translation of: accessibility, filters, package: status, package: notifications, package: explore, package: conversations, package: account.
- Miscellaneous and minor changes
ATTENTION: using words like "social media love" and then asking "Happy messaging" can lead to misleading messages. They should be removed from all translations.
* Update Simplified Chinese localization for Reply Visibility
* Update Simplified Chinese localization for Tag Groups
* Altered Simplified Chinese translation for tab label
显示 Tab 标签 -> 在导航栏中显示文本
* Allow specifying the visibility of replies
Replies can now have their own default visibility. This visibility is always at
least as restrictive as the default post visibility. When posting a reply, the
visibility is pre-populated with the more restrictive out of the default and
the visibility of the original post.
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
* Use iOS-specific modifier
If the app is run on iOS 17, the new onChange(...)-modifier is used.
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
* Restrict the extension of the onChange-Modifier
The extension of the view to allow the use of the version-appropriate
onChange-modifier is now only available in the relevant file.
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
* Reset to use Xcode 14 / iOS 16
The iOS 17 specific changes are removed to allow building in the older Xcode 14.
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
* Make the default reply visibility public
The standard default reply visibility is now public, the behavior of the app
isn't changed for a user who just updated.
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
---------
Signed-off-by: Paul Schuetz <pa.schuetz@web.de>
