#indieweb 2020-02-12

2020-02-12 UTC
#
[tantek]
[snarfed], you convinced me on the don't do tag+comment as a single post thing
#
[tantek]
This is a bit different
#
[tantek]
This is closer to RSVP + comment
#
[tantek]
in that I can make an RSVP post with a yes/no/maybe/interested value *and* still leave a comment with my RSVP, and systems seem to support receiving those and "doing the right thing"
#
[tantek]
so it's still a single type, RSVP, it just happens that an RSVP can have an e-content of the comment about the RSVP
#
[tantek]
this is similar. a close-issue response with text comment
#
[tantek]
what makes this particularly different from the tag+comment case, is that the response (like RSVP) is highly specialized and constrained to a very small set. rather than tag-replies being any number of tags, and when you add comment text it's too complicated
#
[snarfed]
hmm. i understand how they differ in the data model and users' mental model, but for whether to support it in bridgy, the four problems in that comment still apply: atomicity, recovery, UX, and partial support
#
[tantek]
I don't understand atomicity
#
[snarfed]
arguably we can return a reasonable error in the partial support case, but at least the first three
#
[tantek]
the "close" is the atomic action. if it fails the whole thing fails
#
[snarfed]
if the github API exposes comment + close as a single atomic API call, then yes, that specific case would be ok. i don't know that it offers that though
#
[tantek]
ah that would be a blocker. I suppose I am presuming because there's a button for "Close issue", that there would be an API for it
#
[tantek]
I might as well stick with my same plain text pattern that I brainstormed
#
[tantek]
[snarfed], in broader scope, an "issue" really is more than a "blog post", and allows a different set of responses, including close/re-open, and lock/unlock. We basically need to model those, and I'd presume GitHub has APIs for all four of them. If not, that would be useful to know.
#
[tantek]
Maybe I should file an exploratory issue for Bridgy Publish for this "explore Bridgy Publish to GitHub special responses to issues close, re-open, lock, unlock"? Or would you prefer proposed markup first?
#
[snarfed]
sure! feel free to file that. https://indieweb.org/issue etc
#
[tantek]
Thank you. I'll start by adding a "Special Responses" section to /issue#Brainstorming to capture this analysis
#
[tantek]
[snarfed], to be clear, if it turns out that those special responses are their own "atomic" thing, without any text comment, that would still be very useful. E.g. just now after POSSEing my reply to an issue, I went to GitHub manually and all I did was click the "Close issue" button, and it showed up as a separate action in the list of things "done to" the issue
#
[tantek]
I figure exploring the API will help reveal at least one perspective on this
#
[snarfed]
sure! i mentioned the same thing when we talked about this last. see https://indieweb.org/issue#Close_and_re-open_issues_when_commenting
#
[snarfed]
=> #indieweb-dev
turona and KartikPrabhu joined the channel
#
sivy
still, the question of how best to transform an article or Note into a tweet plagues me
#
sivy
i either need to make anything with links in it an article and force the title, or make myself stop putting links in Notes
#
sivy
or something else entirely not that
#
sivy
lol
turona joined the channel
#
[tantek]
sivy, there's nothing wrong with links in notes. What difficulty are you having?
#
[tantek]
[snarfed] interesting I seem to be getting a publish failure POSEEing a reply to a pull request
#
[snarfed]
what was the error response?
#
Loqi
It looks like we don't have a page for "error response" yet. Would you like to create it? (Or just say "error response is ____", a sentence describing the term)
#
[snarfed]
ah. 400, "Please remove the fragment #DISCUSSION_R377968664 from your in-reply-to URL."
#
[snarfed]
for 4xxes, the webmention http response is generally easier to read and understand, if you have it
#
[tantek]
oh I can't reply to a specific comment in the discussion on the PR?
#
[snarfed]
ah yeah PRs have very complicated features (line #s, reviews, previous comments, etc) that bridgy publish definitely doesn't try to support
#
[tantek]
got it. I should've checked the docs
[chrisaldrich] and chimo joined the channel
#
[tantek]
snarfed, replying to a specific comment on an issue works, but not to a specific comment on an PR
#
[tantek]
I'll make a PR on Bridgy Docs to clarify
#
sivy
[tantek] oh it's fine on my site, but my twitter-syndicator strips html, so I lose them. then it's a matter of deciding how to format the tweet so what I want fits in 280 chars
#
Loqi
It seems that there is no good thing that our white capitalist society cannot turn to evil - take for example the independent contractor #work #capitalism https://twitter.com/thotscholar/status/1227266798413897728?s=20
#
sivy
which lost it's internal link when posted to twitter: https://twitter.com/steveivy/status/1227359623214059522
#
@steveivy
It seems that there is no good thing that our white capitalist society cannot turn to evil - take for example the independent contractor #work #capitalism https://twitter.com/thotscholar/status/1227266798413897728?s=20 (monkinetic txt-b163e62)
(twitter.com/_/status/1227359623214059522)
#
sivy
(there's a link on
#
sivy
"independent contractor"
#
sivy
)
#
sivy
anyway, i keep changing my Note->tweet algorithm, trying to get as much of the original intent in there as possible
KempfCreative joined the channel
#
[snarfed]
i and others here still POSSE to twitter manually (and other silos too) for this ^ and other reasons
#
[snarfed]
manual until it hurts
KartikPrabhu joined the channel
#
sivy
I'm tempted to support the old wordpress <!--break--> syntax
#
sivy
anything above could be the tweet :)
#
sivy
but again, makes me think about lenghts
#
sivy
b00
#
sivy
well, http://monkinetic.blog/archive <- light blue are notes/tweets
#
Loqi
Steve Ivy
#
sivy
I think I do it enough to want to make it nice :)
#
sivy
hm, techincaly the darkers blue
#
sivy
lighter as in "more transparent"
#
[tantek]
what no
#
[tantek]
this is all making much too complicated sivy
#
[tantek]
let's move this to dev to discuss specific POSSE techniques in code
#
[tantek]
# indieweb-dev that is
#
sivy
sory
#
sivy
i had not intended to get so deep :)
[jgmac1106] joined the channel
#
[tantek]
whoa new reacji on GitHub since Bridgy Docs were last touched
#
[tantek]
going to update the docs assuming the new reacji will "just work" in Bridgy 😄
#
[tantek]
oh wait, going to update /reacji first
kensp, sivy, KempfCreative, [Jeff_Hawkins], KempfCreative1, jakelazaroff, dg, KartikPrabhu, [xavierroy], nickodd, R2ZER0, wolftune, kensp1, [Michael_Beckwit, swentel, bltavares_, jihaisse, wiedi and [tantek] joined the channel; nickodd left the channel
#
[tantek]
Done and done and done
sukil, [LewisCowles], aquarius_, R2ZER0, gxt and [jeremycherfas] joined the channel
#
jeremycherfas
Good morning IndieWeb
R2ZER0 and [jgmac1106] joined the channel
#
[jgmac1106]
morning jeremy
gxt, sscarfe, anotheryou and R2ZER0 joined the channel
#
[jgmac1106]
ugg all my sites are down, I am hitting the process limit on my shared host......something leaking something somewhere
likus, sscarfe, R2ZER0, sivy, [grantcodes] and beko[m] joined the channel
#
beko[m]
Found https://github.com/RSS-Bridge/rss-bridge#rant and it's my latest favourite toy so far. It's hard to dismiss FB completely because some projects are really only there. This one does a great scraping job for my microsub server.
#
Loqi
[RSS-Bridge] rss-bridge: The RSS feed for websites missing it
R2ZER0, [LewisCowles], KempfCreative, tsrt^, [tantek], gareppa, [manton], petermolnar, [xavierroy], jakelazaroff, [snarfed], KartikPrabhu, eli_oat, IWSlackGateway, [schmarty] and [KevinMarks] joined the channel
#
[KevinMarks]
[snarfed] didn't as1 have verbs for issue management, or was that added in as2? (Jira has as1 output iirc)
R2ZER0, wolftune, dckc, sscarfe and [snarfed] joined the channel
#
[snarfed]
evidently not in 2 though
KartikPrabhu joined the channel
#
[snarfed]
granary supports and emits AS1 objectType issue and pull-request
sscarfe, KartikPrabhu, [jgmac1106], kensp, R2ZER0, opal, [chrisaldrich], Decobus_, wolftune, gRegorLove, NinjaTrappeur, [tantek], mauz555, [Aaron_Klemm], swentel, tantek, nickodd, leg and KempfCreative joined the channel
#
[tantek]
still takes me far too long to "do" a photo post.
#
[tantek]
I need to document all the steps I'm going through, and how much of that is "content authoring" vs futzing with "UI"
#
[tantek]
too long like >30min 🙈
#
[tantek]
to be clear, multiphoto posts in particular
#
[tantek]
There's definitely a lot of "content authoring" time. Choosing which photos to include in a multiphoto (among potentially a dozen or more). Choosing an *order* for the photos to tell a story / write the story/narrative (sometimes these two have to happen simultaneously). Maybe add more photos if the narrative requires it. Write alt text for each photo. Give proper photo credit if any of the photos were taken by someone else. Choose hashtags.
#
[tantek]
Wondering if anyone else overthinks their /multiphoto posts like this 😂
#
[tantek]
KevinMarks, ActivityStreams/feed/verbs discussion -> dev please 🙂
R2ZER0 joined the channel
#
[jgmac1106]
Just 60 days to go Tantek, plenty of time to reflect on that question...
#
[tantek]
You would think I would be faster at it at this point. 42 days completed.
#
[tantek]
42 and I still don't have the answer. 😛
R2ZER0 joined the channel
#
[jgmac1106]
hee hee, I need to count I don't know if I am same, 1 day, or 2 days behind you....Would want to celebrate day 42,.....though I somehow picked up a 30 day poetry challenge along the way as well
#
[tantek]
I don't have a theme, though I think nearly all of them are *outside*
#
[jgmac1106]
your theme is positive posting through photos
[Michael_Beckwit joined the channel
#
[jgmac1106]
and avoiding alliteration always
[Lauro], KartikPrabhu, dougbeal|mb1, kensp, [KevinMarks], wolftune, delli3, wiedi and R2ZER0 joined the channel; leg left the channel
#
[KevinMarks]
the stream of photos model is pretty much what the buzzfeed editor is built around
#
[KevinMarks]
it's worth a look for UI ideas
KartikPrabhu, wolftune, Choscura, plutes, caolanm, crazed, nickodd, mauz555, gRegorLove, [Michael_Beckwit, R2ZER0 and deathrow1 joined the channel; nickodd left the channel
#
sivy
<3
deathrow1 joined the channel