petermolnarI have a syndication flow that uses my RSS feed to syndicate. The problem with this setup is that after the syndication I need to go and find the syndicated copy URL to add it to the entry. I was wondering to make the following instead: add another flow that sends a repost webmention from the silo; keep a list of these semi-POSSE sources; and treat the incoming webmention in a special way so inst
aaronpkmy micro.blog syndication is similar since it's pulling from my jsonfeed, and micro.blog sends a webmention from its copy once it makes it, and my site recognizes that as a syndicated copy and adds the syndication link
[schmarty]Like you could make a relme link on your site to your Twitter, add a "proof" attribute that points to a post on your Twitter account, and a "signing key" attribute with the equivalent of a public key for which you have the private key
[schmarty]Your tweet would then say something like "Verifying that I am my domain.example.com. (And put a signature of that text using your private key here)"
[schmarty]But how long should that signature be valid? If you lose control of the domain but not the key, the relme link would still be valid but you would technically be mucking with someone else's website
[schmarty]catching myself up. looks like this is the project with the "until the prover chooses to reveal them" property folks have been referencing: https://github.com/wesc/devigny-poc
[schmarty]ah, ok, yeah. i feel like this devigny scheme covers exactly the use-case we've been talking about. publish these proofs on each platform you want to show that you own, then publish the proof book on your homepage, add a little bit of discovery with rels or similar and awayyyyy you go.
[tantek]snarfed, we did specify per-platform workarounds for rel=me bidirectional links back in the 2004-era but we never codified it beyond that, nor did we come up with any platform-independent technique that worked across platforms without their explicit support: http://gmpg.org/xfn/and/#idconsolidation
[tantek]bradfitz came up with the technique of using a QR code in your platform profile image (avatar) to link back to your personal site as a rel=me claim
[tantek]That one may make the most sense these days as a method, especially given how much more broadly automatic QR code detection is supported in mobile cameras
[snarfed]QR code usability is...not great even in the real world, when you can use your camera. on a screen, you have to take a screenshot, then load that image into some app...maybe varies by person, but way harder or more work than just tapping on a link
[chrisaldrich]Has anyone messed around with interleaving QR codes into avatars? If done subtly enough like a faint watermark though not going as far as full steganography it might work to embed a rel-me into one's avatar. Then you don't have the issue of an "ugly" QR code on your photo.
[chrisaldrich]Maybe then we go full steganography and embed our 1000 word post into the photo. The bonus with this is that you get an automatic alt text from the start. 🙂
gRegorCan certainly experiment with a reader consuming `read-of` or `read-status` though I wouldn't expect most to do so until the property is more standardized
binyamin[m]What? The brainstorming section, though very wordy, includes ideas for how to write this markup. I'd like to extract those ideas and organize them.
Loqi[chrisaldrich] <p>I seem to recall @gRegorLove having some reservations about having implemented the read-status indicators. Since there are proposals for <code>watch-of</code> and <code>listen-of</code> and potentially other similar future verbs which may have a v...
Loqi[gRegor Morrill] I am proposing a session for IndieWebCamp West Coast: “Keeping Track of Books and Reading Progress.”
I would like to discuss the use-cases and experiences of using our websites to:
track books we want to read
categorize (or “shelve”) books...