briar issueshttps://code.briarproject.org/groups/briar/-/issues2018-06-12T11:32:37Zhttps://code.briarproject.org/briar/briar/-/issues/144User testing sessions2018-06-12T11:32:37ZakwizgranUser testing sessionsTwo user testing sessions for Milestone G -- findings to be documented in the issue tracker.Two user testing sessions for Milestone G -- findings to be documented in the issue tracker.Milestone Ghttps://code.briarproject.org/briar/briar/-/issues/143Co-ordinate translations before 1.0 release2018-06-12T11:32:37ZakwizgranCo-ordinate translations before 1.0 releaseMilestone GTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/142Co-ordinate with OTF security audit2018-06-12T11:32:37ZakwizgranCo-ordinate with OTF security auditMilestone Gakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/141Roadmap for partner organisation's Bramble app2018-06-12T11:32:37ZakwizgranRoadmap for partner organisation's Bramble appMilestone Fakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/140User testing sessions2018-06-12T11:32:37ZakwizgranUser testing sessionsTwo user testing sessions for Milestone F -- findings to be documented in the issue tracker.Two user testing sessions for Milestone F -- findings to be documented in the issue tracker.Milestone Fhttps://code.briarproject.org/briar/briar/-/issues/139User manual2018-06-12T11:32:37ZakwizgranUser manualMilestone Fakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/136Release Bramble as a separate library2018-06-12T11:32:37ZakwizgranRelease Bramble as a separate librarySeparate the Bramble protocol stack from the Briar app so that it can be released as a separate library usable by other projects.Separate the Bramble protocol stack from the Briar app so that it can be released as a separate library usable by other projects.Milestone Fakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/135RSS import2018-06-12T11:32:38ZakwizgranRSS importUsers with internet access should be able to import RSS feeds (via Tor) and re-publish them as Briar blogs.
First iteration:
* UI for importing a feed -- no preview, show an error if the feed can't be fetched and parsed (#483)
* ...Users with internet access should be able to import RSS feeds (via Tor) and re-publish them as Briar blogs.
First iteration:
* UI for importing a feed -- no preview, show an error if the feed can't be fetched and parsed (#483)
* Fetch the feed periodically in the background -- not via Tor (#484)
* Extract new entries from the feed -- not fetching the full text (#485)
* Convert any new entries to Briar blog posts -- just strip HTML tags (#486)
* Post converted entries to the user's personal blog (part of #486)
* Simple UI for Managing RSS Feeds (#483 & #517)
# RSS/Atom Java libraries
## [ROME](https://rometools.github.io/rome/)
* actively maintained and looks to be the most popular on the net
* Does [not support Android fully](https://github.com/rometools/rome/labels/android), support will come with ~~2.0.0~~ 1.6.1 version
* quite big with lots of stuff we don't need such as feed generation, but looks like these are in separate jars
* Has a ROME Fetcher to fetch the feeds, but [is deprecated](https://github.com/rometools/rome/issues/276) in favor of dedicated HTTP libraries such as Apache HttpClient. We can use a library as okhttp as well and just pass the `InputStream` to the feed parser.
* On Maven Central and [jcenter](https://bintray.com/bintray/jcenter/com.rometools%3Arome/view)
* License: Apache License 2.0
* Dependencies:
* rome-utils
* jdom2
* slf4j-api
## [PkRSS](https://pkmmte.github.io/PkRSS/)
* Android library can not be in briar-core
* lightweight
* License: Apache License 2.0
## [Jakarta FeedParser](https://commons.apache.org/dormant/feedparser/)
* Part of apache commons, has *dormant* in the URL
* License: Apache License 2.0
* Dependencies:
* jaxen-full
* jdom
* log4j
* xercesImpl
* xml-apis
* commons-httpclient (starting from version 3)
## [informa](http://informa.sourceforge.net/)
* Last release 2007Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/134Blogs2018-06-12T11:32:38ZakwizgranBlogsUsers should be able to publish and read blogs through the Briar app. This will be a new top-level section in the UI, alongside forums and private groups. Blogs will be shared with contacts in a similar way to forums.Users should be able to publish and read blogs through the Briar app. This will be a new top-level section in the UI, alongside forums and private groups. Blogs will be shared with contacts in a similar way to forums.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/133Security testing2018-06-12T11:32:38ZakwizgranSecurity testingWhite-box security testing of the latest beta for Milestone D -- findings to be documented in the issue tracker.White-box security testing of the latest beta for Milestone D -- findings to be documented in the issue tracker.Milestone Dakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/131Protocol spec for BQP2018-06-12T11:32:38ZakwizgranProtocol spec for BQPMilestone Dhttps://code.briarproject.org/briar/briar/-/issues/129Protocol spec for BTP2018-06-12T11:32:38ZakwizgranProtocol spec for BTPMilestone Dhttps://code.briarproject.org/briar/briar/-/issues/128User testing sessions2018-06-12T11:32:38ZakwizgranUser testing sessionsTwo user testing sessions for Milestone D -- findings to be documented in the issue tracker.Two user testing sessions for Milestone D -- findings to be documented in the issue tracker.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/127Private groups2018-06-12T11:32:38ZakwizgranPrivate groupsUsers should be able to create private groups to have confidential conversations among a known set of identities. This will be a new top-level section in the UI, separate from forums.
Users should be able to create private groups to have confidential conversations among a known set of identities. This will be a new top-level section in the UI, separate from forums.
Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/126User stories for partner organisation's Bramble app2018-06-12T11:32:38ZakwizgranUser stories for partner organisation's Bramble appAgile user stories describing how the app will be used. "As an X, I want Y so that Z".Agile user stories describing how the app will be used. "As an X, I want Y so that Z".Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/125Use cases for partner organisation's Bramble app2018-06-12T11:32:38ZakwizgranUse cases for partner organisation's Bramble appHigh-level description of the tasks for which the app will be used.High-level description of the tasks for which the app will be used.Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/124User feedback submitted via Tor2018-06-12T11:32:38ZakwizgranUser feedback submitted via TorIf a user wants to send feedback to the developers, the app should encrypt the feedback with the developers' public key and post it to a feedback channel.
Messages in the feedback channel should be synced with contacts, but no further...If a user wants to send feedback to the developers, the app should encrypt the feedback with the developers' public key and post it to a feedback channel.
Messages in the feedback channel should be synced with contacts, but no further. We'll need to add a special contact that's only reachable via Tor for delivering feedback to the developers. To prevent the special contact from being a single point where Briar users can be enumerated, it should only be contacted when there's feedback to deliver.
Users should be able to opt out of delivering feedback for their contacts.Milestone Chttps://code.briarproject.org/briar/briar/-/issues/123Encrypted crash reports submitted via Tor2018-06-12T11:32:38ZakwizgranEncrypted crash reports submitted via TorIf the user chooses to report a crash, the crash reporter should encrypt the crash report with the developers' public key and store it on the disk until the app is re-launched. The app should import the encrypted report, post it to a cra...If the user chooses to report a crash, the crash reporter should encrypt the crash report with the developers' public key and store it on the disk until the app is re-launched. The app should import the encrypted report, post it to a crash report channel and delete it from the disk.
Messages in the crash report channel should be synced with contacts, but no further. We'll need to add a special contact that's only reachable via Tor for delivering reports to the developers. To prevent the special contact from being a single point where Briar users can be enumerated, it should only be contacted when there are crash reports to deliver.
Users should be able to opt out of sending crash reports and opt out of delivering crash reports for their contacts.Milestone Chttps://code.briarproject.org/briar/briar/-/issues/122UI for threaded discussions2018-06-12T11:32:38ZakwizgranUI for threaded discussionsForum conversations are currently shown in a flat list, which testers have found confusing. Create a threaded view in which replies are nested below their parents. Reddit shows that this is possible on a phone screen. At some level of ne...Forum conversations are currently shown in a flat list, which testers have found confusing. Create a threaded view in which replies are nested below their parents. Reddit shows that this is possible on a phone screen. At some level of nesting, replies will need to be collapsed.Milestone Chttps://code.briarproject.org/briar/briar/-/issues/121Improve UX for sharing forums2018-06-12T11:32:38ZakwizgranImprove UX for sharing forumsThe process for sharing a forum should involve an explicit invitation message. It should be possible to accept, decline or ignore invitations, and the invitation status of each contact should be shown when viewing the details of a forum....The process for sharing a forum should involve an explicit invitation message. It should be possible to accept, decline or ignore invitations, and the invitation status of each contact should be shown when viewing the details of a forum.
We may also want to show information about the contacts and other identities that have posted to the forum.Milestone C