[00:34:51] <k-man>	 is it possible to make the simple search case insensitive?
[00:35:38] <legoktm>	 k-man: https://www.mediawiki.org/wiki/Extension:TitleKey
[00:37:19] <k-man>	 thanks legoktm 
[19:58:05] <Zoranzoki21>	 Hi, on Serbian Wikipedia number 0 is same as letter o. How I can change font for me from Georgia to Georgia Pro?
[19:58:47] <harmaahylje>	 in the browsers settings, I guess
[20:01:26] <bawolff>	 Zoranzoki21: In Special:MyPage/common.css:   * {font-face: "Georgia Pro" }
[20:01:33] <bawolff>	 or something like that
[20:01:38] <bawolff>	 Browser settings is also a good approach
[20:02:05] <bawolff>	 err, i mean
[20:02:12] <Zoranzoki21>	 bawolff: Thanks, I will try with editing of common.css
[20:02:13] <bawolff>	 * {font-family: "Georgia Pro" }
[20:02:38] <bawolff>	 I always get confused whether its font-family or font-face. Appearently font-family is correct
[20:05:22] <Zoranzoki21>	 bawolff: ok
[20:07:33] <Zoranzoki21>	 bawolff: Font of title is not changed. I cleaned cache memory
[20:11:44] <bawolff>	 Hmm, looks like * has a really low specificity
[20:11:56] <bawolff>	 * {font-family: "Georgia Pro" !important }
[20:12:03] <bawolff>	 Will force the font to be everywhere
[20:13:28] <Zoranzoki21>	 bawolff: Works. Thanks!
[22:07:52] <p_gimeno>	 API question... How can I make a series of recentchanges requests separated in time, without repeating or skipping changes?
[22:09:14] <Skizzerz>	 use the rcstart and rcend timestamps to constrain the start/end dates and make sure they don't overlap with previous requests?
[22:09:37] <Skizzerz>	 Otherwise you could request the entire range at once and just use the query continuation to page through the results
[22:11:10] <p_gimeno>	 Skizzerz: hm, constraining the end is something I didn't think of, but I still see a problem. My concern is clock desynchronization between client and server.
[22:11:42] <p_gimeno>	 Does the API have a "get current timestamp" function?
[22:11:51] <Skizzerz>	 what is your intended use case for this?
[22:12:12] <Skizzerz>	 (asking because the API might not be the way to go, depending on what you're trying to do)
[22:12:18] <p_gimeno>	 my intention is making a mirror of a wiki
[22:13:30] <Skizzerz>	 I assume you don't have server-level access to the original wiki
[22:13:33] <Skizzerz>	 ?
[22:14:10] <p_gimeno>	 that's right. And I don't want to go through the hoops of installing MW and all the extensions they have (including Semantic Wiki).
[22:15:16] <Skizzerz>	 so another alternative would be to subscribe to the recentchanges feed
[22:16:04] <p_gimeno>	 how would that work?
[22:16:40] <Skizzerz>	 which is the feedrecentchanges API (as opposed to the recentchanges API)
[22:16:59] <Skizzerz>	 as to how, you can use any software which lets you sub to an atom or rss feed
[22:17:33] <Skizzerz>	 although, I'm not sure it brings many advantages
[22:17:51] <Skizzerz>	 either way you need to track client-side the cutoff that you need to start requesting changes at
[22:18:19] <Skizzerz>	 (don't need to mess with timestamp synchronization, the client can just say "the last request I made was timestamp X, so next request will be X+1"
[22:18:55] <Skizzerz>	 the main advantage of a feed subscription is that you can plug in a feed library to handle that side of things for you, so your stuff only needs to worry about what happens as a result of getting a change notification
[22:21:29] <Skizzerz>	 in either case (base rc api or the feed api) you'd need to see what the most recent entry is to track as the timestamp to pick up from next time
[22:22:45] <p_gimeno>	 that would be a server-side one, if I understand you correctly, right?
[22:23:51] <p_gimeno>	 I have everything already set up with normal recentchanges, I just realized the sync problem. And I've just found rcprop=timestamp
[22:25:01] <p_gimeno>	 yeah, that will work, thank you!
[22:47:25] <p_gimeno>	 I've got it ready now, thanks again!