kylewmsnarfed: oh so that is probably the opposite of what i want :) i want it to do that stuff on its own magically without me having to cache responses in my app
kylewmsnarfed: back to your thoughts about original post discvoery, does bridgy already take into account "already found a POSSE copy on this service"?
kylewmit sort of hurts my head to think about how aggressively to cache in the middle there... like maybe every incoming request to generate an outgoing request
Loqikylewm meant to say: it sort of hurts my head to think about how aggressively to cache in the middle there... like maybe every incoming request should generate an outgoing request
tantekI kind of gave up on that and just tried to keep the first sentence / part that goes to Twitter interesting enoughto make the permashortlink worth clicking
sensiblemn, halorgium and minsky joined the channel
tanteklike a reply using your own site to a comment on FB, but then POSSE your reply to Twitter and prefix it with the @-name of the person you're replying to on FB
JeenaI have to handle everything with care, the people who are coming are already negative to the whole web-thing (most of them are embeded programmers) so I try to help them with normal websites like blogs, etc. it's a long way to any indie stuff here ;)
KartikPrabhuJeena: I empathise. Most people I know don't know/care about owning their web-presence. IMO this stems from the the idea that either silos will be around forever or they don't really care about the things they post on silos. In either case I don't know of any good argument to convince them so <shrug>
Jeenayeah, hehe one of them has wordpress already but is not really interested in the whole social media thing, he just wants to post blogposts, the other started writing a small CMS in Haskell, but didn't show any social media interest either ;)
Zegnatphotographers are an interesting demographic as they are very concerned about their copyrights. But I have also noticed a lot of them turn out to be very non-technical outside of their niche
KartikPrabhuZegnat: but that is my point. Indieweb has the opportunity to attract the photograpers by providing them with a indieweb photography solution
ZegnatGot ya. I guess the problem is finding someone selfless enough to invest decent time into developing tools they themselves might not even use. Most of us aren’t photographers. And that goes against the scratching of your own itches idea
petermolnarI mean in theory you should not have been able to get a valid, trusted root ca published ssl cert for, for example, a bank's registered domain
tantek.comedited /2015/planning (+184) "edit list of potentials for rest of year, another possible date for SF, more sublisting, prompting for dates" (view diff)
tantekAt its simplest it's just a way to show posts on the same day but from all past years. From there you can add fancy presentation/UI to make it look nicer / more timeline-like / more navigation etc.
@misubaI used to think waves of "fuck Facebook for this change, I'm quitting" were pretty regular. Haven't seen one in a while, though. #indieweb (twitter.com/_/status/643850257206480896)
voxpelliI guess block lists would be such a kind of content where you might want to show different info depending on who accesses it – private / public and maybe even different between different private users
voxpelliif one does that and then advertises a unique URL as the rel-self that PuSH expects then one could even get private Pubsubhubbub through ordinary hubs
voxpelliit's basically https://indiewebcamp.com/indieweb-messaging where the 401 is replaced with a 200 and where the fetch isn't initiated by a WebMention but by consuming a block list or an h-feed or such
voxpellithe posts would be to broadcast the activity of adding or removing someone to the list – but the actual XFN-like list would be the canonical list of everyone blocked
voxpelliso as one can import an XFN-listin a readerto populate who one follows, then one should be able to do the same to import who to block with this
voxpelli(the interesting thing of a "u-follow-list" is that Bridgy could then easily expose the people one follows there as well so one could automatically import them into ones indie reader without manually adding them to ones own sites XFN-list)
voxpellirhiaro: yeah, unless one has a filtered h-feed that only contains follow activities and where one posts unfollows as publicly as one posts follows a list is really needed
rhiaroRead post: http://rhiaro.co.uk/2015/08/1438731932 Don't yet have /reads for a list of them all. But yeah, lists of relations with other things (people, posts, documents) could be generated from create/remove (eg. follow/unfollw) type h-entries
kylewmI'm just a little bit amused that the block list conversation got so complicated because snarfed pushed back on adding a little complexity to bridgy
tantekand if you're delegating your webmention handling to another service, including displaying, then presumably you're ok with whatever their level of blocking (or lack thereof) that's supported.
tantekbtw to all: would appreciate feedback on this list: https://indiewebcamp.com/specifications#Specs_to_iterate_on - in particular regarding rough order of simpler/shorter first, and any feedback about "yes that spec is essential to my implementation" to "no, that spec sounds hypothetical that no one needs". thanks!