Hi,
Yaron Goland:
naming experiment extension
+1 for awesome usability test!!
Wordlife,
Spencer
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Ivan Markin:
> Hi,
>
> I've also recently improved Atlas but it changes major part of the user
> experience. So this is a kind of Request For Comments.
>
> Most of the changes are my vision of how-it-should-all-look-like. The
> most notable changes are:
> * There is no super-wide list of relays t
Yaron Goland:
> I'm also a noob, so just to be clear, is the goal here to adopt namecoin as a
> naming mechanism for hidden services or is the goal to enable a generic
> extension mechanism where multiple different naming solutions can be
> experimented with and namecoin wants to build the code
Arthur D. Edelstein:
> Hi Paulo,
>
> This sounds highly inadvisable to me. Interposing Privoxy between Tor
> Browser and Tor will most likely drastically reduce the anonymity
> provided by Tor Browser, for multiple reasons:
>
> 1. Privoxy filters and modifies the web page in ways that are likely
I'm also a noob, so just to be clear, is the goal here to adopt namecoin as a
naming mechanism for hidden services or is the goal to enable a generic
extension mechanism where multiple different naming solutions can be
experimented with and namecoin wants to build the code to leverage that
mech
Nick Mathewson:
> Hi, all!
>
> I've seen a couple of emails from people looking into new ways to do
> naming for onion services. That's great! Before anybody gets too
> far, I'd like to send this quick note to let you know that integrating
> stuff like this into Tor is actually easier than you t
And 10 years down when 20 bits is easy, you're going
want shrinking it again, or along any interim update cycle.
This is going to upset downstream parsers such as
web indexers that expect matching fixed length / pattern.
or that have to write zero [de]fillers.
ex: [a-z2-7]{16}\.onion, we now see s
On Tue, Aug 2, 2016 at 9:45 AM, teor wrote:
[...]
>
> Has someone put together an example resolver that just does simple extension
> substitution?
> It would amuse me to be able to visit 3g2upl4pq6kufc4m.chive, or
> 3g2upl4pq6kufc4m.allium.
>
I think I did one of these long ago when I was test
George Kadianakis writes:
> [ text/plain ]
> Jeremy Rand writes:
>
>> [ text/plain ]
>> Hello Tor devs,
>>
>> Namecoin is interested in collaboration with Tor in relation to
>> human-readable .onion names; I'm reaching out to see how open the Tor
>> community would be to this, and to get feedbac
> On 2 Aug 2016, at 23:37, Nick Mathewson wrote:
>
> Hi, all!
>
> I've seen a couple of emails from people looking into new ways to do
> naming for onion services. That's great! Before anybody gets too
> far, I'd like to send this quick note to let you know that integrating
> stuff like this
Hi, all!
I've seen a couple of emails from people looking into new ways to do
naming for onion services. That's great! Before anybody gets too
far, I'd like to send this quick note to let you know that integrating
stuff like this into Tor is actually easier than you think.
Here's how you do it,
Hi all,
At the Montreal hidden service hackfest, we discussed another scheme shortening
prop224 .onion addresses.
The only drawback is that it's exponentially difficult, so it can only chop off
a few characters.
I'm describing it here because it has other useful properties, and can be used
as:
12 matches
Mail list logo
