sl-service-account
commented
4 years ago Kitty Barnett commented at 2020-08-15T14:58:00Z, updated at 2020-08-15T14:59:57Z
The technical information above is incorrect: a group message uses the same messaging as IMs so it has a limit of 1023 bytes (total for the title and the message since they're combined).
The 511 character limit is likely to accommodate non-English speaking language where UTF-8 encoding can cause one character to take up multiple bytes.
So:
- for sending the ImprovedInstantMessage is used with a dialog of IM_GROUP_NOTICE and allows 1023 bytes to be used up by the message
- for receiving the same limit is in place
-
for requesting a group notice on demand (GroupNoticeRequest message is sent to request and then IM_GROUP_NOTICE_REQUESTED is sent back as a response) there is a limit of 512 bytes (so actually half the message can end up lost) <-- this is the part that needs to be fixed and it should also be 1023 bytes
Easy repro: create a group notice consisting of a 1 character title and repeated éééééééééééé for the enitre maximum allowed length and then send the message.
You'll note that the toast that appears contains the full message (+/-510 e"s , but if you go back to the notice history and view it from there you'll have just under half of the amount of é's.
This basically means that non-Latin alphabet using resident can still type in a message, but only half of it will end up being received, making this a rather severe bug in my view.
Steps to Reproduce
Communicate -> Groups -> Open a group info you can send notices in, Group A -> Notices -> New Notice.
In the Message box, enter 511 characters (the maximum allowed), for example:
In the Subject box, enter 20 characters, for example
ABCDEFGHIJKLMNOPQRSTSee Fig 1 attached.
Send the group notice.
Observed Behaviour
Observe that in the notification toast, the full message text is shown correctly. See Fig 2 attached.
Open Group A info -> Notices & check the notice you just sent.
Observe that the message text is truncated. See Fig 3 attached.
Bug reproduces on any viewer.
Expected Behaviour
The group message text should be seen in full.
Other Information
Information from [~ansariel.hiller]:
Tested with a 511 chars long notice with standard ASCII chars and 511 bytes (503 chars) long notice including non-standard ASCII characters. Both messages were shown properly in the notification toast. However, if you view them in the Notifications tab in a group profile, they get cut short. They arrive cut short from the simulator already, so it's not a viewer issue. Needs a server side fix from Linden Lab.
A group notice can be 512 bytes long (viewer allows entering 511 bytes). If you view notices from the Notifications tab in the group profile, the limit is imposed on the combined string of| . So the length of the subject reduces the length of message that can be shown.
Basically it's: length of subject + 1 + length of message > 511 = truncate
Additional Problem
Send a group notice that includes the pipe | character in the subject text. See Fig 4
Observe that all subject text after the | character becomes part of the message text. See Fig 5
Attachments
Links
Duplicates
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-202943 | | Summary | Group notice text is truncated by the simulator. | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Whirly Fizzle (whirly.fizzle) | | Created at | 2018-01-18T09:00:05Z | | Updated at | 2023-02-21T18:06:12Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2020-08-15T09:58:00.193-0500', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'Filling in...', 'What were you doing when it happened?': '...', 'What were you expecting to happen instead?': '....', 'Where': 'Any region/server version.', } ```