Configurable SMS segment limit / warning before sending
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 42/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 停滞
- 領域
- mobile, mobile-dev
調査の方向性
This is a new Settings plus send-path feature, not a one-file tweak. Start from the existing outgoing-message settings (character counter and “Send long messages as MMS”) and the send path that already calls SmsManager.divideMessage() to count segments. Wire a confirmation dialog when the count exceeds a configurable warning threshold, then an optional hard cap that blocks send. Done means both options appear under Settings → Outgoing messages and sending respects them. The issue is 205 days old with no comments, so confirm with maintainers before building.
索引モデルが issue の本文から書いたものです。
説明
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Feature description
Fossify Messages already has two useful features related to long messages: a character/segment counter and a "Send long messages as MMS" option. However, neither of these prevents a user from accidentally sending a message that gets split into a very large number of SMS segments.
Proposed solution
Add a configurable segment limit with two levels of protection:
-
Warning before sending: When a message exceeds a configurable number of segments (e.g., default 3), show a confirmation dialog: "This message will be sent as 327 SMS segments. Send anyway?" This is the most important addition — it catches accidental sends while still allowing the user to proceed.
-
Optional hard segment limit: A setting where users can define a maximum number of segments (e.g., 5). Messages exceeding this limit cannot be sent. This is particularly useful for parental control scenarios or users on limited SMS plans.
Both options could be exposed in Settings → Outgoing messages alongside the existing character counter and "Send long messages as MMS" settings.
Why do you want this feature?
In my case, my daughter created a very long message, and hit send. This resulted in 500+ SMS segments being sent — instantly hitting the monthly SMS limit on her prepaid plan, generating extra costs of 31 euro-cent per segment. The character counter was visible, but there was nothing to stop the message from being sent. The "Send long messages as MMS" option does not help in our case because MMS is not included in her plan.
Additional information
Additional context
- The existing character counter shows the segment count but does not prevent sending. The existing MMS conversion option helps some users but is not a solution when MMS is unavailable or costs extra.
- Related issue: #222 (long messages triggering Android warnings and error code 5). A confirmation dialog would also reduce the confusion described in that issue.
- Implementation could hook into the existing
SmsManager.divideMessage()call to count segments before sending and conditionally show a dialog.
- 主要言語
- Kotlin
- スター
- 1.6k
- フォーク
- 187
- 平均マージ
- 1日 15時間
- マージ済み PR（30日）
- 20
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
FossifyOrg/Messages のほかの issue
-
bug needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
FossifyOrg/Messages#929 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
FossifyOrg/Messages#927 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 63/100
FossifyOrg/Messages#919 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
FossifyOrg/Messages#897 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
FossifyOrg/Messages#761 ·
メンテナーはふだん 1 日以内に返信
FossifyOrg/Messages の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
OpenAPITools/openapi-generator#25454 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
navikt/mock-oauth2-server#1149 ·
メンテナーはふだん 1 日以内に返信
-
priority: high scope: frontend type: bug
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
GonsiorHack/czyPrzejade#12 ·
-
afk-ok area:frontend size:S
難易度 2/5 1〜3時間 初心者へのやさしさ 87/100
enorm-labs/event-junkie#4154 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
pengchujin/aerial-tv#857 ·
メンテナーはふだん 1 日以内に返信