briar issueshttps://code.briarproject.org/briar/briar/-/issues2020-11-15T15:34:28Zhttps://code.briarproject.org/briar/briar/-/issues/1748User testing for transport toggles, second round2020-11-15T15:34:28ZakwizgranUser testing for transport toggles, second roundSubtask of #1723.Subtask of #1723.https://code.briarproject.org/briar/briar/-/issues/1690Add private message deletion to user manual2020-11-15T17:10:49ZakwizgranAdd private message deletion to user manualCleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1578Improve structure of Briar Headless API documentation2021-03-22T10:52:52ZNicoImprove structure of Briar Headless API documentationCurrently, the documentation for the API is directly written into [its readme file](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md). That's fine for the beginning, [I was even able to build a first ...Currently, the documentation for the API is directly written into [its readme file](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md). That's fine for the beginning, [I was even able to build a first prototype with it](https://nico.dorfbrunnen.eu/posts/2019/briar-first-demo/).
However, I suggest to improve the structure of the documentation by moving it into a separate repository. My suggestion was to create a Hugo page with a docs theme (or some other static site generator) at docs.briarproject.org.
@grote's response to this was (loosely translated by me): "Best to make the documentation directly into the code with swagger"
My response to this now: OK, we can do this, but I don't know how much sense it makes to put a lot of basic explanations into code. E.g. all the valuable information collected in https://code.briarproject.org/briar/briar/issues/1577.
**Update:** I agree with Torsten that it's best to generate the documentation from code. That's what I do with [`briar_wrapper`](https://code.briarproject.org/briar/python-briar-wrapper), too, at https://wrapper.docs.briarproject.org/ and the API's docs can be hosted at https://api.docs.briarproject.org/, imho.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1531Update threat model document2020-11-15T18:57:13ZakwizgranUpdate threat model documentThe [threat model document](https://code.briarproject.org/briar/briar/wikis/threat-model) on the wiki is out of date, and it doesn't mention the goal of concealing the fact that Briar is being used. The document should be updated.The [threat model document](https://code.briarproject.org/briar/briar/wikis/threat-model) on the wiki is out of date, and it doesn't mention the goal of concealing the fact that Briar is being used. The document should be updated.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1472Explain how Briar is different (rename the "blog"?)2022-11-18T17:24:07ZBjarni RĂșnar EinarssonExplain how Briar is different (rename the "blog"?)Hi! Thanks for Briar, I'm very impressed with what you've done so far.
I was testing it for a bit (the wife and I now have the world's most secure shopping-list app!), and I wanted to share my first impression before it fades. Please fe...Hi! Thanks for Briar, I'm very impressed with what you've done so far.
I was testing it for a bit (the wife and I now have the world's most secure shopping-list app!), and I wanted to share my first impression before it fades. Please feel free to close this issue if you feel it's unhelpful or redundant.
Basically, my dominant feeling was confusion.
What is all this stuff? How does it work? The messages and contacts are straightforward, and the private groups as well... but the forums and blogs had me scratching my head. I still don't fully get them.
How do people discover a blog, or a forum? Are they completely public? Are they shared word-of-mouth over messages? Are there any access controls?
The fact that I couldn't edit or delete blog posts after writing a couple of inane tests was very unsettling - this goes against the expectations any normal user will have for something named "blog", and it's bad enough that after perfectly normal "test behaviour" one is likely going to be forced to delete one's account and start over because anyone with a quirky (let alone risque) sense of humour is likely to write "test posts" that absolutely shouldn't stay on the public record.
I'm technical enough to understand that a lot of this has to do with the underlying p2p distribution, and is also likely emergent from the design goal of making things censorship resistant. But for someone less technical, these limitations are simply baffling and disconcerting. They're also a major roadblock to adoption - I will never use a blog like this as a casual, social tool for expressing myself, and I would strongly recommend against their use to anyone else as well. For personal safety, being able to edit and delete and curate ones' public identity is vital.
There is absolutely a place and a need in this world for a feature like this - but my personal feeling is it needs to be carefully explained and shouldn't be called "blog", as that word implies all sorts of casual social interactions which this is simply inappropriate for (in its current iteration).
But obviously these are just my opinions, I hope they're helpful!CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1312Include user manual in app2022-11-18T17:32:16ZakwizgranInclude user manual in appA user asked for the manual to be included in the app. This was always the plan but it doesn't look like we had a ticket for it.
Related to #94, #315.A user asked for the manual to be included in the app. This was always the plan but it doesn't look like we had a ticket for it.
Related to #94, #315.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1244Update manual for image attachments2021-11-04T11:04:01ZakwizgranUpdate manual for image attachmentsSubtask of #1237.Subtask of #1237.Android 1.4CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1238Design changes to sync protocol to support multi-block messages2022-06-15T12:02:16ZakwizgranDesign changes to sync protocol to support multi-block messagesSubtask of #1237.Subtask of #1237.Multi-block messageshttps://code.briarproject.org/briar/briar/-/issues/1231Design protocol for adding contacts remotely2023-02-22T18:15:44ZakwizgranDesign protocol for adding contacts remotelySubtask of #1230.Subtask of #1230.akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1208Explain what the clock icon means2022-11-29T14:31:01ZPratiwirExplain what the clock icon meansI am getting a clock symbol for each new chat bubble. I switched to tor, the connection is working. 3 days of trial left. I go to the main contacts screen and select the top left three bars menu, at the bottom left both internet and wifi...I am getting a clock symbol for each new chat bubble. I switched to tor, the connection is working. 3 days of trial left. I go to the main contacts screen and select the top left three bars menu, at the bottom left both internet and wifi symbols are green.
Each contact displays how long ago I typed a message.
I'd like to see some way to get the server status if possible, ideally the response time could be translated to a color with a note of the last round trip time.
I don't know the server ip, in fact multiping on android seems to be working fine over tor.
Just don't know if the server is down or it is some other problem.https://code.briarproject.org/briar/briar/-/issues/1197Manual section needed for Bluetooth and Wi-fi.2020-11-18T22:43:47ZPratiwirManual section needed for Bluetooth and Wi-fi.I initially loaded Briar on three devices and added each to the other as a contact, as in the manual. I had bluetooth turned on and wi-fi too. The manual says that after scanning the QR code the devices will exchange information and the ...I initially loaded Briar on three devices and added each to the other as a contact, as in the manual. I had bluetooth turned on and wi-fi too. The manual says that after scanning the QR code the devices will exchange information and the contacts will be added. This works fine, but what isn't clear is how the process takes place. "You must meet up with the person you want to add as a contact." This implies that bluetooth or local Wi-fi is being used silently. This assumption creates confusion because I then assumed that in Android one just has to have the services activated and the rest is taken care of, as you might expect for easy use in a crisis.
I now think that for the devices to send local messages one has to host a hotspot over Wi-fi or bluetooth. So this should be clear in the manual, how to set up the Wi-fi links or bluetooth links properly and what the requirement is for adding contacts. Is it local bluetooth turned on, paired devices required or not, Wi-fi transmitters active, or logged onto same network, full internet access? Can both QR codes be sent by secure e-mail and scanned by the camera at remote locations at the same time, what is the time wimdow?
"If the internet's down, Briar can sync via Bluetooth or Wi-Fi, keeping the information flowing in a crisis." This is the only information in the manual and potentially wrong assumptions about it make actual testing and getting it working more difficult and confusing than it needs to be. The manual is quite compact, but needs additional concise information about what is going on.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1179Handshake protocol2020-11-18T22:39:28ZakwizgranHandshake protocolTo enable account backups (#110) and simplify the introduction protocol (#474) it would be useful to have a way of bootstrapping from static keys, suitable for storing in a backup or exchanging in an introduction, to forward secret trans...To enable account backups (#110) and simplify the introduction protocol (#474) it would be useful to have a way of bootstrapping from static keys, suitable for storing in a backup or exchanging in an introduction, to forward secret transport keys.https://code.briarproject.org/briar/briar/-/issues/304Block path algorithms for BSP2022-06-15T12:02:16ZakwizgranBlock path algorithms for BSPDescribe how to calculate which hashes belong to a block's path, given the block number and message length.
Subtask of #249.Describe how to calculate which hashes belong to a block's path, given the block number and message length.
Subtask of #249.Multi-block messagesakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/137API documentation for Bramble library2020-11-21T19:42:23ZakwizgranAPI documentation for Bramble libraryakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/102Describe how messages are delivered2021-01-13T10:59:20ZakwizgranDescribe how messages are deliveredCleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/86Explain the app's privacy properties2021-02-17T19:06:53ZakwizgranExplain the app's privacy propertiesA user asked for a screen to be shown when the app was first run, explaining what privacy properties the app could and couldn't provide.A user asked for a screen to be shown when the app was first run, explaining what privacy properties the app could and couldn't provide.CleopatraCleopatra