briar-devel Mailing List for Briar

I've been on briar-devel, I think, for a very long time, and not seen
much lately.  I'm contemplating trying to organize a few locals (many of
whom might be more or less normies) to explore various schemes with some
combination of resilient to loss of internet and secure.  Briar is
obviously high on the list.

A few questions:

  - Is there some other place, vs this list?

  - I see a release end of 2025, which is recent.  yay!  What's the
    level of activity?  What's the prognosis?

  - Last I heard, running a tor HS was inconsistent with using a phone
    on battery.  Still the case?

  - Are people running nodes on a small computer on wifi (with backup
    power) at a central physical place in the community, so that those
    who come by  can exchange messages?  Is this a  sane thing to try to
    set up?

  - Is the mailbox ready for actual use, even if very beta, vs only
    suitable for use in developing the mailbox?

  - Is anyone working on something like using the LoRa nodes that people
    use with meshtastic, or using some kind of data over meshtastic?

  - Any thoughts on Reticulum?  (Unfortunately it's not open source; I
    started using it when it was and stopped -- but it's still
    interesting.)

  - Is there a story on iOS other than "connect to your mailbox?" and
    "manually open it when you arrive at a peer"?
    

Hello Seraph,

thank you for your message! We indeed have some problems with Bluetooth 
in the latest version of Briar on newer Android devices. Fortunately, 
this will get fixed in the next release thanks to this code change:

https://code.briarproject.org/briar/briar/-/merge_requests/1845

Once you have had a connection via either Bluetooth or Tor, the devices 
should have exchanged their local LAN addresses and thus be able to 
communicate without data but while being on the same WiFi as well.

One security goal of Briar is keeping it secret that you're using Briar 
at all. Therefore, Briar doesn't announce itself on the LAN which would 
help in your situation, I guess.

Cheers,

~Nico



On 10/10/25 16:04, [?]_S3raph via briar-devel wrote:
> Hello! I'm Seraph, a user who feels that data should be in the hands of the people rather than the eyes of the greedy.
> 
> I downloaded Briar on three devices to test it's functionality before field use. The devices consist of:
> 1 × Samsung S23 Ultra (Samsung stock build, Android 15)
> 1 × Google Pixel 8a (Graphene OS, Android 16)
> 1 × Samsung Tab 7a (LineageOS, Android 16)
> 
> After attempting to verify that these devices could communicate via the described means, I have found that despite various checks of permissions and wiki visits, I am unable to connect these devices beyond the Tor networked internet function. LAN without data does not work. Bluetooth fails to connect on all devices, which was checked against every device against every device. The internet function works perfectly with initiation and return messages arriving within ~20s.
> 
> I am planning to install the PC software tomorrow, which I will test similarly.
> 
> I hope that this information can assist, and although any reply may be delayed, I would be more than happy to carry out any tests or requests you send for the betterment of this system, as I feel it provides vital function to those who need it the most.
> 
> My apologies if this is not what is required. I am rather excited by the prospect of this system, and only want to assist.
> 
> If you wish to contact me, you may call me Seraph. (She/her if that helps.)
> 
> Sent from the Halo's Light.
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

Hello! I'm Seraph, a user who feels that data should be in the hands of the people rather than the eyes of the greedy. 

I downloaded Briar on three devices to test it's functionality before field use. The devices consist of:
1 × Samsung S23 Ultra (Samsung stock build, Android 15)
1 × Google Pixel 8a (Graphene OS, Android 16)
1 × Samsung Tab 7a (LineageOS, Android 16)

After attempting to verify that these devices could communicate via the described means, I have found that despite various checks of permissions and wiki visits, I am unable to connect these devices beyond the Tor networked internet function. LAN without data does not work. Bluetooth fails to connect on all devices, which was checked against every device against every device. The internet function works perfectly with initiation and return messages arriving within ~20s.

I am planning to install the PC software tomorrow, which I will test similarly.

I hope that this information can assist, and although any reply may be delayed, I would be more than happy to carry out any tests or requests you send for the betterment of this system, as I feel it provides vital function to those who need it the most.

My apologies if this is not what is required. I am rather excited by the prospect of this system, and only want to assist.

If you wish to contact me, you may call me Seraph. (She/her if that helps.)

Sent from the Halo's Light.

Hi Justin,

