📅 Original date posted:2013-09-05
📝 Original message:>
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130905/94be6cf4/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:06:35
in reply to nevent1q…anu0
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:06:35Event JSON
{
"id": "44f85cf46fd6c9b1c922997c3782f65fbc364af44f98deb304ce8f3062bc76e8",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686150395,
"kind": 1,
"tags": [
[
"e",
"8769945ee824ea97f8febcbe3c50515e6c9d19a4db58d7907ec1e0e3738f19ef",
"",
"root"
],
[
"e",
"44a3b83492664d699a8d221970c5cbdfa0cb94d238ccdb1fb862b6b8c23f7f67",
"",
"reply"
],
[
"p",
"c534bb535ca1eba460ab96ad869cfa2160259b441c95515f281c187f0130f4f3"
]
],
"content": "📅 Original date posted:2013-09-05\n📝 Original message:\u003e\n\u003e Since this process would necessarily be somewhat manual and would of\n\u003e course be \"undone\" anytime the user changed his/her profile image, it is\n\u003e probably not a solution for everyone.\n\n\nI guess these days most Facebook/G+/Twitter users are logged in from their\nsmartphone , so you'd implement it as a mobile app that gets API access via\nthe standard mobile frameworks. The UI flows for this are highly optimised\nand very slick. Once you have API access to read/write the users profile\npicture, your app can just wake up from time to time and check if the users\nprofile picture has changed. If it did, download the highest resolution\navailable, rewatermark and reupload.\n\nThe main sticking point I can see is that the user might end up losing\ncomments or likes on their primary photo, which would upset some people,\nand they might end up with duplicates if the old one was not erased. The\nFacebook API docs are notoriously poor - it's unclear to me whether an app\ncan edit a photo after it was uploaded, or whether it can only create new\nones (deleting photos requires whitelisting by Facebook).\n\nTo read the users watermarked address requires no API access or account,\nthough.\n\nProbably you wouldn't want to watermark an actual Bitcoin address or key.\nThe capacity of social network photos to carry stegod data is very low due\nto the incredibly high compression they go through. More likely you'd\nencode a very short URL which contains a payment request and then users\nwould rotate their key from time to time at the hosting site.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130905/94be6cf4/attachment.html\u003e",
"sig": "ea83c9068483baca697ed48e90d47c3be0165138b4a7b523c0036fc52ca9f9930f7315006f93efb5c5a116038e240c7c5ebd329d3ca53f1081ed5d7eb109680a"
}