#editorial | Logs for 2020-02-12

« return
[02:53:49] -!- AzumaHazuki [AzumaHazuki!~hazuki@the.end.of.time] has joined #editorial
[03:07:19] <Bytram> =g JEDEC
[03:07:20] <systemd> https://www.jedec.org - JEDEC: Home
[03:07:27] <Bytram> =g JEDEC wikipedia
[03:07:27] <systemd> https://en.wikipedia.org - JEDEC - Wikipedia
[03:46:10] <Bytram> whereto? http://feedproxy.google.com
[03:46:11] <systemd> ^ 03In the future you could fly inside one huge wing ( https://www.cnet.com )
[07:39:41] -!- AzumaHazuki has quit [Quit: Leaving]
[07:52:30] <janrinok> another day, another lurk on here...
[08:00:43] <chromas> Did you get the bug report about missing storybot output?
[08:24:21] <janrinok> yeah, fixed thanks
[08:25:41] <janrinok> it was a combination of multiple tag links in a single sentence, and the use of 2 different domains for each of the tags.
[08:27:01] <janrinok> the regexes and xml searching got a bit confused
[08:31:40] <janrinok> ~eds: Why have we started using spoilers for such things as lists of links etc? They don't spoil anyone's enjoyment of the subject matter, on the contrary, they enhance it.
[08:32:01] <chromas> I think it's just to collapse it
[08:32:49] <chromas> Seems like there was a project to make a 'generic', non-spoiler version of the collapsible block, although <details> is a thing
[08:33:31] <janrinok> well, we have extended copy for that sort of thing. Spoilers have a specific meaning - or so I thought - so do we need another form of reporting things that cannot use Intro or Extended Copy, and what are those things?
[08:33:55] <chromas> I dunno. ~blame
[08:34:23] <janrinok> I just haven't seen any discussion on this and I was wondering if I had missed something...
[08:35:01] <chromas> Not that I recall. I've mostly just seen Bytram doing it
[08:35:25] * chromas puts a demerit sticker on Bytram's progress sheet
[08:35:33] <janrinok> The easy way would be to rename Spoilers to Details, wouldn't it?
[08:36:43] <janrinok> Spoilers shouldn't contain data that is relevant to the topic under discussion, but things that would spoil someone else's enjoyment of the media being discussed.
[08:38:30] <janrinok> just my 0.02c
[09:03:07] <carny> that's always a concern
[09:03:23] <carny> you might have to rewrite part of the block quotes so that you don't spoil things while you're giving points that are important to the discussion
[09:03:56] <janrinok> but we do that all the time - that is the editing role
[09:04:53] <janrinok> For the time being I've simply restructured the links into the Extended Copy as usual
[09:05:34] <janrinok> These are not links related to individual items, but a dozen or so links containing further information.
[09:06:31] <janrinok> links in quoted text are kept exactly as is. These are additional links that the first editor included to provide amplification and previous reporting.
[09:07:09] <janrinok> anyway, how are you today, carny
[09:11:28] * Cascade pipes up just to confuse janrinok's tab completion >:)
[09:13:48] <janrinok> the only thing that is confusing me is who or what the hell is Cascade?
[09:17:41] <Cascade> A tasty beverage and I think a mountain range
[09:18:21] <janrinok> fairy 'nuff
[09:50:20] <FatPhil> janrinok: that quantum story you're looking at is a dupe, I'm sure
[09:51:37] <FatPhil> https://soylentnews.org
[09:51:39] <systemd> ^ 03'Remarkable' Mathematical Proof Describes How to Solve Seemingly Impossible Computing Problem - SoylentNews
[09:51:39] <exec> └─ 13'Remarkable' Mathematical Proof Describes How to Solve Seemingly Impossible Computing Problem - SoylentNews
[11:25:56] -!- spiraldancing has quit [Ping timeout: 244 seconds]
[12:58:12] <Bytram> janrinok: chromas: I was using <spoiler> ... </spoiler> as a means to hide "Previously" links when they looked like a wall-of-text... completely forgetting that it is not, technically, a spoiler! Doh. There was talk of a generalized collapsible element whose presented text could be selected by the writer... something like <hide text="Lots of Links"> ... </hide> or something *like* that.
[12:58:17] <Bytram> ~blame
[12:58:18] * exec points at Bytram
[12:58:51] <Bytram> coffee++
[12:58:51] <Bender> karma - coffee: 108
[13:01:03] <Bytram> Fnord666: Congratulations on posting your 4,400th story! Woo Hoo! ( see: https://soylentnews.org and/or https://soylentnews.org )
[13:01:16] <systemd> ^ 03SoylentNews: Hall of Fame ( https://soylentnews.org )
[13:01:17] <systemd> ^ 03SoylentNews: Authors
[13:01:18] <exec> ├─ 13SoylentNews: Hall of Fame
[13:01:18] <exec> └─ 13SoylentNews: Authors
[13:03:39] <janrinok> Bytram, no problem - it is your train set ;) I just wondered if there had been a discussion or decision that I was unaware of. I've moved the links in the MWC story to the Extended Copy section.
[13:08:06] <Bytram> janrinok: Nope, no discussion at all. I have a local tool that encapsulates SoylentNews' Search page to look for: stories in any section that contains $stuff with results returned with newest first... from the HTML that is returned, creates what you've seen me recently use:
[13:08:16] <Bytram> Previously:
[13:08:38] <Bytram> <a href=".........">Story1 title</a> 
[13:08:46] <Bytram> <a href=".........">Story2 title</a> 
[13:08:48] <Bytram> etc.
[13:09:37] <Bytram> we really do need some other tag, but I cannot remember off-hand what was suggested before as the tag name. Can anyone here refresh my memory?
[13:13:05] -!- spiraldancing [spiraldancing!~spiraldan@Soylent/Staff/Editor/spiraldancing] has joined #editorial
[13:13:05] -!- mode/#editorial [+v spiraldancing] by Hephaestus
[13:13:08] <Bytram> For historical reference: "(Note: only the characters a-zA-Z0-9$_.+!*'(),-, plus space, are allowed in nicknames, and all others will be stripped out.)"
[13:42:53] <Bytram> break time
[13:44:14] <janrinok> back in 2 hours - got to go and talk English with some schoolkids
[15:00:21] -!- spiraldancing has quit [Ping timeout: 244 seconds]
[15:55:07] <janrinok> I enjoyed the last couple of hours - but I wouldn't want to be a full-time teacher.
[15:57:58] <janrinok> Bytram - is your local tool something that would work for anyone, or would they need your higher seclev access?
[18:11:38] <Bytram> Should work for anyone, but it is built on a scaffold of other tools I had built along the way to support automating the creating and moderating of comments on soylentnews
[18:11:57] <Bytram> OTOH, it *might* not be ALL that bad... lemme take a look
[18:15:06] <Bytram> janrinok: How about that... it's mostly implemented using grep and sed (it was hack-as-I-go-to-figure-it-out-and-never-got-updated). About the only external thing that cou,ld be a problem is getting a copy of HTMLtidy which acts as a front-end to do initial HTML cleanup and formatting.
[18:28:09] <Bytram> Oh, and it runs under windows as a cmd/batch script, using copies of sed and grep that I got online. If you want to stay with windows... you can get sed and grep from either: GnuWin32 or GNU on Windows (GoW)
[18:28:42] <Bytram> OTOH, it is so copiously commented, it might be easier to just port it to bash =)
[18:30:28] <Bytram> One other thing.... the batch program now sets environment variables with different formats of the current time... here's a sample of what it outputs atm:
[18:30:41] <Bytram> now_date=20200212
[18:30:41] <Bytram> now_dttm=20200212_133029
[18:30:41] <Bytram> now_iso8601=20200212T133029Z
[18:30:41] <Bytram> now_time=133029
[18:37:06] <janrinok> thanks for that - I'm Linux so sed and grep are always installed, but it might need some tweaking for bash
[20:20:57] -!- spiraldancing [spiraldancing!~spiraldan@Soylent/Staff/Editor/spiraldancing] has joined #editorial
[20:20:57] -!- mode/#editorial [+v spiraldancing] by Hephaestus
[20:24:01] <Bytram> janrinok: HTH! I'm sure there is a much better way to do it, but I was researching things and when I figured out what was where and how search worked, well so did my tool. So I resisted the temptation to fix it until it was broken!
[23:15:12] <Bytram> .
[23:15:17] <Bytram> whereto? https://go.theregister.co.uk
[23:15:18] <systemd> ^ 03Mobile World Congress now none of those things as 2020 industry megashow axed over coronavirus fears ( https://www.theregister.co.uk )
[23:15:18] <exec> └─ 13Mobile World Congress now none of those things as 2020 industry megashow axed over coronavirus fears • The Register
[23:15:52] -!- Dean [Dean!~68f6df09@104.246.izp.y] has joined #editorial
[23:16:04] <Bytram> whereto? http://feedproxy.google.com
[23:16:05] <systemd> ^ 03With MWC 2020 cancelled, most new Android phones face a tough debut ( https://www.cnet.com )
[23:28:52] -!- Dean [Dean!~68f6df09@104.246.izp.y] has parted #editorial
[23:39:18] <Bytram> =submit https://www.theregister.co.uk
[23:39:19] <systemd> Submitting "Mobile World Congress now none of those things as 2020 industry megashow axed over coronavirus fears"...
[23:39:20] <exec> └─ 13Mobile World Congress now none of those things as 2020 industry megashow axed over coronavirus fears • The Register
[23:39:41] <systemd> ✓ Sub-ccess! "03Mobile World Congress Now None of Those Things as 2020 Industry Megashow Axed Over Coronavirus Fears" (15 paragraphs) -> https://soylentnews.org
[23:39:50] <Bytram> =submit https://www.cnet.com
[23:39:52] <systemd> Submitting "With MWC 2020 canceled, most new Android phones face a tough debut"...
[23:39:52] <exec> └─ 13Page Not Found (404) - CNET
[23:40:14] <systemd> ✓ Sub-ccess! "03With MWC 2020 Canceled, Most New Android Phones Face a Tough Debut" (30 paragraphs) -> https://soylentnews.org
[23:42:01] <Bytram> .
[23:42:05] <Bytram> whereto? https://arstechnica.com
[23:42:07] <systemd> ^ 03Andy Rubin’s smartphone startup, Essential, is dead ( https://arstechnica.com )
[23:42:07] <exec> └─ 13Andy Rubin’s smartphone startup, Essential, is dead | Ars Technica
[23:42:22] <Bytram> ~arthur https://arstechnica.com
[23:42:24] <exec> └─ 13Andy Rubin’s smartphone startup, Essential, is dead | Ars Technica
[23:42:26] <exec> 971 stories loaded
[23:42:26] <exec> attempting to submit story: "Andy Rubin’s smartphone startup, Essential, is dead"
[23:42:56] <exec> submission successful - https://soylentnews.org
[23:43:02] <exec> 970 stories loaded
[23:43:04] <exec> *** wiki: edit error
[23:43:14] <chromas> I guess it wasn't that essential