Thanks for spreading the word about Briar. Responses inline below...

On 11/10/2024 09:18, Justin McAfee wrote:
> Good morning team,
> 
> I live in TN where we were most recently struck by horrific flooding 
> after Helene that has crippled around 20% of our cellular infrastructure.
> 
> I'm in the process of writing a white paper and doing some proof of 
> concepts to get the word out about Briar and encourage my local 
> auxiliary communications groups, and others to make use of the software.
> 
> I'd like to contribute pull requests as well but believe my access is 
> pending in gitlab.

Sorry about that - I've just approved your account.

> I'd also like to ask some technical and feasibility questions if anyone 
> has time.
> 
> 1) I've ran multiple packet captures on Briar and can't find broadcast 
> traffic or similar to see clients finding each other on a LAN. Is this 
> pulled off by some other means?

Briar doesn't use LAN discovery because one of our design goals is that 
it should be difficult for nearby observers to detect whether Briar is 
being used. It's possible that we'll revisit this decision in the 
future, because LAN discovery would improve offline connectivity 
(although only on small LANs, as larger LANs don't usually allow 
multicast and may not allow clients to connect to each other at all).

Briar gets around the lack of a discovery mechanism by storing a list of 
its most recently used LAN addresses, including the link-local IPv6 
address, and syncing this list with contacts whenever a connection is 
available over any transport. When your device sees that it's on a LAN 
that's compatible with a LAN address shared by a contact, it tries to 
connect to that address.

In practice this means that if you and a contact are on a LAN that 
either of you has used before, you'll probably be able to connect to 
each other, even if the LAN doesn't support multicast. If you're on a 
LAN that neither of you has used before, you *may* be able to connect 
via IPv6, depending on whether your device uses a different link-local 
address for each LAN (on Android this varies between device models and 
Android versions). If IPv6 doesn't work then you'll need to connect to 
each other via Bluetooth or Tor and exchange your updated lists of LAN 
addresses before being able to make a LAN connection.

> 2) What back end infrastructure exist to facilitate coordination over 
> the internet/tor. Does briar run a coordination service?

We don't run a coordination service. Tor has a feature called onion 
services, which make it possible to receive connections via the Tor 
network at a stable and cryptographically secure address, even if your 
device can't receive incoming TCP connections due to NAT/firewall.

> 3) Is there a requirement for a continuous connection chain to exist for 
> messages to be relayed. E.g. given user A, B, and C. If all are contacts 
> and C wants to talk to A, using B as an intermediary does B have to be 
> in range to both A and C for messages to be relayed? Or do messages from 
> C, cache on B's device until they come back into contact with A?

There's no requirement for a continuous connection chain - messages are 
stored and forwarded. However, Briar has some rules about which messages 
will be stored/forwarded. A message will be synced between two devices 
if (1) the users of the devices are contacts, (2) the users both 
subscribe to the group where the message was posted, and (3) the users 
have chosen to share that subscription with each other.

In this context, "group" is a generic term that can mean a private chat 
between two people, a group chat, a forum, a blog, etc. "Sharing a 
subscription" can mean inviting someone to a group or accepting an 
invitation, etc.

In the case of a private chat between two people, the group is 
automatically created and shared when the users add each other as 
contacts. Nobody else subscribes to that group, so messages won't be 
synced with any other devices. If A sends a message to C in their 
private chat then it will never be synced to B.

Obviously this isn't ideal for offline communication! The sync rules 
were designed to protect metadata privacy, and there are some hard 
tradeoffs between offline connectivity and metadata privacy.

If offline connectivity is your priority then currently the least-bad 
solution is to create a forum and share it among all the users who want 
to communicate. For maximum connectivity, every user should add everyone 
else they meet as a contact and invite that person to the forum. 
Counterintuitively, inviting someone (and accepting the invitation) 
makes a difference even if both of you already subscribe to the forum, 
because of rule 3 above: it lets Briar know that you're OK with this 
contact knowing that you subscribe to the forum, and thus messages in 
the forum can be synced with that contact.

This is clearly bad UX. We're currently working on improving it, but it 
won't be an easy fix because of the complex tradeoffs between 
connectivity, privacy and scalability.

> Thanks for your time,
> 
> I greatly enjoy the app and hope to be a contributing member to the 
> project and the great thing you've built,

