Re: [tor-relays] Bridge lifecycle expectations

2022-03-30 Thread meskio
Quoting flux via tor-relays (2022-03-23 22:52:29) > > On 3/23/22 14:11, meskio wrote: > > You can monitor how many > > connections you get from each country (by looking at stats/bridgestats) and > > if > > you were getting many connections from a certain country and they drop to 0 > > that > >

Re: [tor-relays] Bridge lifecycle expectations

2022-03-24 Thread flux via tor-relays
On 3/23/22 14:11, meskio wrote: You can monitor how many connections you get from each country (by looking at stats/bridgestats) and if you were getting many connections from a certain country and they drop to 0 that means your bridge is burned in that country. Could you elaborate a bit more

Re: [tor-relays] Bridge lifecycle expectations

2022-03-23 Thread Just a Pleb
Hi meskio, Thanks for the detailed response. My bridge has been assigned to telegram so that explains why it's not active yet. Watching per country stats makes sense for determining where the bridge has been blocked. Also good to know the bridge state should be fully disposed when recycling

Re: [tor-relays] Bridge lifecycle expectations

2022-03-23 Thread meskio
Quoting Just a Pleb (2022-03-23 02:43:54) > 1) How long is typical (or what factors are involved ) before the bridge > address is given out to users. It should take less than 3 hours to start being taken into account by rdsys/bridgedb. But unless you configure a specific distributor you will be as

[tor-relays] Bridge lifecycle expectations

2022-03-23 Thread Just a Pleb
Hi All, I have three lifecycle questions: 1) How long is typical (or what factors are involved ) before the bridge address is given out to users. 2) How do I know when the bridge is burned (identified and blocked) 3) When it is burned and I build a new one on an other address should I copy th