briar issueshttps://code.briarproject.org/briar/briar/-/issues2018-06-12T11:32:18Zhttps://code.briarproject.org/briar/briar/-/issues/660Implement UX for the list of private groups2018-06-12T11:32:18ZakwizgranImplement UX for the list of private groupsDepends on #656. Subtask of #127.
![list of private groups](https://code.briarproject.org/akwizgran/briar/uploads/5538a5b7a515228da908afe57367038c/656_pg_list.jpg)Depends on #656. Subtask of #127.
![list of private groups](https://code.briarproject.org/akwizgran/briar/uploads/5538a5b7a515228da908afe57367038c/656_pg_list.jpg)Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/659Protocol for private group invitations2018-06-12T11:32:18ZakwizgranProtocol for private group invitationsThis could be similar to the blog and forum invitation protocols, but there's an opportunity to make it simpler, as only the creator of the group can send invitations. When a member has been added or removed, the creator should send an a...This could be similar to the blog and forum invitation protocols, but there's an opportunity to make it simpler, as only the creator of the group can send invitations. When a member has been added or removed, the creator should send an announcement to the group (see #658).
Related to #456. Subtask of #127.Milestone Eakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/658Protocol for private group messaging2018-06-12T11:32:18ZakwizgranProtocol for private group messagingThis can be similar to the forum protocol, plus messages for announcing when members join and leave. We may not need a message for announcing that the group has been dissolved, as that may be part of the invitation protocol.
Posts will ...This can be similar to the forum protocol, plus messages for announcing when members join and leave. We may not need a message for announcing that the group has been dissolved, as that may be part of the invitation protocol.
Posts will need to be compared with the current membership list to ensure they're signed by members, taking into account the possibility of posts and membership messages arriving out of order.
Subtask of #127.Milestone Eakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/657UX design for viewing the membership of a private group2018-06-05T20:39:27ZakwizgranUX design for viewing the membership of a private groupThis capability was requested by users, and was part of the motivation for creating the private group feature, so it should be easily accessible.
Subtask of #127.This capability was requested by users, and was part of the motivation for creating the private group feature, so it should be easily accessible.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/656UX design for the list of private groups2018-06-05T20:39:27ZakwizgranUX design for the list of private groupsEach list item should include the name of the group, the timestamp of the latest message and the number of unread messages. We could also include the identity of the creator and/or the number of members.
Subtask of #127.Each list item should include the name of the group, the timestamp of the latest message and the number of unread messages. We could also include the identity of the creator and/or the number of members.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/655UX design for renaming a private group2018-06-05T20:39:27ZakwizgranUX design for renaming a private groupThis action is only available to the creator of the group.
Subtask of #127.This action is only available to the creator of the group.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/654UX design for revealing contacts to a private group2018-06-05T20:39:27ZakwizgranUX design for revealing contacts to a private groupThis action is not available to the creator of the group. This ticket includes the UX for notifying the user that she has contacts in the group, both when she first joins and when any of her contacts subsequently join. The design may inc...This action is not available to the creator of the group. This ticket includes the UX for notifying the user that she has contacts in the group, both when she first joins and when any of her contacts subsequently join. The design may include an indication of how many contacts the user syncs the group with (connection strength), which may overlap with #645 and #646. The design may involve onboarding.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/653UX design for inviting new members to a group2018-06-12T11:32:18ZakwizgranUX design for inviting new members to a groupThis action is only available to the creator of the group.
Subtask of #127.This action is only available to the creator of the group.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/652UX design for leaving a group2018-06-12T11:32:18ZakwizgranUX design for leaving a groupThis action is not available to the creator of the group. This ticket includes the UX for notifying other members that a member has left, and displaying groups the user has left in the list of private groups (or not, if we decide they sh...This action is not available to the creator of the group. This ticket includes the UX for notifying other members that a member has left, and displaying groups the user has left in the list of private groups (or not, if we decide they should be removed from the list).
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/651UX design for dissolving a group2018-06-12T11:32:18ZakwizgranUX design for dissolving a groupThis action is only available to the creator of the group. This ticket includes the UX for notifying other members of the group that it has been dissolved, and displaying dissolved groups in the list of private groups (or not, if we deci...This action is only available to the creator of the group. This ticket includes the UX for notifying other members of the group that it has been dissolved, and displaying dissolved groups in the list of private groups (or not, if we decide they should be removed from the list).Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/650UX design for displaying message threads in private groups2018-06-12T11:32:18ZakwizgranUX design for displaying message threads in private groupsThis can be identical to forums unless there's a reason we need to do things differently.
Subtask of #127.This can be identical to forums unless there's a reason we need to do things differently.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/649UX design for composing and replying to private group messages2018-06-12T11:32:18ZakwizgranUX design for composing and replying to private group messagesThis can be identical to forums unless there's a reason we need to do things differently.
Subtask of #127.This can be identical to forums unless there's a reason we need to do things differently.
Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/648UX design for creating a private group2018-06-12T11:32:18ZakwizgranUX design for creating a private groupSubtask of #127.Subtask of #127.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/646UX for groups that are synced with contacts who are all offline2018-06-12T11:32:19ZakwizgranUX for groups that are synced with contacts who are all offlineDecide how to display blogs, forums and private groups that are synced with contacts who are all offline (thus no messages will be sent or received until one of those contacts comes online).
"Do nothing" may be an acceptable solution.Decide how to display blogs, forums and private groups that are synced with contacts who are all offline (thus no messages will be sent or received until one of those contacts comes online).
"Do nothing" may be an acceptable solution.Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/645UX for groups that are no longer synced with any contacts2020-11-21T17:04:16ZakwizgranUX for groups that are no longer synced with any contactsDecide how to display blogs, forums and private groups that are no longer synced with any contacts (thus no messages will be sent or received).Decide how to display blogs, forums and private groups that are no longer synced with any contacts (thus no messages will be sent or received).https://code.briarproject.org/briar/briar/-/issues/644Header not visible after account creation2018-06-12T11:32:19ZErnir ErlingssonHeader not visible after account creation1. Run Briar for the first time
2. Perform the necessary step to create an account.
3. The Contact list is displayed in an empty state, notice that the header is not visible, rendering all user interaction is impossible.
The issue c...1. Run Briar for the first time
2. Perform the necessary step to create an account.
3. The Contact list is displayed in an empty state, notice that the header is not visible, rendering all user interaction is impossible.
The issue corrects itself if I close the app (via the home button) and re-enter it.
This problem might be affected by #642Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/643Allow messages to be deleted in the delivery hook2018-06-12T11:32:19ZakwizgranAllow messages to be deleted in the delivery hookIf a client deletes a message in the delivery hook, the validation manager treats the message as invalid. Clients may want to delete messages they've finished handlng without having them invalidated, so we should provide some other way f...If a client deletes a message in the delivery hook, the validation manager treats the message as invalid. Clients may want to delete messages they've finished handlng without having them invalidated, so we should provide some other way for the delivery hook to signal that a message is invalid, such as throwing an InvalidMessageException.Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/642Remove loading screen callbacks from BaseFragmentListener2018-06-12T11:32:19ZakwizgranRemove loading screen callbacks from BaseFragmentListenerFragments should be responsible for their own progress bars.Fragments should be responsible for their own progress bars.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/641RSS Feed Entry Comparator wrongly assumes existing date2018-06-12T11:32:19ZTorsten GroteRSS Feed Entry Comparator wrongly assumes existing dateThe `EntryComparator` in the `FeedManager` can cause a crash when run on a feed with entries that do not have dates at all.The `EntryComparator` in the `FeedManager` can cause a crash when run on a feed with entries that do not have dates at all.Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/640Detect blogs that are no longer receiving updates2020-11-21T17:05:02ZakwizgranDetect blogs that are no longer receiving updatesIt's possible for a blog subscriber to be cut off from the blog's author due to upstream subscribers unsubscribing or leaving the network. We could use some combination of keepalive messages from the author and an adaptive timeout at the...It's possible for a blog subscriber to be cut off from the blog's author due to upstream subscribers unsubscribing or leaving the network. We could use some combination of keepalive messages from the author and an adaptive timeout at the subscriber to detect this and mark the blog as inactive or unreachable.
If we use keepalives, the interval between keepalives should adapt to the average interval between posts. If we use a timeout at the subscriber based on the arrival times of updates, TCP's running estimates of round-trip time and round-trip time variance might be a good place to start.
Depending on the mechanism used, this might also be applicable to other kinds of group.