briar merge requestshttps://code.briarproject.org/briar/briar/-/merge_requests2017-07-07T12:25:26Zhttps://code.briarproject.org/briar/briar/-/merge_requests/562Alert every time2017-07-07T12:25:26ZJulian DehmAlert every timeThe current notification design will only alert for the first notification, subsequent will only be displayed. This is bad because we combine all messages from a certain type (private, group, forum, blog) into one notification. For examp...The current notification design will only alert for the first notification, subsequent will only be displayed. This is bad because we combine all messages from a certain type (private, group, forum, blog) into one notification. For example, if there is an active notification for a group message in group A, there won't be any alerts for new messsages in any other group. You can easily miss messages this way.
Signed-off-by: goapunk <noobie@goapunks.net>https://code.briarproject.org/briar/briar/-/merge_requests/532WIP:Don't rely on notifyDataSetChanged recreating the ViewHolders2017-07-07T12:33:23ZJulian DehmWIP:Don't rely on notifyDataSetChanged recreating the ViewHoldersnotifyDataSetChanged does not trigger a recreation of the ViewHolders, it only calls onBindViewHolder.
Signed-off-by: goapunk <noobie@goapunks.net>notifyDataSetChanged does not trigger a recreation of the ViewHolders, it only calls onBindViewHolder.
Signed-off-by: goapunk <noobie@goapunks.net>https://code.briarproject.org/briar/briar/-/merge_requests/615Resolve "Bluetooth remains active after adding contact"2018-01-09T12:36:38ZMajorCrazedResolve "Bluetooth remains active after adding contact"Closes #299
Bluetooth is now enabled by default.
But if the user change the settings to enable Bluetooth just for the contact exchange than it would be disabled after adding the contact.Closes #299
Bluetooth is now enabled by default.
But if the user change the settings to enable Bluetooth just for the contact exchange than it would be disabled after adding the contact.akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/merge_requests/599Added Doxyfile for doxygen documentation.2018-01-09T12:37:22ZDaniel SteinhauerAdded Doxyfile for doxygen documentation.Start an API documentation using *Doxygen*.
Documentation for **briar-core**, **briar-api**, **brumble-core** and **brumble-api**.Start an API documentation using *Doxygen*.
Documentation for **briar-core**, **briar-api**, **brumble-core** and **brumble-api**.https://code.briarproject.org/briar/briar/-/merge_requests/676WIP: Add copy and paste support for (Threaded-)Conversations2018-06-14T12:00:40ZJulian DehmWIP: Add copy and paste support for (Threaded-)ConversationsI experimented with this some time ago, we could use this as a base for discussions. Not sure if inheritance is the best way to go here but it seemed the easiest to me.
Signed-off-by: goapunk <noobie@goapunks.net>
Closes #9I experimented with this some time ago, we could use this as a base for discussions. Not sure if inheritance is the best way to go here but it seemed the easiest to me.
Signed-off-by: goapunk <noobie@goapunks.net>
Closes #9https://code.briarproject.org/briar/briar/-/merge_requests/894Allow retransmission if it will result in faster delivery2018-08-21T11:34:53ZJulian DehmAllow retransmission if it will result in faster deliveryAs proposed by @akwizgran this will save the time a message got sent (or rather picked up by a session) instead of saving the expiry time. This has the advantage that the next send-time is calculated based on the currently used transport...As proposed by @akwizgran this will save the time a message got sent (or rather picked up by a session) instead of saving the expiry time. This has the advantage that the next send-time is calculated based on the currently used transport and not forced by the transport which previously sent it (as we do it right now). This will allow us to resend a message if the current transport is faster.
Closes #541https://code.briarproject.org/briar/briar/-/merge_requests/850WIP: Add special purpose contacts2019-02-05T12:58:21ZJulian DehmWIP: Add special purpose contactsFirst approach to distinguishable contact types:
* Start with four contact types (CONTACT, PRIVATE_MAILBOX, CONTACT_MAILBOX and MAILBOX_OWNER)
* getContacts will only return regular contacts, getAllContacts() will return contacts of ev...First approach to distinguishable contact types:
* Start with four contact types (CONTACT, PRIVATE_MAILBOX, CONTACT_MAILBOX and MAILBOX_OWNER)
* getContacts will only return regular contacts, getAllContacts() will return contacts of every type
* ContactHooks now declare which type of contacts they want to receive.
* Adds a database migrationMailbox Prototypehttps://code.briarproject.org/briar/briar/-/merge_requests/1175WIP: Replace gradle-witness with checksum-dependency plugin2021-08-05T10:22:31ZJulian DehmWIP: Replace gradle-witness with checksum-dependency pluginSomething I played around with following @vlsi hint here: https://code.briarproject.org/briar/briar/issues/1488#note_38104
Feels much smoother than gradle witness and is actively maintained by @vlsi - so might be worth a look.
Switch...Something I played around with following @vlsi hint here: https://code.briarproject.org/briar/briar/issues/1488#note_38104
Feels much smoother than gradle witness and is actively maintained by @vlsi - so might be worth a look.
Switching between GPG and SHA512 is as easy as it gets. I used the default of GPG and sha512 as fallback here, sha512 only might be safer though?
Solves #1613