From: Mike Hearn <mike@plan99•net>
To: Wendell <w@grabhive•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Social network integration (brainstorm)
Date: Thu, 5 Sep 2013 10:33:24 +0200 [thread overview]
Message-ID: <CANEZrP2ph9SM6kUdTXooZ2nqKD4LweWsgVEdssiftNdBmcP+_w@mail.gmail.com> (raw)
In-Reply-To: <2DE404E4-446E-41F4-8ECF-B312EE42D067@grabhive.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
>
> 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.
I guess these days most Facebook/G+/Twitter users are logged in from their
smartphone , so you'd implement it as a mobile app that gets API access via
the standard mobile frameworks. The UI flows for this are highly optimised
and very slick. Once you have API access to read/write the users profile
picture, your app can just wake up from time to time and check if the users
profile picture has changed. If it did, download the highest resolution
available, rewatermark and reupload.
The main sticking point I can see is that the user might end up losing
comments or likes on their primary photo, which would upset some people,
and they might end up with duplicates if the old one was not erased. The
Facebook API docs are notoriously poor - it's unclear to me whether an app
can edit a photo after it was uploaded, or whether it can only create new
ones (deleting photos requires whitelisting by Facebook).
To read the users watermarked address requires no API access or account,
though.
Probably you wouldn't want to watermark an actual Bitcoin address or key.
The capacity of social network photos to carry stegod data is very low due
to the incredibly high compression they go through. More likely you'd
encode a very short URL which contains a payment request and then users
would rotate their key from time to time at the hosting site.
[-- Attachment #2: Type: text/html, Size: 1920 bytes --]
next prev parent reply other threads:[~2013-09-05 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 8:23 Wendell
2013-09-05 8:33 ` Mike Hearn [this message]
2013-09-05 11:02 ` Mats Henricson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP2ph9SM6kUdTXooZ2nqKD4LweWsgVEdssiftNdBmcP+_w@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=w@grabhive$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox