[Lewis_Cowles], KartikPrabhu and [snarfed] joined the channel
#[snarfed]!tell sorry for the trouble! myfreeweb looks like granary is happy with unrelenting.technology now. haven't figured out what happened yesterday. logs do show it returned an empty response, but it was able to fetch your site fine, so i don't know yet
#[snarfed]!tell myfreeweb sorry for the trouble! looks like granary is happy with unrelenting.technology now. haven't figured out what happened yesterday. logs do show it returned an empty response, but it was able to fetch your site fine, so i don't know yet
#Loqi[snarfed] before we get too deep into plumbing, how would you want bridgy fed to federate this post? ie how would you expect it to look in Mastodon?
it's a repost, but it can't be federated as an AP repost (boost). it's not a note, so bridgy fed is reluctant ...
#[fluffy]Like, I’m not necessarily *replying* to a thing, I’m just linking to it
#[snarfed]your example post has u-in-reply-to another post on your site
#[fluffy]it just happens to reply to someone else’s blog entry, but the intention is that it be seen by my subscribers
#[snarfed]mind reading the few comments on the issue i linked? bridgy fed definitely could federate it, but it's unclear whether/how to include a reply context
#[snarfed]same thing discussed on the github issue ^
#[snarfed]also higher level background in https://snarfed.org/2015-11-29_keep-bridgy-publish-dumb . basically, bridgy and bridgy fed are useful plumbing tools, but i get reluctant to include too much user-visible presentation logic in them. i'm definitely open to discussion and ideas though!
#[fluffy]Yeah but my blog is a blog not a social media presence
#[fluffy]and I didn’t do anything particular to set that up
#[tantek]snarfed's questions are on point — there's design work to be done on the presentation side and it is non-trivial
#[snarfed]right. replies are a bit more dependent on context to be readable though
#[tantek]reply to post to silo A, POSSEing to silo B <-- no obvious design, but workable and we have some examples
#[fluffy]but none of the content that is the actual reply would be showing up in the first place
#[fluffy]This stuff is all just such a big mess, as always
#[fluffy]and I get that you’re trying to support the Right Thing but that seems to defy expectations of what’s going to actually be intended
#[tantek]repost post to silo A, POSSEing to silo B <-- no design anywhere AFAIK (last I remember discussing this with Karthik at IWC NYC 2016?) and would be kinda nonsensical to followers on B
#[fluffy]my “reply” posts aren’t really replies in the same sense as a twitter or mastodon reply though
#[tantek]fluffy, re: "like if someone would see a post via an RSS subscription" yup that's exactly why I stopped putting reply posts in my Atom feed, because it was more noisy than not to RSS subscribers
#[fluffy]if I’m posting it on my blog it’s because I intend for people to read it
#[fluffy]and I try to do things with enough context that they’re not just like a one-liner or whatever
#[tantek]same, so it is on my home page and h-feed
#[tantek]RSS subscribers have different expectations due to legacy UIs
#[fluffy]like I’ll be quoting what I’m replying to and it’s part of a larger ongoing discussion
#aaronpkif your reply posts aren't really a reply, then I'd suggest not marking them up as a reply
#Loqiresponses, or interactions, in the context of the indieweb, refer to all the different ways and things people explicitly do to and with others’s posts, from written replies to quick likes, in other words responses = replies + reactions https://indieweb.org/response
#[fluffy]okay, so, what I’m getting here is that a public response to a blog entry is not considered a reply, and a reply is specifically intended as a twitter-style response then
#aaronpkalso not sure what the like-of is doing there, because that's going to cause a consumer to disregard all the contents of the post
#[fluffy]so okay I need to adjust my mindset away from how things work in an RSS world, is what I’m getting.
#[tantek]replies are typically directly in a thread, meant to be read as part of that thread, and may even be speaking directly to the author of the in-reply-to post
#aaronpki'm not sure how the RSS world factors into this
#[tantek]I've seen inconsistent anecdotes about "how things work in an RSS world"
#[tantek]Like there is no one way "how things work in an RSS world", but there are some patterns
[jgmac1106] joined the channel
#[jgmac1106]Part of the reason I may unfollow people from Mastodon in micro.blog...i can't get the whole conversation (unless I leave) and if I reply all the reply context missing Mastodon
#[fluffy]like, if I make a “like” post of someone else’s pose I don’t want it to show up in my RSS feed as its own thing, so if someone responds to a post of mine and I like it I’ve been adding the “like” (as a webmention-only thing) into the post being responded to
#aaronpkif anything, the mindset shift is to move away from automatically adding markup/structure to every part of content
#[fluffy]I’m just trying to limit the amount of chatter that my blog generates in peoples’ feed readers while still participating in IndieWeb stuff
#[tantek]^^^ exactly why I dropped my reply posts from my Atom feed
#[jgmac1106]Fluffy can you just unfurl any link you like and display that as well as the like and link?
#[fluffy]what do you mean by ‘unfurl’ in this case?
#[tantek]my rough understanding of RSS reader users is that they expect to see original content, not responses
#aaronpkthis is why I don't put my "like" posts on my home page
#[jgmac1106]Mean take OG stuff, Activity stream and display the title, featured imagexand/or summary
#[fluffy]that’s what I thought you meant, but the question made no sense to me in the context
#[tantek]aaronpk, "like" posts in a home page composite stream were definitely a difficult design problem. I sympathize
[KevinMarks] joined the channel
#aaronpk[fluffy]: it sounds like you want people to see these "response" posts, but don't want people to see your "like" posts. that's fine, you just decide which ones to put on your feed pages
#[jgmac1106]gwg does a decent job in WordPress and swentel does with Indigenous as well
#[fluffy]that requires a bunch more plumbing in Publ (or at least in my templates) but if that’s what it takes I’ll do that instead.
#[tantek]Atom/RSS are for publishing distribution, that's all
#aaronpk[KevinMarks]: unless any modern software displays "rss native reply" posts, it's not really worth bringing up
#[tantek][fluffy] I sympathize with the "quoting [something] and it’s part of a larger ongoing discussion" format, however that needs to be a standalone blog post /article IMO and is not a "response" to any one thing in particular.
#[KevinMarks]Sorry, let me rephrase. The blogging convention was to blockquote extensively when replying, precisely because you couldn't rely on the other post being visible to your reader.
#ZegnatInteresting data point: advertisers we work with increasingly tell us they will just index our HTML themselves, do not want us to push any sort of format (like RSS) to them at all.
#[KevinMarks]Fisking is the endpoint of that approach.
#ZegnatWe have had problems with that too, e.g. if we need to redact an article, we have to contact advertisers and ask them to re-/de-index.
#[fluffy]okay so I think I know how I’ll go forward on this: I will make my atom feed *by default* not publish like-of or in-reply-to, and I’ll allow overriding that so that Pushl can access those entries.
#[schmarty]+1 to treating RSS/Atom as special formats _based on the consuming applications_
#[KevinMarks](the other pattern was a multi-author blog where you replied in the same space)
#[schmarty]in the cooking metaphor: if nobody eats it, it's not food
#Loqicontent warning is a feature of a post create UI where an author can hide by default some or all of the primary content of a post due to some concern about the nature of the content https://indieweb.org/content_warning
#[fluffy]also: my preamble isn’t necessarily the same as my summary, either
#[fluffy]by default Publ generates a summary from the first paragraph of preamble text, but that can also be overridden
#[fluffy]I do know that out-of-the-box FeedOnFeeds actually strips *all* HTML, because there’s no way to have a plugin be disabled by default and for some reason one of the other maintaners really wanted a “strip all HTML” mode. 😕
#[fluffy]well, not all HTML, but everything aside from <a> <br> <p> <div>
#[fluffy]Hm, I guess RSVP posts should also be hidden from feeds
#[fluffy]and my indieweb posts (which will still be in /blog/chatter) can generally be much much less elaborate than what I was doing before 🙂
#[fluffy]I forget what Publ does if there’s an entry with no title or content, in terms of how it’ll appear on an index or a feed… guess I’ll find out!
#[snarfed]it's kind of a case of the indieweb "let a thousand flowers bloom" philosophy, which i love, ie we all get to do whatever we want on our own sites!
#[snarfed]there are common use cases and recommendations for interop, as you mentioned, eg in readers and other common tools and services like bridgy, but they're only recommendations, not requirements
#[fluffy]well after cleaning my stuff up I decided to make a little script to make it easier to do IndieWeb likes/replies/etc., and that ended up kinda weird
#[snarfed]...but having said that, i think most people now use micropub-enabled indie readers to do this kind of thing instead, including on phone, which generally have much better UX