From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RaFnu-0003oS-21 for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 00:01:06 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=timon.elviejo@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RaFnt-0008D4-3F for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 00:01:06 +0000 Received: by wgbds1 with SMTP id ds1so11512158wgb.10 for ; Mon, 12 Dec 2011 16:00:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.0.100 with SMTP id 4mr23458534wid.48.1323734458971; Mon, 12 Dec 2011 16:00:58 -0800 (PST) Received: by 10.223.81.79 with HTTP; Mon, 12 Dec 2011 16:00:58 -0800 (PST) In-Reply-To: References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> <201112121841.39864.luke@dashjr.org> Date: Tue, 13 Dec 2011 01:00:58 +0100 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= To: bitcoin-development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (timon.elviejo[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 2.5 FREEMAIL_REPLY From and body contain different freemails -1.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RaFnt-0008D4-3F Subject: [Bitcoin-development] Fwd: [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2011 00:01:06 -0000 Is the point is to have different hosts like in jtimon@gmail.com, jtimon@timon.es, etc. so if jtimon is already taken I can take another host? What about reserving directly the string "jtimon@nottaken.org" or "jtimon::public::receiving::bitcoin" in namecoin? I'm confused about the problem we're trying to solve. 2011/12/13, Luke-Jr : > On Monday, December 12, 2011 6:37:56 PM Jorge Tim=F3n wrote: >> Would it be too strange to use namecoin? > > This has the same problem as FirstBits, except .bit domains are dirt chea= p, > whereas vanitygen at least slows down grabbing all the common words... >