Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2017-02-21

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:07 autarch1 joined #metacpan
01:31 Tempesta_ joined #metacpan
01:34 rsrchboy joined #metacpan
03:14 oalders autarch1 : my $rel = $mc->release( { name => 'MooseX-Getopt-0.71' } )
03:15 oalders when in doubt, i just check the api for what the available fields are https://fastapi.metacpan.org/v1/release/MooseX-Getopt
03:15 oalders you could also do distribution + version_numified, but name seems easier
03:28 autarch1 oalders: why doesn't $mc->release('MooseX-Getopt0.71') work then?
03:40 oalders autarch1 i _think_ what happens in that case is that it tries to fetch https://fastapi.metacpan.org/v1/release/MooseX-Getopt-0.71
03:40 oalders and that doesn't exist
03:41 oalders since the versioned url is at https://fastapi.metacpan.org/v1/release/DROLSKY/MooseX-Getopt-0.70
03:41 oalders https://metacpan.org/source/MICKEY/MetaCPAN-Client-2.005000/lib/MetaCPAN/Client.pm#L211
03:42 autarch1 ah, I see
03:42 autarch1 makes sense
07:36 nakiro joined #metacpan
08:58 Relequestual joined #metacpan
09:03 edward joined #metacpan
09:09 BooK joined #metacpan
09:53 neilb joined #metacpan
12:43 Relequestual joined #metacpan
13:52 nakiro joined #metacpan
13:52 nakiro joined #metacpan
14:10 Guest69 joined #metacpan
14:39 carandraug joined #metacpan
14:43 neilb joined #metacpan
14:47 Guest69 joined #metacpan
15:05 carandraug left #metacpan
16:03 Guest69_ joined #metacpan
16:39 autarch1 joined #metacpan
17:15 ilmari several perlsecret operators have their synopses rendered blank
17:15 ilmari e.g. https://metacpan.org/pod/perlsecret#Bang-bang
17:21 Guest69 joined #metacpan
17:26 haarg ilmari: https://github.com/metacpan/metacpan-web/issues/1228
17:28 ilmari haarg: aah
18:45 [SoQ]Forseti joined #metacpan
18:46 ranguard jberger: API and UI are completly seperate, so you can build your own UI (or app) on top of MC's api - though that's more a technical thing than for users
18:48 jberger ranguard etc al. yes I know the differences
18:48 jberger the thing is there isn't a good list of the differences that users can see
18:48 jberger the thing went like this: user A linked to a module on twitter to sco, user B replied and asked user A to link at metacpan
18:49 ranguard ahh
18:49 jberger user A didn't have a strong opinion and has always used sco
18:49 jberger and went to look for "why metacpan is better for me than sco" and couldn't find it
18:49 jberger btw, you know both people
18:50 jberger I was kinda shocked that not all well known perl people are aware of why metacpan is better, but if that is true then certainly others are in the same spot
18:50 ranguard heh https://perlhacks.com/2013/01/give-me-metacpan/ - " Isn’t it obvious that MetaCPAN is better? "
18:50 jberger also, "because it is open source" made absolutely zero effect on this person
18:50 preaction i mean, we are right here talking and ... _not_ coming up with reasons either :p
18:50 ranguard well, actually... no
18:51 ranguard lots of techincal reasons, but day to day usage.. not so much clear cut...
18:51 preaction do they boil down to "stability"? because that's totally a reason
18:51 ranguard we've got bells a whistles (data intergrations), and some nice rendering (pod and source code)
18:52 preaction also, i gave my reasons as: more readily-available metadata (on the sidebar instead of in some random other page), and easier navigation of the contents of the dist itself
18:52 ranguard but at the end of the say it's still just a search engine on the same set of data
18:54 ranguard what MC needs is to have the BEST (for what ever value) search results and then get SEO (ultimatly seeing if s.c.o will redirect to us) - that's the 'win' :)
18:54 preaction s.c.o could tank its own SEO (and apply that to MC) if it wanted, without redirecting at all
18:55 preaction <link rel="canonical" href="http://metacpan.org/..." />
18:55 ranguard preaction: oh yea, nice...
18:56 ranguard we just need these other steps first :)
19:26 perigrin preaction: ish, some of S.C.O's SEO comes from the C.O
19:27 perigrin metacpan.org would potentially need to 301 to meta.cpan.org to inherit that too
19:27 perigrin I think.
19:28 preaction afaik rel="canonical" is basically saying "take my score and apply it over to this page instead"
19:28 perigrin I'm not 100% sure that clean because people.
19:28 perigrin I know who to ask though
19:32 perigrin preaction: the advantage of spending four years working for an SEO tools company, I know a few professional SEOs to ask :)
19:33 neilb joined #metacpan
19:38 perigrin preaction: so Cyrus says via twitter 85-100% of the PR will transfer ... so I think there are complications but it' the best choice short of a 301
20:30 autarch1 joined #metacpan
21:37 autarch1 joined #metacpan
23:56 autarch1 joined #metacpan

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary