05:11 <Snader_LB> hi all

05:14 <havenwood> Snader_LB: hi

05:14 <Snader_LB> topic could use an update; is there anyone that can update it?

05:15 <Snader_LB> current topic: http://blog.rubygems.org/2017/11/03/2.7.1-released.html - Latest status: http://twitter.com/rubygems_status and http://status.rubygems.org

05:17 <Snader_LB> proposed new topic:

05:17 <Snader_LB> https://rubygems.org/ | https://blog.rubygems.org/2019/03/05/3.0.3-released.html | Latest status: https://twitter.com/rubygems_status and https://status.rubygems.org/

05:19 <Snader_LB> on a different note: anyone here with edit permissions for <https://guides.rubygems.org/> / <https://github.com/rubygems/guides>?

05:21 <havenwood> Snader_LB: I can't edit the topic.

05:21 <havenwood> Snader_LB: Please open a PR with suggested improvments!

05:33 <Snader_LB> allow me to just note it here FWIW, it's minor but perhaps someone will pick it up

05:36 <Snader_LB> <https://guides.rubygems.org/security/> gives "gem cert --add <(curl -Ls https://raw.github.com/metricfu/metric_fu/master/certs/bf4.pem)" as a command instruction, but that syntax does not work in every shell

05:37 <Snader_LB> that might confuse readers

05:42 <Snader_LB> more portable (and better readable) would be: "curl ... | gem ..."

05:48 <Snader_LB> (that'd be in <https://github.com/rubygems/guides/blob/gh-pages/security.md>)

05:53 <Snader_LB> at least if that's what's meant

07:12 <Snader_LB> hm; no, that's not what's meant

07:20 <Snader_LB> in that case i wonder how this works

07:22 <Snader_LB> aiui, the output of the command in "<(...)" is taken as a file name, and that file name is given as an argument to the command standing before the "<(...)" ("gem cert --add", in this case)

07:40 <Snader_LB> no, not the output; the FIFO file name, which contains the output

07:40 <Snader_LB> got it

07:41 <Snader_LB> still, it won't work in any shell, e.g., dash(1) does not support it, which is /bin/sh on Debian based systems

07:53 <Snader_LB> so in that sense, it might still be better to split the command in two commands: one for downloading the file to a temporary file, and one for importing that file using "gem cert --add <file>"

07:54 <Snader_LB> (and the real question would be, why gem(1) can't read such file from standard input)

08:10 <Snader_LB> ok, thanks