[00:04] <krytarik> Bashing-om: Hmm, can you try putting the first of those links as "<https://discourse.ubuntu.com/t/call-for-nominations-for-the-local-communities-council/39557>" instead?
[00:04] <Bashing-om> krytarik: Are you caught up presently - question here for ./summary-uwn-discourse.pl 810 failure.
[00:05] <krytarik> I'll run it locally here and see if I get one too..
[00:06] <krytarik> Nope, appears to work here.
[00:06] <Bashing-om> krytarik: ^ clairify replace the leading spaces with "<" and end the links with ">" ?
[00:07] <krytarik> Did you update your local copy of the repo yet?
[00:08] <krytarik> Yeah, exactly - but just try with one of them first and see if that makes the link being spelled out raw.
[00:08] <Bashing-om> krytarik: I am on 22.04 and running the ./summary-uwn script I get "Can't locate JSON.pm in @INC" / I again know nothing of JSON.
[00:12] <krytarik> Bashing-om: Install "libjson-perl"
[00:13] <Bashing-om> krytarik: 1st link modified "<.....>" looks and works good - make all the links such as now ? 
[00:15] <krytarik> Yeah, and I'll make the publish script drop those for the other platforms again (email and forums)
[00:16] <Bashing-om> krytarik: You the man. Install of libjson-perl does the tricvk :D 
[00:23] <krytarik> It seems we need to surround all Discourse links like this though, since on the inline ones it doesn't do the previews but still does the title text.
[00:24] <Bashing-om> krytarik: Ack on ALL links - making it so :D
[00:26] <krytarik> Not all.. just the summary ones we already did plus any further Discourse ones.
[00:27] <krytarik> Should be the ones in the LoCo Events and the Meeting Reports section.
[00:28] <Bashing-om> krytarik: Those sumary links done.// LocO Events and Meeting Reports comming up :D
[00:29] <krytarik> The Delhi one between the summaries looks erroneously formatted btw.
[00:31] <krytarik> And please drop the leading space off all of those.
[00:44] <krytarik> Just pushed said update to the publish script to the repo btw.
[00:55] <Bashing-om> UWN: Discourse edits saved // next edits ?
[00:56] <krytarik> Was just going to say "#ftag=RSSbaffb68" should be dropped from the Sputnik link! >_<
[00:59] <krytarik> I'm still seeing wrong or missing formatting on some of the links btw.. not sure whether that's due to caching or you didn't actually fix those yet..
[01:01] <Bashing-om> krytarik: Leading spaces ! removed - sorry lots of distractions currently.
[01:02] <krytarik> https://discourse.ubuntu.com/t/upcoming-events-for-azloco/38466 - still needs the brackets in the LoCo Events section.
[01:06] <krytarik> Might want to do the latter one in the template too, and for good measure while they aren't rendered differently currently, the other two links there too.
[01:07] <Bashing-om> LoCo event links edited.
[01:20] <Bashing-om> UWN: Template edited for LoCo Events links and extraineous new lines through out.
[01:25] <krytarik> https://ubuntu.social/@UbuntuWeeklyNews - I was just thinking we might finally want to add this to the Subscribe section, but looking at it I wonder if we could make manual and thus add more text to the postings, since it looks rather crappy the way it is.. :3
[01:28] <Bashing-om> krytarik: crappy yes - there is a 500 character limit to the Mastodon post :(
[01:30] <krytarik> Well, that's not the issue here though, we know similar from Twitter and it suffices for us.. but rather the postings are done by a bot and therefore only the page title and the link are picked up, which makes it look rather slim..
[01:33] <Bashing-om> krytarik: Oh - yeah - maybe we can discuss altering with popey to get a better presence ?
[01:37] <krytarik> Yeah, since it's the only social platform we want to post to anymore, it'd be great if you guys (being the Ubuntu Members between us eligible for using that instance) could try to get in contact with popey and look at possible options to improve there.
[01:43] <Bashing-om> krytarik: Talking to popey now on my to-do list.
[01:43] <krytarik> Bashing-om: And please don't forget to update your local copy of the UWN repo once more (as mentioned again in today's channel log), so you'll have no issues publishing tomorrow.
[01:47] <Bashing-om> krytarik: Thanks for the reminder to update - publishing tomorrow: How now to handle pushing out to ubuntu-news.email for the Mailing List ? 
[01:51] <guiverc> Bashing-om, a run of `perl publish-uwn-discourse.pl 810` has a `ubuntu-news.email` created that looks fine (i only looked a few pages down; graphic header at top won't be viewable I bet on email)
[01:53] <krytarik> Yeah, I've since made the script drop the images for the email.
[01:56]  * guiverc suspects my branch is set to master (not discourse)
[02:02] <guiverc> i tried switching branch (`git checkout discourse` & `git fetch`) but I'm still getting the image on email; fridge file also only ~header/tailer detail
[04:08] <guiverc> uwn 810 looks good to me Bashing-om 
[04:15] <Bashing-om> guiverc: Been fraught getting there :D Still with some concern that all T's crossed and all I's dotted.; Will see how we look when we publish tomorrow. 
[04:16] <guiverc> yep.
[04:31] <Bashing-om> guiverc: Found another i that I dotted :P
[04:58] <guiverc> :)
[11:41] <popey> Happy to hand over the mastodon account if someone wants to post like a human rather than a summarised bot krytarik. Bashing-om pinged me last night and I told them the same.
[12:56] <guiverc> thanks popey 
[19:33] <Bashing-om> UWN: Pulling "WIP" - Log checked and no further edits are known -- Will start the push soonest - see how things run :)
[19:48] <Bashing-om> UWN: M/L is away - Doing to Forums posting next - So far krytarik's works looks mighty fine :D 
[20:01] <Bashing-om> UWN: Forums Post done - Looking good. Doing the Re-directs next and making the Discourse edits.
[20:26] <Bashing-om> UWN: Re-directs/edit done - next up is a Mastodon blog.
[21:08] <Bashing-om> UWN: Masodon blog done up. 
[21:12] <Bashing-om> krytarik: When you have eyes on - popey gives us the UbuntuWeeklyNews bot's code >> "if someone else wants to take over the bot, happy to hand it to someone on your team."
[21:28] <krytarik> Bashing-om: Yeah, I've seen his offer in the log.  And if either of you is willing to run the account for us, that'd be great I think - no idea how this technically works on Mastodon though.. a) dedicated credentials for the account or b) access to it through your own users there.
[21:32] <Bashing-om> krytarik: My UWN plate is pretty full as is - However, soon as I have the spare time I look at the bot code and consider my skill set.
[21:39] <popey> technically it's just an account on mastodon like any other
[21:39] <popey> you could paste what you put in your own mastodon account on the uwn one
[21:40] <Bashing-om> popey: Great - that method would be handy inddeed - on my to-see-about list now :P
[21:41] <popey> +1
[21:50] -ubottu:#ubuntu-news- ::omg!ubuntu:: KDE Plasma 6.0 Release Date is Feb 28, 2024 @ https://www.omgubuntu.co.uk/2023/10/kde-plasma-6-0-release-date-is-feb-28-2024
[22:14] <guiverc> https://fridge.ubuntu.com/2023/10/23/ubuntu-weekly-newsletter-issue-810/
[22:14] <guiverc> ^ that is heavily edited
[22:14]  * guiverc has a unpleasant headache; thus real slow
[22:18] <Bashing-om> guiverc: a headache == NoFun - checking what the Fridge looks like.
[22:19] <guiverc> no links in it; as using the discourse post
[22:19] <guiverc> (link checking was easier; as so few)
[22:21] <guiverc> uwn 810 posted to twitter, telegram, (mewe)
[22:21] <Bashing-om> guiverc: Yup - not good  - not of much value without links working :(
[22:22]  * guiverc just noted I missed PLANET link there too, so won't appear there.. correcting that
[22:23] <Bashing-om> guiverc: My next is to copy the template for 811 / got any edits in mind for the template ? >> remove camel''case .
[22:23] <guiverc> nope (on any edits).. i'm not thinking now anyway..   go ahead
[22:24]  * guiverc returning to bed..   I'll hear this box ping, but maybe slowish responding
[22:24] <Bashing-om> doing Discourse re-set :D
[22:47] <Bashing-om> guiverc: When you return - Fridge: "In this issue we cover:" no hyperlinks are active :(
[22:48] <Bashing-om> UWN: Discourse 811 set to go.
[22:57] <guiverc> no links are there.. ` perl publish-uwn-discourse.pl 810` didn't create anything, so it was just copy/paste of "In this issue" from discourse, added in form of list <li></li>
[23:00] <Bashing-om> guiverc: ack.
[23:01] <krytarik> Bashing-om: Yeah, as I said twice before, Discourse doesn't (easily or at all) offer what wiki did and let you link directly to a topic in a post.
[23:02] <guiverc> i can copy/paste links so they point to wiki ; but discourse only was the purpose I thought
[23:02] <krytarik> guiverc: That would be because you failed to update your local copy of the repo yet though.
[23:04] <guiverc> i ran 'git checkout discourse' (already there), 'git fetch' (no answer) so I assumed it was updated.. but I may have run older copy & not latest in error (if $PWD wasn't correct)
[23:05] <krytarik> If you did run only these two then yes, you missed to main command there.
[23:05] <guiverc> which is (headache & not thinking clearly sorry)
[23:06] <krytarik> First, when you do "git log" there, do you see the WIP commit in the log?
[23:08] <guiverc> Bashing-om, links there now (via wiki 810 since we have it)
[23:08] <guiverc> https://fridge.ubuntu.com/2023/10/23/ubuntu-weekly-newsletter-issue-810/
[23:09] <guiverc> Date:   Tue Oct 17 04:50:04 2023 +0200 ; your latest listed
[23:09] <krytarik> Mildy fun though to link to the "full version" on Discourse but link the subtopics to the wiki..
[23:11] <krytarik> Is that the Discourse migration commit?
[23:11] <guiverc> yeah I know - intentional.. the unedited was to discourse, only sublinks were modified to point to wiki (given discourse link not possible except to thread as I undersand it)
[23:11] <Bashing-om> guiverc: ^ "git log" >> Date:   Mon Oct 23 02:23:04 2023 +0200 .
[23:11] <guiverc> [WIP] Update scripts for Discourse migration
[23:12] <guiverc> yeah looks like I'm behind sorry
[23:13]  * guiverc not updating now sorry; returning to bed (headache)
[23:13] <krytarik> guiverc: Try "git fetch origin discourse" (to make sure you fetch the correct branch) followed by "git reset --hard origin/discourse"
[23:13] <krytarik> When you can anyway..
[23:15] <Bashing-om> Fridge: spot check and all happy happy.
[23:17] <krytarik> Bashing-om: Since we are now linking to the wiki page.. it still says WIP at the top and were there any changes that you didn't sync yet?
[23:19] <Bashing-om> krytarik: No - I am updated - perhaps the WIKI results from my manually making the page up prior to reading the channel logs ? // then when the scriipt was ran, did not over write the page ?
[23:21] <krytarik> Well yes, the wiki page is from when you manually created it alongside the Discourse post, and of course since nobody deleted it yet it's still there - and now linked to from the Fridge post.
[23:29] <Bashing-om> krytarik: removed "WIP" on WIKI // Next week things be good having your scripts handle the details ?
[23:31] <krytarik> What?  The scripts were ready this time even, but somebody felt it's necessary to create a wiki page alongside! :P
[23:32] <krytarik> https://meta.discourse.org/t/link-to-a-heading-within-a-post-or-topic/47552 - in the meantime you could see if you can make anything of this.
[23:34] <krytarik> And to be absolutely clear here, missing support for direct linking on a page (Discourse or otherwise) isn't something one can fix from the outside.
[23:37] <krytarik> The way I read the post I just linked to is that you are supposed to just hover over any existing header and get the link icon which exposes a direct link - which does work in the very post but not on our Discourse instance.
[23:47] <krytarik> Huh, just as I was guessing already.. looks like our instance is on version 2.6.0 which is like three years old by now, while the feature is only available since version 2.7.0 XD
[23:49] <Bashing-om> krytarik: Good sluething :D
[23:52] <krytarik> https://meta.discourse.org/c/releases/30 - for reference.