#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
#kylewmnetwork topology stuff is kind of counter-intuitive
#[snarfed]one thing is that req'ts for archiving are mostly disconnected from req'ts for caching
#[snarfed]eg you can archive and still try to refresh each time
#[snarfed]and caching req'ts are also mostly disconnected from fetching strategy
#[snarfed]eg you can always request with an etag if you have one, even if you decide your own cached page is expired
#tantekAlso I've been having very good responses/interactions with "long notes" when they're POSSEd fully intact into FB (e.g. using Bridgy Publish)
#tantekso much so that I'm definitely tempted to use Bridgy Publish for any POSSE to FB automatically when the length of the note is > tweet length
#KartikPrabhuyes I have a lot of trouble condensing long notes to fit Twitter's mandates
reidab joined the channel
#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
#tantekanyone else here POSSE replies outside of their original post context?
tantek and mdik_ 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
#KartikPrabhuI do that with likes and disguise them as normal posts on the silo
#tantekwhoa interesting. have you documented this practice anywhere
#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 ;)
#Jeenaand by indie stuff I mean the things we write about in the wiki like webmentions, etc.
#ZegnatJeena: I guess getting them started with Known as a blog might be a good idea? It would instantly have them connected to the IndieWeb
pfefferle joined the channel
#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 ;)
#KartikPrabhunot having social media is fine but enabling website-to-website comments might be of interest to them
#KartikPrabhuIn fact I have found that photographers and designers are more inclined to own their data
#Jeenathat is why I am trying to find out where to find people who are interested but just haven't heard about IndieWeb yet
#KartikPrabhuspecially photographers who want to keep their photos and avoid absurd censorship rules of the silos
#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
#KartikPrabhuI do a lot of photography and photo hosting is on my itch-list, but it is enough work that I have never started it
#KartikPrabhuas a fallback I host my photos on Google Photos :P
LauraJ joined the channel
#ZegnatHas anyone here requested to be part of the Let’s Encrypt beta?
#petermolnarthe other thing is that SSL in theory was something checked
#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)
#tantekDoes anyone else implement "On This Day" functionality on their site?
#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.
#tantekTheoretically you can do this for any "day"
snarfed, mlncn, elf-pavlik, cleverdevil, tantek, chreekat, eschnou, sensiblemn and KartikPrabhu joined the channel
#GWGtantek: Depends. If it involves venues...I'm not tackling that. But if I can help out, I will.
#tantekGWG - that's ok - put that in as a caveat then. Explicitly list what you *can* help out with.
snarfed joined the channel
#@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)
#tantekwhat if I wanted to include someone else's block list in my own, dynamically?
#voxpelliKevinMarks: micropub already has a way to query for information – so that would basically be building a "block api"
#KevinMarksthe challenge is delegated auth between indie services, but I think indieauth is robust enough to do that
#tantekand then what if someone else wanted to then include my entire block list (including what I dynamically included) ?
#tantekcould we form a ... wait for it ... block chain?
#KevinMarksright, I'm thinking more about the UI for "there is webmention abuse on my page - I want to remove this and propagate the block" idea
#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
#voxpelliand same could work for block list and h-feeds and everything
#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
#KevinMarksso then I would webmention the block post to my upstream indieservices
#voxpelliKevinMarks: I rather think they would discover it from your profile and import/subscribe to it
#KevinMarksright, I was thinking about the 'get this off my page now' case
gavinc joined the channel
#KevinMarkswhere a webmention may be better than a polling based model
#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)
#voxpelliI think "u-follow-list" and "u-block-list" has a whitelist/blacklist kind of relation – so they go kind of hand in hand
#rhiaroI have started posseing twitter follows when I remember: http://rhiaro.co.uk/follows But not yet generating a list of rel=follows from that
#rhiaroWould like to, for readers to be able to discover automatically
#rhiaroso I have follow posts, but not a follow list, though the list can be implied from the posts
#rhiaromaking it explicit is probably more useful for search/discovery
#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
#tantekelf-pavlik: nope - based on real world implementation needs
#voxpelli(I would _never_ publicly announce that I'm unfollowing someone)
#tantekvoxpelli: people publicly announce unfollowings on Twitter all the time
#rhiarovoxpelli: right. I think about generating the list as kind of a 'side effect' of follows and unfollows posts
tantek joined the channel
#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
interactivist, cleverdevil-, eschnou and tantek joined the channel
#tantekindeed kylewm - it really is up to the receiving site to handle blocking etc. anything else is value added by services in the middle
#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.
lukebrooker joined the channel
#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!