Thank you! Looking forward to having you on board.

Cheers,
Michael

> -jm
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

I'm a little hazy but will give you an answer; take it with a grain of
salt.

The biggest point below is that Briar using LoRa would be a great thing.



First, briar is primarily aimed at a different use case.  It's about
metadata protection so that people can communicate without state-level
actors (intelligence agencies, facebook, etc. :-( ) finding out who is
communicating.  You are talking about disaster resilience.  There are
similarities, but different goals drive different choices.

My recollection of Briar is that it has two primary mechanisms:

  bluetooth

  tor

with tor, the node runs a hidden service, and another node connects to
it.  The info is shared over local connection.

Running a tor hidden service had huge battery costs, last I checked.

I am unclear if there is briar over wifi.  That's tricky because it can
out people running briar, for later rounding up.


Briar has or is getting "mailboxes", a node you can run on stable
internet to accept messages for you, that you can then connect to, so
that 1) people can send you messages while you are offline if your mbox
is online and 2) you can not kill your batery.

With the no-internet no-cell situation, tor doesn't work because it runs
over IP.

The bluetooth part is interesting because if someone goes to town and
gets info and comes back the others can get it too.  This is basically a
form of Disruption Tolerant Networking, at the presentation layer more
or less.


The other thing you should be looking  at is longer-range
non-infrastructure radios.  People are using 915 LoRa (not LoraWAN!!) as
basically a higher-range BLE.   Projects using that are Meshtastic
(which is limited to a small group and doesn't have good confidentiality
properties) and Reticulum (which is less popular and quite different,
but very interesting).

*** There is no good reason why briar couldn't use LoRa, and it would be
great to have it be able to talk to a reticulum-style RNode
(microcontroller and LoRa chip, accessible to a phone over bluetooth).
This is probably not even that much work. ***

In general, ad hoc routing, low bandwidth, and mobility do not all go
togeher.

In the amateur radio world, there is AREDN, basically internet over 5
GHz p2p links.  You said 'auxiliary communicaitons' and I don't know if
you meant that loosely or you mean AUXCOMM in FEMA doctrine.

Good morning team,

I live in TN where we were most recently struck by horrific flooding after
Helene that has crippled around 20% of our cellular infrastructure.

I'm in the process of writing a white paper and doing some proof of
concepts to get the word out about Briar and encourage my local auxiliary
communications groups, and others to make use of the software.

I'd like to contribute pull requests as well but believe my access is
pending in gitlab.

I'd also like to ask some technical and feasibility questions if anyone has
time.

1) I've ran multiple packet captures on Briar and can't find broadcast
traffic or similar to see clients finding each other on a LAN. Is this
pulled off by some other means?
2) What back end infrastructure exist to facilitate coordination over the
internet/tor. Does briar run a coordination service?
3) Is there a requirement for a continuous connection chain to exist for
messages to be relayed. E.g. given user A, B, and C. If all are contacts
and C wants to talk to A, using B as an intermediary does B have to be in
range to both A and C for messages to be relayed? Or do messages from C,
cache on B's device until they come back into contact with A?

Thanks for your time,

I greatly enjoy the app and hope to be a contributing member to the project
and the great thing you've built,

-jm

Hello<br><br><div id="hw_signature">ارسال‌شده از تلفن من</div><div style="line-height:1.5"><br><br>-------- پیام اولیه --------<br>از: abdurrahman1--- via briar-devel &lt;bri...@li...&gt;<br>تاریخ: یکشنبه ۱۴ ژوئیهٔ ۲۰۲۴،‏ ۱۳:۵۵<br>به: Briar Devel &lt;bri...@li...&gt;<br>موضوع: [briar-devel] Hi<br><blockquote><div>
<div dir="auto">Hello</div>  </div>
</blockquote></div>

Hello

On Monday, 17 June 2024 07:55:17 -03 Michael Rogers wrote:
> Some apps in F-Droid also seem to show what's new
> in the latest version - I'm not sure if there's a dedicated field 
for
> that or if developers just update the description field.

This comes from fastlane and is the same what apps use with Google 
play. If we checked in the fastlane changelogs, it would appear in F-
Droid as well. As a side effect, they would get automatically used 
when publishing to Google Play, so no manual entering needed.

Kind Regards,
Torsten

