briar issueshttps://code.briarproject.org/briar/briar/-/issues2018-06-12T11:32:26Zhttps://code.briarproject.org/briar/briar/-/issues/422Forum sub-tree duplicates2018-06-12T11:32:26ZErnir ErlingssonForum sub-tree duplicates>I've managed to generate a different bug now: subtrees can get duplicated. Specifically, if I close one subtree (at any level), the indicator for one of the subtrees below it at the same level (not always the immediate next subtree) wil...>I've managed to generate a different bug now: subtrees can get duplicated. Specifically, if I close one subtree (at any level), the indicator for one of the subtrees below it at the same level (not always the immediate next subtree) will also change to closed, and tapping it will "open" the subtree again, inserting it into the list a second time.Milestone Chttps://code.briarproject.org/briar/briar/-/issues/423Forum code re-factor2018-06-12T11:32:26ZErnir ErlingssonForum code re-factor* Remove redundancy in nested for-loops
* Use `NO_POSITION` instead of -1 when applicable
* Some comments have improper indenting
* Make sure that `position` is not directly in `onBindViewHolder`* Remove redundancy in nested for-loops
* Use `NO_POSITION` instead of -1 when applicable
* Some comments have improper indenting
* Make sure that `position` is not directly in `onBindViewHolder`Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/424Forum post timestamps2018-06-12T11:32:26ZErnir ErlingssonForum post timestampsThere was some old logic upon forum post creation that I didn't quite understand:
`// Don't use an earlier timestamp than the newest post`
Find out what this is about and make appropriate changes if anyThere was some old logic upon forum post creation that I didn't quite understand:
`// Don't use an earlier timestamp than the newest post`
Find out what this is about and make appropriate changes if anyMilestone Dhttps://code.briarproject.org/briar/briar/-/issues/425Forum Event race-condition2018-06-12T11:32:26ZErnir ErlingssonForum Event race-conditionCurrently there exists a race condition in the event handler when new forum messages are received.
Note that this is related to #310 Currently there exists a race condition in the event handler when new forum messages are received.
Note that this is related to #310 https://code.briarproject.org/briar/briar/-/issues/426Forum improvements2018-06-12T11:32:26ZErnir ErlingssonForum improvements* Orientation changes should maintain the state of thread closures and text input
* clickable snack bar when applicable
* bottom divider should not be visible* Orientation changes should maintain the state of thread closures and text input
* clickable snack bar when applicable
* bottom divider should not be visibleMilestone Dhttps://code.briarproject.org/briar/briar/-/issues/427Loading authors2018-06-12T11:32:26ZErnir ErlingssonLoading authorsCurrently, in the forum, the author is loaded like this.
```
private void loadAuthor() throws DbException {
Collection<LocalAuthor> localAuthors =
identityManager.getLocalAuthors();
for (LocalAuthor author : localAuth...Currently, in the forum, the author is loaded like this.
```
private void loadAuthor() throws DbException {
Collection<LocalAuthor> localAuthors =
identityManager.getLocalAuthors();
for (LocalAuthor author : localAuthors) {
if (author == null)
continue;
data.setLocalAuthor(author);
break;
}
}
```
This follows the assumption that the first author (with a null safety check) is the correct author.
* Am I right to assume that we are following a single author scheme at the moment?
* Shouldn't we load up the author once, after login, and then just re-use that instance throughout the app ? Heck, we could even inject it.Milestone Fhttps://code.briarproject.org/briar/briar/-/issues/428Blog Post Activity2018-06-12T11:32:26ZTorsten GroteBlog Post ActivityThis ticket depends on #410 and #415.
When tapping on a long blog post, the post should open up in a dedicated activity. This activity should be implemented here.
![list_of_posts_-_post_overview](/uploads/3d1e667760f502a117211d6d3e...This ticket depends on #410 and #415.
When tapping on a long blog post, the post should open up in a dedicated activity. This activity should be implemented here.
![list_of_posts_-_post_overview](/uploads/3d1e667760f502a117211d6d3e9b1836/list_of_posts_-_post_overview.jpg)
The overflow menu hides the delete option (see #418)Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/429Explain that QR codes can not be scanned remotely2018-06-12T11:32:26ZTorsten GroteExplain that QR codes can not be scanned remotelyAlmost all people that I showed Briar to asked my to post my QR code into another chat app or to go into a WebRTC room to show my QR code in a webcam. Everytime I need to explain that this won't work, so it would be nice if it would some...Almost all people that I showed Briar to asked my to post my QR code into another chat app or to go into a WebRTC room to show my QR code in a webcam. Everytime I need to explain that this won't work, so it would be nice if it would somehow be clear from the app.Milestone BTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/430NPE in ForumSharingStatusActivity2018-06-12T11:32:26ZTorsten GroteNPE in ForumSharingStatusActivity```
java.lang.NullPointerException
at org.briarproject.android.contact.BaseContactListAdapter.onBindViewHolder(BaseContactListAdapter.java:55)
at org.briarproject.android.contact.BaseContactListAdapter.onBindViewHolder(BaseCon...```
java.lang.NullPointerException
at org.briarproject.android.contact.BaseContactListAdapter.onBindViewHolder(BaseContactListAdapter.java:55)
at org.briarproject.android.contact.BaseContactListAdapter.onBindViewHolder(BaseContactListAdapter.java:23)
```Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/431New Design for Navigation Drawer2019-02-26T14:44:09ZTorsten GroteNew Design for Navigation DrawerWe have a new navigation drawer now that looks like this:
![device-2016-06-02-191101](/uploads/28ab48ef3a7e921375313de3c4783547/device-2016-06-02-191101.png)
The Briar logo in the header is just provisional and should be replaced w...We have a new navigation drawer now that looks like this:
![device-2016-06-02-191101](/uploads/28ab48ef3a7e921375313de3c4783547/device-2016-06-02-191101.png)
The Briar logo in the header is just provisional and should be replaced with a nice header graphics. Maybe this should already take an identity selector into account? Here's an example of how it looks like for other apps:
![p6rjm](/uploads/2f2e0b6ea476f60ae72225ef21e016e0/p6rjm.png)
Some feature futures that should maybe be taken into account already:
* More data transports might be added later and users will probably be able to turn individual transports on/off
* More identities will be supported, so maybe the last two used should be in the account header
* More features might be added that will be added to the navigation drawer menu as wellhttps://code.briarproject.org/briar/briar/-/issues/432Design consistent visual elements for empty states, error messages and navidr...2018-06-12T11:32:26ZMegaloxDesign consistent visual elements for empty states, error messages and navidrawer headerSubtickets:
* empty states #327
* error messages #380
* navigation drawer #431Subtickets:
* empty states #327
* error messages #380
* navigation drawer #431https://code.briarproject.org/briar/briar/-/issues/433ForumPersistentData does not work2018-06-12T11:32:26ZTorsten GroteForumPersistentData does not workThe idea of `ForumPersistentData` is to keep its data in memory as long as the activity lives, so that you can rotate your screen and the data does not need to be loaded from the database again.
However, when you go to a forum and rot...The idea of `ForumPersistentData` is to keep its data in memory as long as the activity lives, so that you can rotate your screen and the data does not need to be loaded from the database again.
However, when you go to a forum and rotate your screen, the data is loaded from the database again. I am facing the same problem with blogs.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/434Tor: Could not parse my own descriptor2019-02-25T09:55:40ZTorsten GroteTor: Could not parse my own descriptorI am running Briar in an emulator and suddenly my log gets spamed with these:
```
6-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
06-15 11:17:17.656 10108-11546/org.bri...I am running Briar in an emulator and suddenly my log gets spamed with these:
```
6-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
06-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN rend_encode_v2_descriptors(): Bug: Could not parse my own descriptor: rendezvous-service-descriptor zzqy2x5mk2kgo4lie44345uzc37xp7gk version 2 permanent-key -----BEGIN RSA PUBLIC KEY----- MIGJAoGBAO8OZaFqUOdslKsUllgU2pHZ4byDLgQF3MeXBRq6NGGCHdQ0k0OAqmq7 AE/F8MPlfi4Nxv8gr3Cn3ePjLqP6ylEaL7sFEHtVDMEZYk9PSQ/o+UkzwMfu967y UymPH/vzAiytgBc4zQSbjatlUPFyrHgEkppcERzlCl0wjseKhUERAgMBAAE= -----END RSA PUBLIC KEY----- secret-id-part qbpaetzw5utrk5bs5y2j2wf7zsp5mrgp publication-time 1880-05-09 07:31:44 protocol-versions 2,3 introduction-points -----BEGIN MESSAGE----- aW50cm9kdWN0aW9uLXBvaW50IGJ5NnQ3dHJnNjJsanc2eGliemdrbnJncHZmNHly NHk2CmlwLWFkZHJlc3MgOTQuMjMuMjAuMjgKb25pb24tcG9ydCAyMzQyCm9uaW9u LWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlHSkFvR0JBTTZU akpxQ1BQZVVKQ0E0OVc1NGx0TEp6eEk2OXJtYjlZeTRLU1Y3SlRPbEV2NEVqZmt6 d3NERgplMWttaDRSeWE3alFoOG9XdlVBR2Uwb3E3ZFFUa1lCQ296azRtQ3dQOTA2 SkVPcVIxNjMwZ0phTTB6RXBib1Z2CmlHZWhzWjdwWEtGM1FVMVYxRjM3eFVkQldK aUdLcERyOW9pQ3FkWGhPSWVuZDAzNWh4VEhBZ01CQUFFPQotLS0tLUVORCBSU0Eg UFVCTElDIEtFWS0tLS0tCnNlcnZpY2Uta2V5Ci0tLS0tQkVHSU4gUlNBIFBVQkxJ QyBLRVktLS0tLQpNSUdKQW9HQkFPTFlRL3hhM1hoMFpCdkR6OS9Jcll4UWZid01I NDFZdmFVTjVrRVRnOUwranduYm84SHNBSTBPCjU4VjFGWTRyT2xyT3cvNWFsbzh4 TVdvSEpMMUlKMmhSMXBFRkt3cVNaN2pyMkozOHVKWHNXWGE0LzlFZWNOTEsKcFVU ZHFXellDbEJSSU9EOCt1TDNnK3lUUi9KcXdUa2R4Sk4yVHZtNUdwd0NneUpjMkZW aEFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMgS0VZLS0tLS0KaW50cm9kdWN0 aW9uLXBvaW50IGl3dnI2dXNjY2h2bWNxdnBoM3JwcHZibjJoYnh2MnoyCmlwLWFk ZHJlc3MgODEuMjI5LjM2LjIwMwpvbmlvbi1wb3J0IDE3ODgKb25pb24ta2V5Ci0t LS0tQkVHSU4gUlNBIFBVQkxJQyBLRVktLS0tLQpNSUdKQW9HQkFOSzA3NzUxZUlp bmZRa3Q4MFZ0ai9nZU5lVjJNdGxUM0ZyTE9HUGcybHNhb09ydWV1SVdSekxZCkxR VGlUemlyTDJ2TzBlUnZLVkJ1VVpiNklLSWtmb0FRZEMzODFSd2VRc2xBMkk3MzMv VXpRYm9nTHlhREFIZEEKRVR4QmQ3V0tLNFExQWpxVGIwUDNyOTBoQ3J2RWk5MDN3 QmxOakRxbTR6b2JaVG1VUVRyOUFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMg S0VZLS0tLS0Kc2VydmljZS1rZXkKLS0tLS1CRUdJTiBSU0EgUFVCTElDIEtFWS0t LS0tCk1JR0pBb0dCQU1UQTQ5RUUyYkxZN1NXU0xkVXZHZXhRVDZ1UVFPUDBoL1Vi MU9CZVFuQkIxVkxxNFRoU3FNK0oKaDlXSlAwTUk0TGlNeHV3ODBhZjJHK0REczlv MGNUakRUdmxVNlQvc0lXdlVDSWVHVTlRcDVBRm5KSThmRTM2QwpjYUovNGJ1Vi90 L0JVODRpR2Fvd3pObG9zNmllK3pUbVZMcU9uU1I2S2l4cjh3cEZvWUU5QWdNQkFB RT0KLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0tLQppbnRyb2R1Y3Rpb24tcG9p bnQgZ213bmpjaXhwNHFjazRmaGFpanNyaWwyc2c3eWVvZWoKaXAtYWRkcmVzcyAx OTIuMTUwLjk0LjQ5Cm9uaW9uLXBvcnQgOTAwMQpvbmlvbi1rZXkKLS0tLS1CRUdJ TiBSU0EgUFVCTElDIEtFWS0tLS0tCk1JR0pBb0dCQUxpWXppQ1gwSFM5eVd1VTNo TFRrZ0F6TGhYS0l3eFRyanVtQmVrdXBYRzRJM0laOWNPbmttNmEKcFhzUlRGaTF5 NXBiWWNvTzRMTmw1SnBndVJaYVJGR29KZmVJallkNTdXTW5xTkRoUlhzWHVrVW5l TkVHaHFZeApSVEJiMlRZWTlpVW1JSEZSMElrblZtOEFCVFIrNDlJRUFZaUkvNy9s a2FTMlQza2lSZ3NqQWdNQkFBRT0KLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0t LQpzZXJ2aWNlLWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlH SkFvR0JBTEtCYXNHN09MNGYyUDdrQW5INDFIV1RSY092TnRlMkFRdkc0VkxKOXJ5 SjBLN0NCN3Zqd3dMbAo1L21WaVh0ZzNid3JDQ3MvYnI4S2pOd29MZEhIRHU1cmJP S3VlNWxnV0VSYzV4cXk0eGkzcGtORk0wUDlTaUZaCm9QOUlRcCtDeUZRZVlLVlNP K3RPOFBzVHozK0xQdjlRcEFDSmdJSnlaTnMwMnA5L0VOeGhBZ01CQUFFPQotLS0t LUVORCBSU0EgUFVCTElDIEtFWS0tLS0tCgo= -----END MESSAGE----- signature -----BEGIN SIGNATURE----- NILJpinHVXuLzc/FKxxcXsB8cQXmPvD4xi6+D/JDM6SiRffsRRWoWcIufOvWRUZM gAf55SxV1M+jVFhw1gGNfjbBo56hytfmPQdhF9ucoPHlZA90kytyTgBtPiw9qeQG n5pcPq8qmpG9dlEfYOK1EJkYTIieYkXrNB4B5Zyju0I= -----END SIGNATURE----- (on Tor 0.2.7.6 )
06-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN upload_service_descriptor(): Bug: Internal error: couldn't encode service descriptor; not uploading. (on Tor 0.2.7.6 )
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN ISO time "1880-05-09 07:31:44" was nonsensical
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN rend_encode_v2_descriptors(): Bug: Could not parse my own descriptor: rendezvous-service-descriptor zzqy2x5mk2kgo4lie44345uzc37xp7gk version 2 permanent-key -----BEGIN RSA PUBLIC KEY----- MIGJAoGBAO8OZaFqUOdslKsUllgU2pHZ4byDLgQF3MeXBRq6NGGCHdQ0k0OAqmq7 AE/F8MPlfi4Nxv8gr3Cn3ePjLqP6ylEaL7sFEHtVDMEZYk9PSQ/o+UkzwMfu967y UymPH/vzAiytgBc4zQSbjatlUPFyrHgEkppcERzlCl0wjseKhUERAgMBAAE= -----END RSA PUBLIC KEY----- secret-id-part qbpaetzw5utrk5bs5y2j2wf7zsp5mrgp publication-time 1880-05-09 07:31:44 protocol-versions 2,3 introduction-points -----BEGIN MESSAGE----- aW50cm9kdWN0aW9uLXBvaW50IGJ5NnQ3dHJnNjJsanc2eGliemdrbnJncHZmNHly NHk2CmlwLWFkZHJlc3MgOTQuMjMuMjAuMjgKb25pb24tcG9ydCAyMzQyCm9uaW9u LWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlHSkFvR0JBTTZU akpxQ1BQZVVKQ0E0OVc1NGx0TEp6eEk2OXJtYjlZeTRLU1Y3SlRPbEV2NEVqZmt6 d3NERgplMWttaDRSeWE3alFoOG9XdlVBR2Uwb3E3ZFFUa1lCQ296azRtQ3dQOTA2 SkVPcVIxNjMwZ0phTTB6RXBib1Z2CmlHZWhzWjdwWEtGM1FVMVYxRjM3eFVkQldK aUdLcERyOW9pQ3FkWGhPSWVuZDAzNWh4VEhBZ01CQUFFPQotLS0tLUVORCBSU0Eg UFVCTElDIEtFWS0tLS0tCnNlcnZpY2Uta2V5Ci0tLS0tQkVHSU4gUlNBIFBVQkxJ QyBLRVktLS0tLQpNSUdKQW9HQkFPTFlRL3hhM1hoMFpCdkR6OS9Jcll4UWZid01I NDFZdmFVTjVrRVRnOUwranduYm84SHNBSTBPCjU4VjFGWTRyT2xyT3cvNWFsbzh4 TVdvSEpMMUlKMmhSMXBFRkt3cVNaN2pyMkozOHVKWHNXWGE0LzlFZWNOTEsKcFVU ZHFXellDbEJSSU9EOCt1TDNnK3lUUi9KcXdUa2R4Sk4yVHZtNUdwd0NneUpjMkZW aEFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMgS0VZLS0tLS0KaW50cm9kdWN0 aW9uLXBvaW50IGl3dnI2dXNjY2h2bWNxdnBoM3JwcHZibjJoYnh2MnoyCmlwLWFk ZHJlc3MgODEuMjI5LjM2LjIwMwpvbmlvbi1wb3J0IDE3ODgKb25pb24ta2V5Ci0t LS0tQkVHSU4gUlNBIFBVQkxJQyBLRVktLS0tLQpNSUdKQW9HQkFOSzA3NzUxZUlp bmZRa3Q4MFZ0ai9nZU5lVjJNdGxUM0ZyTE9HUGcybHNhb09ydWV1SVdSekxZCkxR VGlUemlyTDJ2TzBlUnZLVkJ1VVpiNklLSWtmb0FRZEMzODFSd2VRc2xBMkk3MzMv VXpRYm9nTHlhREFIZEEKRVR4QmQ3V0tLNFExQWpxVGIwUDNyOTBoQ3J2RWk5MDN3 QmxOakRxbTR6b2JaVG1VUVRyOUFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMg S0VZLS0tLS0Kc2VydmljZS1rZXkKLS0tLS1CRUdJTiBSU0EgUFVCTElDIEtFWS0t LS0tCk1JR0pBb0dCQU1UQTQ5RUUyYkxZN1NXU0xkVXZHZXhRVDZ1UVFPUDBoL1Vi MU9CZVFuQkIxVkxxNFRoU3FNK0oKaDlXSlAwTUk0TGlNeHV3ODBhZjJHK0REczlv MGNUakRUdmxVNlQvc0lXdlVDSWVHVTlRcDVBRm5KSThmRTM2QwpjYUovNGJ1Vi90 L0JVODRpR2Fvd3pObG9zNmllK3pUbVZMcU9uU1I2S2l4cjh3cEZvWUU5QWdNQkFB RT0KLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0tLQppbnRyb2R1Y3Rpb24tcG9p bnQgZ213bmpjaXhwNHFjazRmaGFpanNyaWwyc2c3eWVvZWoKaXAtYWRkcmVzcyAx OTIuMTUwLjk0LjQ5Cm9uaW9uLXBvcnQgOTAwMQpvbmlvbi1rZXkKLS0tLS1CRUdJ TiBSU0EgUFVCTElDIEtFWS0tLS0tCk1JR0pBb0dCQUxpWXppQ1gwSFM5eVd1VTNo TFRrZ0F6TGhYS0l3eFRyanVtQmVrdXBYRzRJM0laOWNPbmttNmEKcFhzUlRGaTF5 NXBiWWNvTzRMTmw1SnBndVJqYVJGR29KZmVJallkNTdXTW5xTkRoUlhzWHVrVW5l TkVHaHFZeApSVEJiMlRZWTlpVW1JSEZSMElrblZtOEFCVFIrNDlJRUFZaUkvNy9s a2FTMlQza2lSZ3NqQWdNQkFBRT0BLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0t LQpzZXJ2aWNlLWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlH SkFvR0JBTEtCYXNHN09MNGYyUDdrQW5INDFIV1RSY092TnRlMkFRdkc0VkxKOXJ5 SjBLN0NCN3Zqd3dMbAo1L21WaVh0ZzNid3JDQ3MvYnI4S2pOd29MZEhIRHU1cmJP S3VlNWxnV0VSYzV4cXk0eGkzcGtORk0wUDlTaUZaCm9QOUlRcCtDeUZRZVlLVlNP K3RPOFBzVHozK0xQdjlRcEFDSmdJSnlaTnMwMnA5L0VOeGhBZ01CQUFFPQotLS0t LUVORCBSU0EgUFVCTElDIEtFWS0tLS0tCgo= -----END MESSAGE----- signature -----BEGIN SIGNATURE----- NILJpinHVXuLzc/FKxxcXsB8cQXmPvD4xi6+D/JDM6SiRffsRRWoWcIufOvWRUZM gAf55SxV1M+jVFhw1gGNfjbBo56hytfmPQdhF9ucoPHlZA90kytyTgBtPiw9qeQG n5pcPq8qmpG9dlEfYOK1EJkYTIieYkXrNB4B5Zyju0I= -----END SIGNATURE----- (on Tor 0.2.7.6 )
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN upload_service_descriptor(): Bug: Internal error: couldn't encode service descriptor; not uploading. (on Tor 0.2.7.6 )
06-15 11:17:19.656 10108-11546/org.briarproject I/TorPlugin: WARN ISO time "1880-05-09 07:31:44" was nonsensical
06-15 11:17:19.657 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
```
Please note that the time of the emulator is correct.https://code.briarproject.org/briar/briar/-/issues/435Generalise ForumSharingIntegrationTest2020-11-21T18:58:09Zstr4dGeneralise ForumSharingIntegrationTestAs part of #403, `ForumSharingManager` was generalised into a `SharingManager` that is subclassed per-shareable.
`ForumSharingIntegrationTest` should be similarly generalised to ensure that the common behaviour is consistent across all ...As part of #403, `ForumSharingManager` was generalised into a `SharingManager` that is subclassed per-shareable.
`ForumSharingIntegrationTest` should be similarly generalised to ensure that the common behaviour is consistent across all subclasses (and to reduce duplication).https://code.briarproject.org/briar/briar/-/issues/436Automatic Personal Blogs2018-06-12T11:32:26ZTorsten GroteAutomatic Personal BlogsAll users should have a blog by default and automatically subscribe to the default blog of their contacts. The blogs of the contacts should show up in the combined feed (#417). Writing a new post into the default blog should be quick an...All users should have a blog by default and automatically subscribe to the default blog of their contacts. The blogs of the contacts should show up in the combined feed (#417). Writing a new post into the default blog should be quick and easy.
As for other blogs, the group descriptor is a BDF list with three elements: `name` (string), `author_name` (string) and the author's long-term `public_key` (raw). The name should be a deterministic identifier that is either known beforehand or can be calculated from the given information. I would suggest to not use "$author_name's blog" as the internal name to allow for localization. The name could be something like "org.briaproject.BLOG_NAME" which will be shown as "$Author's blog" in an English UI.
This is a sub-ticket of #134.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/437Blog Comments2018-06-12T11:32:26ZTorsten GroteBlog CommentsCommenting on blog posts works by reblogging the original post into one's own blog and adding a comment. Comments are visible to subscribers of the commenter's blog.
The reblogged post would be wrapped in a new message that would be p...Commenting on blog posts works by reblogging the original post into one's own blog and adding a comment. Comments are visible to subscribers of the commenter's blog.
The reblogged post would be wrapped in a new message that would be posted to the reposter's blog. The new message would include a signature by the reposter and an optional comment, and it would be distributed to the reposter's subscribers in the same way as a normal post.
Reading a few Tumblr blogs is the easiest way to understand how this style of commenting works. See http://awkwardvagina.com/ for example (don't worry about the URL, it's just a typical Tumblr blog full of reblogged memes and jokes).Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/438Extract general means for loading body content in background2020-11-21T18:56:48Zstr4dExtract general means for loading body content in backgroundPer [this comment](https://code.briarproject.org/akwizgran/briar/merge_requests/209#note_6830):
> Fetching content is also needed for blogs and I think also forums. Maybe there's a way to somehow generalize this either further so it can...Per [this comment](https://code.briarproject.org/akwizgran/briar/merge_requests/209#note_6830):
> Fetching content is also needed for blogs and I think also forums. Maybe there's a way to somehow generalize this either further so it can be reused by other clients as well.https://code.briarproject.org/briar/briar/-/issues/439Compare TRVE Data with BSP2020-11-21T18:55:43Zstr4dCompare TRVE Data with BSPFrom the research team we are talking with about performance / battery life measurements (for #115). It sounds like it has a lot of overlap with BSP; it would be interesting to know in what ways the approaches differ.
http://www.cl.cam....From the research team we are talking with about performance / battery life measurements (for #115). It sounds like it has a lot of overlap with BSP; it would be interesting to know in what ways the approaches differ.
http://www.cl.cam.ac.uk/research/dtg/trve/
https://github.com/trvedatahttps://code.briarproject.org/briar/briar/-/issues/440SSLHandshakeException when trying to build from source2018-06-12T11:32:25ZmakleiSSLHandshakeException when trying to build from sourceAndroid Studio under Windows give me this error :
:briar-android:downloadTorBinaryArm FAILED
Error:Execution failed for task ':briar-android:downloadTorBinaryArm'.
> javax.net.ssl.SSLHandshakeException: sun.security.validator.Valida...Android Studio under Windows give me this error :
:briar-android:downloadTorBinaryArm FAILED
Error:Execution failed for task ':briar-android:downloadTorBinaryArm'.
> javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Do you know how can I resolve this?
Thank you in advance for your help. Milestone Fakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/441Group descriptor can be too long, causes crash2018-06-12T11:32:25ZTorsten GroteGroup descriptor can be too long, causes crashThere is a constant `MAX_GROUP_DESCRIPTOR_LENGTH` which is currently set to `100`.
Now there's two problems:
* The group descriptor of forums is currently a `BdfList` of the forums's name (100) and a salt (65).
* The group descript...There is a constant `MAX_GROUP_DESCRIPTOR_LENGTH` which is currently set to `100`.
Now there's two problems:
* The group descriptor of forums is currently a `BdfList` of the forums's name (100) and a salt (65).
* The group descriptor of blogs is currently a `BdfList` of the blog's name (100), the author's name (50) and her public key (65).
In both cases, the limit can be exceeded leading to a hard crash.
What is the reason for `MAX_GROUP_DESCRIPTOR_LENGTH` and can we just increase it as needed?Milestone DTorsten GroteTorsten Grote