[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 ...
[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]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!
[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
[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
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
[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
[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
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
[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.
[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.
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]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. 😕
[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