On 17/06/2024 11:20, Nico Alt wrote:
> On 6/17/24 12:14, Michael Rogers wrote:
>> Adding them to F-Droid too is a good idea. I'll keep that in mind when 
>> we eventually move to using Fastlane for releases - then we can send 
>> the same release notes to F-Droid and Google Play. (The ones currently 
>> shown in Google Play are copied and pasted from the changelogs above.)
> 
> fwiw, I already see them in my F-Droid app, having added the Briar 
> F-Droid repo in addition to the default F-Droid one. Maybe the 
> (changelog) metadata comes from Briar's entry in the default F-Droid 
> repo? I have F-Droid 1.19.1 here, not yet grote's shiny new 1.20.0 version.

Good point, we do already have a changelog link in our own repo as well 
as the default repo. Some apps in F-Droid also seem to show what's new 
in the latest version - I'm not sure if there's a dedicated field for 
that or if developers just update the description field.

(Sorry for duplicating your earlier response, BTW - I didn't see it 
until I'd sent mine.)

Cheers,
Michael

On 6/17/24 12:14, Michael Rogers wrote:
> Adding them to F-Droid too is a good idea. I'll keep that in mind when 
> we eventually move to using Fastlane for releases - then we can send the 
> same release notes to F-Droid and Google Play. (The ones currently shown 
> in Google Play are copied and pasted from the changelogs above.)

fwiw, I already see them in my F-Droid app, having added the Briar 
F-Droid repo in addition to the default F-Droid one. Maybe the 
(changelog) metadata comes from Briar's entry in the default F-Droid 
repo? I have F-Droid 1.19.1 here, not yet grote's shiny new 1.20.0 version.

Hi,

You can find the changelogs for Briar and Briar Mailbox here:

https://code.briarproject.org/briar/briar/-/wikis/changelog

https://code.briarproject.org/briar/briar-mailbox/-/wikis/changelog

Adding them to F-Droid too is a good idea. I'll keep that in mind when 
we eventually move to using Fastlane for releases - then we can send the 
same release notes to F-Droid and Google Play. (The ones currently shown 
in Google Play are copied and pasted from the changelogs above.)

Cheers,
Michael

On 16/06/2024 23:36, Charlie Sierra 2 via briar-devel wrote:
> Hi,
> 
> Can you please tell me where to find the release notes of each new 
> version when it comes out?
> 
> Despite a pretty good search, I can't find them anywhere online.
> 
> I would like to be able to know what has changed before I do an update, 
> and I'm sure I'm not the only user who feels that way.
> 
> Also, it's difficult enough to promote Briar to new users as it is, and 
> it's irritating and doesn't help with trust if users can't find this 
> information.
> 
> My suggestion would be to just publish release notes, or at least a 
> direct link to them, in F-Droid and in any other place where Briar can 
> be downloaded, right next to the download itself.
> 
> Cheers
> 
> 
> Sent from ProtonMail mobile
> 
> 
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

Hi,

you can find Briar's changelog linked from, e.g., its F-Droid page, also 
visible in the F-Droid app:

https://f-droid.org/en/packages/org.briarproject.briar.android/

https://code.briarproject.org/briar/briar/-/wikis/changelog

Cheers,

~Nico


On 6/17/24 00:36, Charlie Sierra 2 via briar-devel wrote:
> Hi,
> 
> Can you please tell me where to find the release notes of each new version when it comes out?
> 
> Despite a pretty good search, I can't find them anywhere online.
> 
> I would like to be able to know what has changed before I do an update, and I'm sure I'm not the only user who feels that way.
> 
> Also, it's difficult enough to promote Briar to new users as it is, and it's irritating and doesn't help with trust if users can't find this information.
> 
> My suggestion would be to just publish release notes, or at least a direct link to them, in F-Droid and in any other place where Briar can be downloaded, right next to the download itself.
> 
> Cheers
> 
> Sent from ProtonMail mobile
> 
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

Hi,

yes, the project is still alive and well. It's probably best to check 
out GitLab to see this.

https://code.briarproject.org/groups/briar/-/activity

Cheers,

~Nico

On 6/17/24 00:40, Charlie Sierra 2 via briar-devel wrote:
> As far as I can see, the most recent entry in the "news" page on the Briar web page is almost a year old, and things seem a bit quiet lately around Briar.
> 
> Maybe I have missed some things, not sure, but it does make me wonder.
> 
> Is the Briar project still well?
> 
> I would hate to see it disappear.
> 
> Sent from ProtonMail mobile
> 
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

Hi Charlie,

I think they are still quite active in terms of updates to wordcounts for
translations which means updates to the app are still happening.

It may be a case of simply not having enough time to update the blog,
maybe?

It remains to be seen but from what I know, the project is still quite
alive. We wait to hear from the development team.


Best,

On Mon, Jun 17, 2024 at 12:42 AM Charlie Sierra 2 via briar-devel <
bri...@li...> wrote:

> As far as I can see, the most recent entry in the "news" page on the Briar
> web page is almost a year old, and things seem a bit quiet lately around
> Briar.
>
> Maybe I have missed some things, not sure, but it does make me wonder.
>
> Is the Briar project still well?
>
> I would hate to see it disappear.
>
>
>
>
> Sent from ProtonMail mobile
>
>
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel
>


-- 
Chido Musodza (she/her)
Program Associate, Community Engagement
www.localizationlab.org
PGP Key
<https://keys.openpgp.org/vks/v1/by-fingerprint/FB9C75E3A2BAC609A6261E2007AC1E56B3CE4AD8>



Localization Lab is a non-profit organization that is working to address
ethnocentric bias in tech & improving accessibility through collaborative
localization, user feedback, and co-design. At Localization Lab, we believe
that language shouldn't be a barrier when it comes to security and access
to the Internet. Since 2012, we have helped expand the reach of Internet
freedom tools by unlocking access to communities all over the world.

As far as I can see, the most recent entry in the "news" page on the Briar web page is almost a year old, and things seem a bit quiet lately around Briar.

Maybe I have missed some things, not sure, but it does make me wonder.

Is the Briar project still well?

I would hate to see it disappear.

Sent from ProtonMail mobile

Hi,

Can you please tell me where to find the release notes of each new version when it comes out?

Despite a pretty good search, I can't find them anywhere online.

I would like to be able to know what has changed before I do an update, and I'm sure I'm not the only user who feels that way.

Also, it's difficult enough to promote Briar to new users as it is, and it's irritating and doesn't help with trust if users can't find this information.

My suggestion would be to just publish release notes, or at least a direct link to them, in F-Droid and in any other place where Briar can be downloaded, right next to the download itself.

Cheers

Sent from ProtonMail mobile

Hi Tux,

I'm afraid we don't have a published roadmap. When I said this feature 
was on our roadmap I just meant it was one of many things we'd been 
intending to work on. Apparently I'm slipping into management-speak in 
my old age. ;)

