[07:59:02] Hi, where can I check mediawiki.org's configration settings? I need to check the value of $wgRSSAllowedFeeds [08:00:45] To fix this: Extension:RSS -- Error: "https://blog.wikimedia.org/c/technology/feed/" is not in the whitelist of allowed feeds. https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview [08:48:54] qgil, hi [08:49:00] qgil, you want operations/mediawiki-config [08:49:16] ah, thanks Krenair [08:49:56] alex@alex-laptop:~$ ssh terbium -t mwscript eval.php mediawikiwiki [08:49:56] > var_dump( $wgRSSAllowedFeeds ); [08:49:56] NULL [08:50:14] that would explain ;) [08:50:47] There is a $wgRSSUrlWhitelist [08:51:31] Which includes https://blog.wikimedia.org/feed/ but not https://blog.wikimedia.org/c/technology/feed/ [08:51:55] That explains even more [08:52:09] So this is not handled from a wiki page but from source code directly? [08:52:54] from our config directly [08:53:30] Hre? https://phabricator.wikimedia.org/diffusion/OMWC/browse/master/wmf-config/FeaturedFeedsWMF.php [08:53:37] no [08:53:46] CommonSettings/InitialiseSettings [08:54:53] aha https://phabricator.wikimedia.org/diffusion/OMWC/browse/master/wmf-config/InitialiseSettings.php;d0091d1791f2a75ff486af3782633f5a90423bfc$12812 [08:56:08] Thank you Krenair [08:56:14] https://www.mediawiki.org/w/index.php?title=MediaWiki/Homepage_redesign/Preview&diff=next&oldid=1843517 [08:56:25] okay, so http://blog.wikimedia.org/feed/ will probably no longer work and I should unwhitelist that [08:56:33] needs to be https, which we already whitelisted [08:57:09] If you can add the technology feed, that would be great. It's been a while since my last patch sent to gerrit [08:57:30] Hmmm [08:57:40] I think don't you should be using that feed on that page [08:58:12] Fair. :) It's a discussion I want to have about the scope of mediawiki.org and therefore of its homepage. :) [08:58:24] We can wait [08:59:19] It's for the MediaWiki.org main page, therefore needs to be about MediaWiki announcements, not Wikimedia-specific stuff [08:59:44] My opinion is that MediaWiki announcements should also go to the Wikimedia blog / tech [09:00:03] ... and that mediawiki.org is not only about MediaWiki [09:00:13] Most of it is release announcements [09:00:21] Wikimedia does not really use the release branches of MediaWiki [09:00:37] No, please read the project scope. [09:00:41] Details [09:01:10] (the projewct scope is not details) [09:01:17] I meant your previous sentence [09:01:19] I was about to say :) [09:02:20] My idea fits in https://www.mediawiki.org/wiki/Project:About [09:02:20] Okay, so if you did copy release announcements to the technology blog [09:02:37] Some stuff on https://blog.wikimedia.org/c/technology/ still probably shouldn't show up on the mediawiki.org home page [09:02:58] then maybe should not use the "technology" tag, something that we can agree with Comms [09:03:34] In short, I think that this equation is benefitial for everybody: Wikimedia + Technology = mediawiki.org [09:03:40] no [09:03:49] Wikimedia + Technology = wikitech.wikimedia.org [09:03:57] that is a website that nobody knows or reads [09:04:01] MediaWiki things = mediawiki.org [09:04:23] and most of those news are mostly interesting for people interested in betting their content on MediaWiki [09:04:49] I think that strictly correct vision is not helping MediaWiki [09:06:31] Well I think your strictly incorrect idea hurts the idea of MediaWiki as a generic open source software project which is not specific to one organisation (Wikimedia). [09:07:33] We can change the feed to a planet then. I'm just looking for the most interesting news about what people is doing with MediaWiki and related technologies. [09:07:43] "News" being only new MediaWiki releases is not helping [09:08:32] https://blog.wikimedia.org/c/technology/ is the closest feed to that idea that I'm aware today [09:08:45] It is a blog open to contributions [09:08:53] I agree we shou;d add more stuff to news than just releases [09:09:09] The news posted there are interesting and well written [09:09:25] "We should" has been an idea for years, and it is not working. [09:10:07] Just stating, as someone who has updated Template:News a lot in the past -- and was the only one, basically. [09:10:20] (apart from the release guys) [09:10:30] "Wikimedia Foundation hosts lively panel on copyright", "My life as an autistic Wikipedian", "Get the latest Wikipedia updates easily with IFTTT", "Get email updates from the Wikimedia blog" - sorry, these are good posts for the Wikimedia blog, but don't belong on the mediawiki.org main page [09:11:28] Yes, and they probably could live without the "technology" tag. [09:12:22] The ContentTranslation stuff I'm more open to as they are an actual MediaWiki extension [09:12:26] Same with Wikidata [09:12:36] Events stuff is fine [09:13:06] As said, this can be solved with a conversation with Comms about criteria to use the technology tag [09:14:00] Okay [09:14:06] the posts you mention have a very generous distribution of categories and tags, they will survive without the "technology" category [09:14:26] Krenair, I'll create a task right now. :) [09:15:28] Krenair, in fact, now I remember https://phabricator.wikimedia.org/T86437 [09:15:30] Once you get that sorted out and get the agreement of the MediaWiki.org community in the discussion about the home page, file a #Wikimedia-Site-requests ticket and it can be whitelisted for RSS inclusion [09:15:39] ok [09:15:44] thanks! [09:49:52] Krenair, task created: https://phabricator.wikimedia.org/T108926 [09:55:05] thanks [10:54:45] any recent problems related to JS scripts not running? [10:55:07] my personal JS seems to execute for pages in the User NS but not in the Main NS [10:57:25] anything in console? [10:57:31] actually, it runs in all NS except MAIN [10:57:36] not, nothing unusual [10:58:29] just the usual: [10:58:30] ReferenceError: sajax_init_object is not defined load.php:6:684 "Exception in store-localstorage-update:" load.php:178:1 "NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached" [10:59:56] actually, "ReferenceError: sajax_init_object is not defined load.php:6:684" doesn't appear in every NS [11:07:53] was this sajax_init_object removed in the last update of 11th Aug? [11:19:03] yes, it has been removed [12:14:34] in obj['query']['pages'], how can I access the first page if I don't know its Id? [12:14:40] (in a JSON response) [12:14:59] i.e. "36198":{"pageid":36198,"ns":0,"title":"akatuntu","contentmodel":"wikitext","pagelanguage":"pt","touched":"2014-05-20T04:25:08Z","lastrevid":1367467,"length":129} [12:15:12] malafaya: Add indexpageids to the query and you'll get a list of page ids [12:17:24] i was hoping i could do somehting like pages[0] but it doesnt work [12:17:40] only page['36198'] seems to work [12:17:52] hoo is that the only way? [12:18:27] In JavaScript, yes [12:18:32] you can also loop over it [12:18:34] :( ok thanks [12:18:39] loop how? [12:18:55] for(page in pages) doesnt seem to yield the expected result [12:19:08] i get text [12:19:22] hoo [12:19:32] That should work [12:19:49] in the example above, i'm getting page='36198' [12:20:07] not an object [12:22:10] so look up obj['query']['pages'][page] [12:22:43] Krenair, problem is i don't know page [12:22:50] i want to iterate them [12:23:27] for ( page in obj['query']['pages'] ) { console.log( obj['query']['pages'][page] ); } [12:25:55] that does work... how come? what's the difference [12:26:40] pages = obj['query']['pages']; for(page in pages) { alert(page); } [12:27:33] do you have basic javascript programming skills? [12:28:29] basic, yes, but just that [12:29:53] are you writing a gadget for use by readers of wikimedia sites? [12:30:45] no, nothing so fancy. i'm just changing common.js because of deprecated functions [12:31:02] ok [12:31:04] in this casa, from sajax_* to JSON [12:31:19] great [12:31:46] anyway, is there anything wrong with the alternative code i posted above? is there any basic mistake? [12:31:56] seems the same to me [12:32:01] Nothing wrong with it [12:32:06] Your code will print the object keys [12:32:12] I.e. the page IDs [12:32:33] That might not be what you want to do... [12:33:25] i was hoping page would be an object... instead i get a string [12:33:35] It's not going to be an objecgt. [12:33:37] object* [12:33:39] basic JS i guess [12:33:44] indeed [12:34:52] ok, so i get the key and then i use it to get the appropriate value. that's the only way [12:35:52] You don't have to use for [12:36:47] $.each( obj['query']['pages'], function () { console.log( this ); } ); [12:42:45] thank you for your patience Krenair [12:42:52] i got it working [16:03:02] is it possible to change the rate of collapsation/expansion in mw-collapsible elements?