From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VHUqV-0000rY-MD for bitcoin-development@lists.sourceforge.net; Thu, 05 Sep 2013 08:23:19 +0000 X-ACL-Warn: Received: from mail-ee0-f52.google.com ([74.125.83.52]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VHUqR-0004u6-G7 for bitcoin-development@lists.sourceforge.net; Thu, 05 Sep 2013 08:23:19 +0000 Received: by mail-ee0-f52.google.com with SMTP id c41so722077eek.11 for ; Thu, 05 Sep 2013 01:23:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version; bh=m2OP8mr+E5fsd0jywhUm9Cm/C5beGJYmBS6rbmycH5I=; b=lG9rhMHCXTwuvFOXcMwifu5Q24a/dwO+JGvc+5sniDq+o974VWuJgC0t7mXgngDUg4 J7nGg9yxZNXwIi1Sll8err6VwQrU+iaHCNT5/mvjMHo3m3azkf7SKd5NI84tr57PxjKU MySC4lDTh3p6Ta6d/nu+eOY7yRkkwhzXmQCXsaF44LUS52UNWXSFjaxjd7qVpfLeRDeY pQAFeilgYw9N76Axs4/kGbOInmDwqMPFt9X8gjJx+ICkWcuQO6BAqUbGgRJWG9ponJB4 d5VMIcnVw9Xs6cw30gsmCqfXc+dtnkoMtMGOtLg3XATuYGOUz2Xj4d4eCnTELYkyKWlH cuNQ== X-Gm-Message-State: ALoCoQkjRUaGuEIlzZ6LnPTEdjVXuidBXnsU/a7j5UU+fWP8RrGLFCTwKuyEBFCyhKgayl2LaPX7 X-Received: by 10.15.54.72 with SMTP id s48mr2011159eew.58.1378369388586; Thu, 05 Sep 2013 01:23:08 -0700 (PDT) Received: from [127.0.0.1] (spftor4e1.privacyfoundation.ch. [77.109.138.42]) by mx.google.com with ESMTPSA id t6sm46573837eel.12.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 05 Sep 2013 01:23:07 -0700 (PDT) Sender: Wendell From: Wendell Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Sep 2013 10:23:01 +0200 Message-Id: <2DE404E4-446E-41F4-8ECF-B312EE42D067@grabhive.com> To: Bitcoin Dev Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1VHUqR-0004u6-G7 Subject: [Bitcoin-development] Social network integration (brainstorm) 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: Thu, 05 Sep 2013 08:23:19 -0000 Mike Hearn had a rather cool idea about watermarking images with Bitcoin = addresses in order to facilitate auto-magically linking social = networking profiles: apparently even without API access, reasonably = large user images are available publicly via the major services = (Facebook, Twitter). Since this process would necessarily be somewhat manual and would of = course be "undone" anytime the user changed his/her profile image, it is = probably not a solution for everyone. But it seems that this could be a = helpful way to at least _begin_ organizing Bitcoin around people and = organizations in a way that is broadly familiar. I haven't been able to get this to work myself, but Blockchain.info = seems to offer sending 'coin via Facebook: https://blockchain.info/wallet/send-via There is also the very cute Bitcoins With Friends: https://bitcoinswithfriends.com/ Most of the other apps that I have seen at one point or another have = vanished. I recall reading that Facebook was not particularly friendly = to them, hence the present interest in more subversive (?) ways of = making those connections. Again, I am not 100% sure that this is the correct place for it, but I'm = opening this thread to other such ideas in case anyone else wants to = discuss it. Our motivation is making Bitcoin easier to use, and we = suspect that even imperfect social network support will move us closer = to that goal. -wendell grabhive.com | twitter.com/grabhive | gpg: 6C0C9411 > Re-orienting Bitcoin around people and companies is something we = wanted to do for a long time. How do you get an address linked to a = personal profile? Someone was asking me about this last month and I = suggested watermarking addresses into social network profile pictures. = The advantage of that approach is every social network supports profile = pictures and big ones like Facebook and Twitter allow querying of = somebodies picture without needing any API or user authentication, eg: >=20 > https://graph.facebook.com/i.am.the.real.mike/picture?type=3Dlarge >=20 > So obviously with such a thing you can send to any Facebook user who = has configured their profile correctly. There's a library that = implements watermarking that can survive social network recompression, = but it is (doh) written in Java ;)