We're currently applying for funding to do some user research to guide 
the future development of the project. It's possible that a proper 
roadmap may be an output of that research.

The board doesn't have regular meetings but I guess we could publish the 
occasional decisions it makes.

Cheers,
Michael

On 18/04/2024 14:57, briar.sourceforge.soc--- via briar-devel wrote:
> Thank you Michael! Is the roadmap for this project published?
> Also, are the Minutes of board meetings made available to the public?
> 
> Thanks,
> Tux
> 
> On 2024-04-18 06:25, Michael Rogers wrote:
>> Yup, that's right. The feature for verifying a contact who was added
>> via the internet, if you later meet them in person, has been on the
>> roadmap for a long time and we're hoping to be able to implement it in
>> the next few months.
>>
>> To answer the other question, the mailbox app should be able to run on
>> an Android tablet, as long as it has reliable internet access.
>>
>> Cheers,
>> Michael
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

Thank you Michael! Is the roadmap for this project published?
Also, are the Minutes of board meetings made available to the public?

Thanks,
Tux

On 2024-04-18 06:25, Michael Rogers wrote:
> Yup, that's right. The feature for verifying a contact who was added
> via the internet, if you later meet them in person, has been on the
> roadmap for a long time and we're hoping to be able to implement it in
> the next few months.
> 
> To answer the other question, the mailbox app should be able to run on
> an Android tablet, as long as it has reliable internet access.
> 
> Cheers,
> Michael

Yup, that's right. The feature for verifying a contact who was added via 
the internet, if you later meet them in person, has been on the roadmap 
for a long time and we're hoping to be able to implement it in the next 
few months.

