mblaneyvoxpelli: I lost that post about a follow webaction when my server crashed last year... had to restore from a backup and that was the only post I missed :-(
nelsonInstead, I should look for an open source application that will post to Twitter and Facebook, and whatever else, when it sees the special keystroke.
petermolnarI was thinking about a reverse-subscribe method for a reader: a micropub-like receiver on site A ( my site ), that can receive webmentions; site B has indieauth set up, and for authenticated handles lets them add a single endpoint for the same base url that will get a webmention from every update/new post
tantekif you can rephrase it starting with user actions and then in nested explanation the server bits, that would be worth adding to /follow#Brainstorming
tantekthat's the key part of webmention - it's not abstract like source has something to do with target, it's concrete, source *linked* to target, and for the rest of the information, go get source
tantekthe point is not to ask "how can I use webmention to solve this problem" the point is to ask how can I solve this problem with user-actions, and then what posts/protocols/formats could/would work to solve those user actions?
tantekmy point is that Twitter's message "sign-up or login to follow ..." is an explanation for *why* you should sign-up or login even if you just want to follow
petermolnarI'm not going to say that's just wording something, because I know it's important, but maybe not the very first step before any working demo for us, nerds; my question is that would anyone be interested in testing this out, does anyone believe this should be a thing to offer for visitors?
voxpellipetermolnar: very rarely will someone indieauth into a subscribeable site imho – indieauth is something you do to known tools, indie-config and such is what you do to unknown third-parties
voxpelliI also fail to see why folling an h-feed by itself and upgrade it to realtime with pubsubhubbub as a progressive enhancement isn't technically enough for a subscribe/follow use case
Loqivoxpelli meant to say: I also fail to see why following an h-feed by itself and upgrade it to realtime with pubsubhubbub as a progressive enhancement isn't technically enough for a subscribe/follow use case
voxpellithe way I see it we need more readers that experiment with current tech so we can learn more about the limitations and possibilities it has, before any new tech gets involved
petermolnarok, I'll rephrase it: me, as petermolnar.eu gets a visitor; the visitor wants to follow (parts of) the site so there is a "follow"(ish) button
tantekvoxpelli: agreed on all points. especially, I'd rather see innovation / iteration on *integrated* indieweb reading, as that's where the silos still have a VERY big advantage.
tantekI'd rather not spend time developing more tech/interactions for *separate* readers. That's the old model and by sticking with that we will never get to silo levels of good UX
LoqiPubSubHubbub (PuSH) is a notification-based protocol for publishing and subscribing to streams and legacy feed files in real time https://indiewebcamp.com/PuSH
voxpelliand having a separate hub is fully optional, just like a webmention endpoint can be part of ones site or separate a PuSH "hub" can be part of ones site or separate
kylewm!tell tantek of course you're welcome to share my post, but i don't believe it has much bearing on ActivityStreams in general, more about internal bits of the Known codebase
aaronpkif you have rel=author somewhere with the same URL that's the URL of the h-card in the footer then the authorship algorithm will find that footer h-card as the author of the post
aaronpkhm, something the authorship algorithm might benefit from is "upgrading" the author info if there is a more complete h-card elsewhere on the page with a matching URL
aaronpk"implementer experience" is shorthand for the idea of seeing how a spec actually works in the wild with people who are trying to accomplish a goal that isn't the spec itself
Loqitantek: kylewm left you a message 40 minutes ago: of course you're welcome to share my post, but i don't believe it has much bearing on ActivityStreams in general, more about internal bits of the Known codebase http://indiewebcamp.com/irc/2016-02-28/line/1456700276200
tantekkylewm: internal bits of the Known codebase which got guided by AS-like thinking/design to start with, and said thinking/design led to the complexities/inefficiencies which you are fixing