2021-04-04 UTC
[scojjac], Seirdy0, [tantek], sumner, petermolnar_, [snarfed], [jeremycherfas] and tomlarkworthy joined the channel
# 06:36 tomlarkworthy I don't think http is safe so I would be no.
# 07:04 beko !tell [snarfed] Seems that Bridgy does not accept re-publishing. Probably because the old job is still hanging on "Processing"
# 07:04 Loqi Ok, I'll tell them that when I see them next
dhanesh, [KevinMarks], PauloPinto, Zegnat and [tantek] joined the channel
# 15:07 [tantek] beko, I think that's "expected" behavior, that is, if Bridgy Publish thinks it has handled a permalink already, then it does nothing. I've had to update (change) my permalinks in order to get Bridgy to re-publish something (e.g. when I've manually deleted the POSSE copy due to an error etc.)
[snarfed] joined the channel
# 15:14 Loqi [snarfed] #84 allow updating a published post
# 15:14 [snarfed] in this case though, the publish attempt died halfway through due to an underlying infra failure, and it never actually completed
# 15:14 [tantek] and this is a good reason to have non-essential slugs in your URLs
# 15:23 [tantek] publish, Bridgy Publish POSSE. see mistake, edit post & permalink slug, delete POSSE copy, re-run Bridgy Publish POSSE.
# 15:23 [snarfed] yeah, i get it. just unfortunate that bridgy’s plumbing tail here is wagging the URL UX dog
# 15:24 [tantek] editing is a real use-case, and there's no less awkward way I know of doing that with POSSE (that uses Bridgy Publish)
# 15:25 [snarfed] beko i’ve manually marked that old publish attempt as errored, you should be able to retry now. thanks for your patience!
[fluffy] joined the channel
nertzy, KartikPrabhu, [KevinMarks], nertzy_, [tantek], alex__, [schmarty], alex11 and oedmarap joined the channel