To answer the other question, the mailbox app should be able to run on 
an Android tablet, as long as it has reliable internet access.

Cheers,
Michael

On 17/04/2024 19:25, potato via briar-devel wrote:
> I think that I can answer this question - at least from what I've 
> experienced, I think that one hashtag by someone's name means that 
> they're not a contact, two means they're a contact established via the 
> internet, and three hashtags means that they're a contact established in 
> person, which for purposes of verifiability, is the most secure.
> 
> On 4/17/24 9:48 AM, briar.sourceforge.soc--- via briar-devel wrote:
>> Thank you for the response!
>>
>> I have an Android tablet I use for home automation 
>> programming/scheduling, so it is my wish to run the mailbox on that 
>> device where it benefits from basically an off-grid house (starlink 
>> and solar/gas generator). I have not yet played with the desktop (or 
>> containers), but almost my entire use case is for mobile at the moment.
>>
>> I can get a contact "connected" at a distance and chat, but never 
>> fully verified (so far). Under their name, it shows 2 orange # 
>> symbols, one grey symbol, and "Unverified contact"  -  unlike the 
>> other contacts I have established that show 3 green # symbols along 
>> with "Verified contact".
>>
>>
>> On 2024-04-17 11:18, Eric Lynema wrote:
>>> Hi, I can answer one of your questions. For mailbox, if you run docker
>>> containers you can run multiple instances on a computer. I've been
>>> doing this for a while now. I know for desktop you can move the config
>>> folder to a new machine or install, not sure about mobile. and lastly,
>>> I would love to know if you can verify at a distance.
>>>
>>> Sent from my phone. Please excuse the fact that I can't type on these
>>> things to save my life.
>>>
>>> On Mon, Apr 15, 2024, 4:57 PM briar.sourceforge.soc--- via briar-devel
>>> <bri...@li...> wrote:
>>>
>>>> Good Day Everyone,
>>>>
>>>> When I add a contact at a distance, sharing contact URLs, the
>>>> contacts
>>>> always appear as "unverified". What is the process to make them
>>>> verified?
>>>>
>>>> Is there a plan for backup/restore of logins (for example, in the
>>>> case
>>>> of losing/breaking a phone)?
>>>>
>>>> Is there a roadmap for the project? Interested in features like:
>>>> * Adding photos to forum posts, blogs, and private groups.
>>>> * Multiple (trusted) users for mailbox helper app (and perhaps
>>>> multiple
>>>> instances of a helper app where it might live on either side of a
>>>> segmented Internet).
>>>> * Exporting a forum and/or blog would be very useful in the case
>>>> of
>>>> Crisis Management. CERT members are required to take notes and be
>>>> able
>>>> to hand them off to officials. This tool is fantastic for CERT teams
>>>> to
>>>> stay in communication during comms outages but inability export
>>>> notes/logs/etc is a ugly Debbie Downer for this use case.
>>>>
>>>> Thanks!
>>>> Tux
>>>>
>>>> _______________________________________________
>>>> briar-devel mailing list
>>>> bri...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/briar-devel
>>
>>
>> _______________________________________________
>> briar-devel mailing list
>> bri...@li...
>> https://lists.sourceforge.net/lists/listinfo/briar-devel
> 
> 
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

Thank you for this reasonable answer!

On 2024-04-17 14:25, potato via briar-devel wrote:
> I think that I can answer this question - at least from what I've
> experienced, I think that one hashtag by someone's name means that
> they're not a contact, two means they're a contact established via the
> internet, and three hashtags means that they're a contact established
> in person, which for purposes of verifiability, is the most secure.

I think that I can answer this question - at least from what I've 
experienced, I think that one hashtag by someone's name means that 
they're not a contact, two means they're a contact established via the 
internet, and three hashtags means that they're a contact established in 
person, which for purposes of verifiability, is the most secure.

