Hi,
I'm happy to finally announce version 1 of the ContactInfo Information Sharing
Specification:
https://github.com/nusenu/ContactInfo-Information-Sharing-Specification
This is an effort that started in 2017 as you can see on github.
Tor's ContactInfo field was primarily intended to contain an
On 7/21/20 7:16 PM, nusenu wrote:
> verifyurl
What is the advantage over the torrc config value "MyFamily" ?
--
Toralf
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists
Toralf Förster:
> On 7/21/20 7:16 PM, nusenu wrote:
>> verifyurl
>
> What is the advantage over the torrc config value "MyFamily" ?
MyFamily is somewhat orthogonal to the idea behind the verifyurl field.
MyFamily has an impact on path selection, ContactInfo/verifyurl has not.
verifyurl is u
Great job, except one thing. Can’t providing *any* contact info be
obligatory? What’s the point of making specifically the email address
required? What are benefits of having it *over other contact info*?
- Automatic verification of some kind? No.
That would require client-side system coup
mpan a écrit :
> - Increasing contact? No.
> I was offering an email address for some time and the only
> experience was no single message from a human actually contacting
> me about Tor. Everything was only spam. Suggesting address rotation
> or antispam filters is merely an atte
Thank you for your feedback.
mpan:
> Can’t providing *any* contact info be
> obligatory? What’s the point of making specifically the email address
> required? What are benefits of having it *over other contact info*?
I'd argue that email is the most accessible?
The Tor Project used to use email
On Tue, 21 Jul 2020 20:17:24 +0200
nusenu wrote:
> > What is the advantage over the torrc config value "MyFamily" ?
>
> MyFamily is somewhat orthogonal to the idea behind the verifyurl field.
Still not getting what advantage do you propose to ones who choose to also
maintain the latter.
It re
Roman Mamedov:
> On Tue, 21 Jul 2020 20:17:24 +0200
> nusenu wrote:
>
>>> What is the advantage over the torrc config value "MyFamily" ?
>>
>> MyFamily is somewhat orthogonal to the idea behind the verifyurl field.
>
> Still not getting what advantage do you propose to ones who choose to also
>
* nusenu:
> https://github.com/nusenu/ContactInfo-Information-Sharing-Specification
> This is an effort that started in 2017 as you can see on github.
In section "Defined fields" you write:
Non-ASCII characters are not supported.
I'm not sure if this applies only to keys or also to values? Wi
> I'm also fine with making it optional in the upcoming version 2
> to lower the barrier for adoption.
My goal is not to make contact info optional. I do understand value of
such information. The problem is choosing one specific means of
communication as mandatory, instead of letting the operator
On 21/07/20 18:16, nusenu wrote:
Hi,
I'm happy to finally announce version 1 of the ContactInfo Information Sharing
Specification:
https://github.com/nusenu/ContactInfo-Information-Sharing-Specification
This is an effort that started in 2017 as you can see on github.
...
regards,
nusenu
On 21.07.2020 19:16, nusenu wrote:
keybase
Much of this list is verified by keybase. ;-)
https://keybase.io/boldsuck
Keybase was purchased from Zoom. Some may want to use https://keys.pub/
instead.
bitcoin
zcash
Zcash? If privacy coin then Monero.
You can create an openalias
On Fri, Jul 24, 2020 at 9:08 PM Ralph Seichter wrote:
>
> * nusenu:
>
> > https://github.com/nusenu/ContactInfo-Information-Sharing-Specification
> > This is an effort that started in 2017 as you can see on github.
>
> In section "Defined fields" you write:
>
> Non-ASCII characters are not suppo
>> In section "Defined fields" you write:
>>
>> Non-ASCII characters are not supported.
>>
>> I'm not sure if this applies only to keys or also to values? With the
>> availability of IDN (https://unicode.org/faq/idn.html) in email
>> addresses, supporting only US-ASCII values is too limited.
>
>
On Mon, Jul 27, 2020 at 2:05 PM nusenu wrote:
>
> >> In section "Defined fields" you write:
> >>
> >> Non-ASCII characters are not supported.
> >>
> >> I'm not sure if this applies only to keys or also to values? With the
> >> availability of IDN (https://unicode.org/faq/idn.html) in email
> >>
* Nick Mathewson:
> I'd suggest that we should allow UTF-8 for values, at least.
Indeed, that should work.
-Ralph
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
16 matches
Mail list logo