On 4/17/24 9:48 AM, briar.sourceforge.soc--- via briar-devel wrote:
> Thank you for the response!
>
> I have an Android tablet I use for home automation 
> programming/scheduling, so it is my wish to run the mailbox on that 
> device where it benefits from basically an off-grid house (starlink 
> and solar/gas generator). I have not yet played with the desktop (or 
> containers), but almost my entire use case is for mobile at the moment.
>
> I can get a contact "connected" at a distance and chat, but never 
> fully verified (so far). Under their name, it shows 2 orange # 
> symbols, one grey symbol, and "Unverified contact"  -  unlike the 
> other contacts I have established that show 3 green # symbols along 
> with "Verified contact".
>
>
> On 2024-04-17 11:18, Eric Lynema wrote:
>> Hi, I can answer one of your questions. For mailbox, if you run docker
>> containers you can run multiple instances on a computer. I've been
>> doing this for a while now. I know for desktop you can move the config
>> folder to a new machine or install, not sure about mobile. and lastly,
>> I would love to know if you can verify at a distance.
>>
>> Sent from my phone. Please excuse the fact that I can't type on these
>> things to save my life.
>>
>> On Mon, Apr 15, 2024, 4:57 PM briar.sourceforge.soc--- via briar-devel
>> <bri...@li...> wrote:
>>
>>> Good Day Everyone,
>>>
>>> When I add a contact at a distance, sharing contact URLs, the
>>> contacts
>>> always appear as "unverified". What is the process to make them
>>> verified?
>>>
>>> Is there a plan for backup/restore of logins (for example, in the
>>> case
>>> of losing/breaking a phone)?
>>>
>>> Is there a roadmap for the project? Interested in features like:
>>> * Adding photos to forum posts, blogs, and private groups.
>>> * Multiple (trusted) users for mailbox helper app (and perhaps
>>> multiple
>>> instances of a helper app where it might live on either side of a
>>> segmented Internet).
>>> * Exporting a forum and/or blog would be very useful in the case
>>> of
>>> Crisis Management. CERT members are required to take notes and be
>>> able
>>> to hand them off to officials. This tool is fantastic for CERT teams
>>> to
>>> stay in communication during comms outages but inability export
>>> notes/logs/etc is a ugly Debbie Downer for this use case.
>>>
>>> Thanks!
>>> Tux
>>>
>>> _______________________________________________
>>> briar-devel mailing list
>>> bri...@li...
>>> https://lists.sourceforge.net/lists/listinfo/briar-devel
>
>
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel

>From a quick search engine query it looks like containers like docker or
podman can be run on a device running android but doesn't sound like it for
the normal user.
Good Luck don't try anything that could brick something you aren't willing
to replace.

On Wed, Apr 17, 2024, 11:52 briar.sourceforge.soc--- via briar-devel <
bri...@li...> wrote:

> Thank you for the response!
>
> I have an Android tablet I use for home automation
> programming/scheduling, so it is my wish to run the mailbox on that
> device where it benefits from basically an off-grid house (starlink and
> solar/gas generator). I have not yet played with the desktop (or
> containers), but almost my entire use case is for mobile at the moment.
>
> I can get a contact "connected" at a distance and chat, but never fully
> verified (so far). Under their name, it shows 2 orange # symbols, one
> grey symbol, and "Unverified contact"  -  unlike the other contacts I
> have established that show 3 green # symbols along with "Verified
> contact".
>
>
> On 2024-04-17 11:18, Eric Lynema wrote:
> > Hi, I can answer one of your questions. For mailbox, if you run docker
> > containers you can run multiple instances on a computer. I've been
> > doing this for a while now. I know for desktop you can move the config
> > folder to a new machine or install, not sure about mobile. and lastly,
> > I would love to know if you can verify at a distance.
> >
> > Sent from my phone. Please excuse the fact that I can't type on these
> > things to save my life.
> >
> > On Mon, Apr 15, 2024, 4:57 PM briar.sourceforge.soc--- via briar-devel
> > <bri...@li...> wrote:
> >
> >> Good Day Everyone,
> >>
> >> When I add a contact at a distance, sharing contact URLs, the
> >> contacts
> >> always appear as "unverified". What is the process to make them
> >> verified?
> >>
> >> Is there a plan for backup/restore of logins (for example, in the
> >> case
> >> of losing/breaking a phone)?
> >>
> >> Is there a roadmap for the project? Interested in features like:
> >> * Adding photos to forum posts, blogs, and private groups.
> >> * Multiple (trusted) users for mailbox helper app (and perhaps
> >> multiple
> >> instances of a helper app where it might live on either side of a
> >> segmented Internet).
> >> * Exporting a forum and/or blog would be very useful in the case
> >> of
> >> Crisis Management. CERT members are required to take notes and be
> >> able
> >> to hand them off to officials. This tool is fantastic for CERT teams
> >> to
> >> stay in communication during comms outages but inability export
> >> notes/logs/etc is a ugly Debbie Downer for this use case.
> >>
> >> Thanks!
> >> Tux
> >>
> >> _______________________________________________
> >> briar-devel mailing list
> >> bri...@li...
> >> https://lists.sourceforge.net/lists/listinfo/briar-devel
>
>
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel
>

Thank you for the response!

I have an Android tablet I use for home automation 
programming/scheduling, so it is my wish to run the mailbox on that 
device where it benefits from basically an off-grid house (starlink and 
solar/gas generator). I have not yet played with the desktop (or 
containers), but almost my entire use case is for mobile at the moment.

I can get a contact "connected" at a distance and chat, but never fully 
verified (so far). Under their name, it shows 2 orange # symbols, one 
grey symbol, and "Unverified contact"  -  unlike the other contacts I 
have established that show 3 green # symbols along with "Verified 
contact".


On 2024-04-17 11:18, Eric Lynema wrote:
> Hi, I can answer one of your questions. For mailbox, if you run docker
> containers you can run multiple instances on a computer. I've been
> doing this for a while now. I know for desktop you can move the config
> folder to a new machine or install, not sure about mobile. and lastly,
> I would love to know if you can verify at a distance.
> 
> Sent from my phone. Please excuse the fact that I can't type on these
> things to save my life.
> 
> On Mon, Apr 15, 2024, 4:57 PM briar.sourceforge.soc--- via briar-devel
> <bri...@li...> wrote:
> 
>> Good Day Everyone,
>> 
>> When I add a contact at a distance, sharing contact URLs, the
>> contacts
>> always appear as "unverified". What is the process to make them
>> verified?
>> 
>> Is there a plan for backup/restore of logins (for example, in the
>> case
>> of losing/breaking a phone)?
>> 
>> Is there a roadmap for the project? Interested in features like:
>> * Adding photos to forum posts, blogs, and private groups.
>> * Multiple (trusted) users for mailbox helper app (and perhaps
>> multiple
>> instances of a helper app where it might live on either side of a
>> segmented Internet).
>> * Exporting a forum and/or blog would be very useful in the case
>> of
>> Crisis Management. CERT members are required to take notes and be
>> able
>> to hand them off to officials. This tool is fantastic for CERT teams
>> to
>> stay in communication during comms outages but inability export
>> notes/logs/etc is a ugly Debbie Downer for this use case.
>> 
>> Thanks!
>> Tux
>> 
>> _______________________________________________
>> briar-devel mailing list
>> bri...@li...
>> https://lists.sourceforge.net/lists/listinfo/briar-devel

Hi, I can answer one of your questions. For mailbox, if you run docker
containers you can run multiple instances on a computer. I've been doing
this for a while now. I know for desktop you can move the config folder to
a new machine or install, not sure about mobile. and lastly, I would love
to know if you can verify at a distance.

Sent from my phone. Please excuse the fact that I can't type on these
things to save my life.

On Mon, Apr 15, 2024, 4:57 PM briar.sourceforge.soc--- via briar-devel <
bri...@li...> wrote:

> Good Day Everyone,
>
> When I add a contact at a distance, sharing contact URLs, the contacts
> always appear as "unverified". What is the process to make them
> verified?
>
> Is there a plan for backup/restore of logins (for example, in the case
> of losing/breaking a phone)?
>
> Is there a roadmap for the project? Interested in features like:
>   * Adding photos to forum posts, blogs, and private groups.
>   * Multiple (trusted) users for mailbox helper app (and perhaps multiple
> instances of a helper app where it might live on either side of a
> segmented Internet).
>   * Exporting a forum and/or blog would be very useful in the case of
> Crisis Management. CERT members are required to take notes and be able
> to hand them off to officials. This tool is fantastic for CERT teams to
> stay in communication during comms outages but inability export
> notes/logs/etc is a ugly Debbie Downer for this use case.
>
> Thanks!
> Tux
>
>
> _______________________________________________
> briar-devel mailing list
> bri...@li...
> https://lists.sourceforge.net/lists/listinfo/briar-devel
>