You're doing good work, zas (even if that didn't work yet)!
zas
well, i'm quite unhappy with this week, not very productive
reosarevok
Everybody knows Gandhi is always silence, silence and then nukes
zas
and now i'm fighting with exim, thx to Freso ;)
reosarevok
zas: you've been working not-very-part-time and hardcore for ages, you might as well have some less productive weeks too
To stop making us look bad
ruaok
lol
yes, thanks for working more than reosarevok. :-p
zas
lol
reosarevok
Hey, I'm over a million edits and all. That must count for something (?)
zas
Also i would like to welcome chrisskye
Freso
zas: :D
reosarevok
(even if only for declaring me insane)
zas
fin.
Freso
bitmap: :)
bitmap
hi
last week was less focused than normal, I mostly worked on random tickets
there was a problem with the caa-indexer crashing early in the week, which I deployed a fix for
and then documented parts of the indexer in syswiki
reosarevok
Yay docs
JonnyJD joined the channel
CallerNo6
+yay
bitmap
tried to figure out why dagon wasn't serving translated pages, but it ended up mysteriously fixing itself
(after restarting the service)
ruaok
wow, you passed drsaunde. congrats reosarevok, you're certifiable.
:)
bitmap
worked on MBS-8722, MBS-8730, and two cleanup PRs that don't have tickets
I also finished porting the link_entity macro to react, but I was waiting for an upstream PR I have to be merged
I may just add a workaround an submit it anyway
looks like that's all for me, fin
LordSputnik
sneaking in.... This week I've finished off the script for migrating our current schema, "v0", to our new and improved "v1" schema - with the exception of relationships between entities, which we're still working out. Also did some more work on moving the site to being independent of the web service, so we now have search implemented there as well. As part of that I've been improving the models in the
node.js ORM. Also have been approving GCI tasks, and we almost have our first style guideline approved (opatel99 + ariessa) (poke, Leftmost, check your mail), some annoying display bugs fixed (opatel99), and a whole suite of web service tests nearly done (stanislas).
fin :)
ruaok
did you manage to get any sleep, bitmap ?
my day has been challenging.
Freso wonders if opatel99, gcilou, stanislas or other GCI students want to chime in?
bitmap
yes, eventually I got a few hours in, heh
Freso
If so, you can go after Gentlecat.
Gentlecat: Go ;)
Gentlecat
hello 🙋
Freso
🙋
ruaok
bitmap: here is the best quote of the day, which also explains why I got hit so hard: "David Bowie’s death is a litmus test for weirdness. The misfits and freaks are devastated, the normals are, “Oh, too bad.""
Freso
... I'm a normal. D:
chirlu`
By that measure, I’m normal too …
chrisskye
I’m some sort of hybrid.
Freso hopes Gentlecat is typing a loong message and not just ran off...
Gentlecat
Last week I deployed new JS/CSS build system for AB, fixed some login issues there
Also merged some fixes for CB and tweaked layout a bit
Freso
("Ooh! Thread from a ball of yarn!")
zas
Damn i fall in misfits category....
Gentlecat
Helped alastairp a bit with fixing our wrapper for memcached
ruaok
zas: no surprise here.
Gentlecat
And took another look at the whole in-site communication/notifications thing
Freso
( reosarevok, chirlu`: How "long" do you think your topics will be? )
Freso: I couldn't say it better than LordSputnik :)
reosarevok
(probably not very)
Gentlecat
I'm starting to think that XMPP might actually be an overkill for what we need in the end
stanislas
Are the meetings over now ?
reosarevok
Nope, around the full hour probs
Gentlecat
And it will probably be easier to do something custom for ourselves, but I didn't write any of this down yet
bitmap
my comment on MBS-8721 seems relevant, if it's only used internally I'd tend to agree...
Gentlecat
Hopefully next week
Meanwhile, any comments on these tickets are welcome
fun.
ruaok
gah, less custom code please.
Gentlecat
I mean fin
ruaok
because what starts simple, inevitably turns into complex shizzle.
Freso
^
Gentlecat
ruaok: XMPP will require custom too
Freso
chirlu`: Go.
ruaok
less custom, I would think.
chirlu`
My week was rather slow.
I did fix a few tiny MBS tickets.
Freso
(Anyone who wants to go/I've missed, poke me, or we'll skip to topics once chirlu`'s fin'd.)
gcilou
poke
chirlu`
I also thought a bit about speed improvements for edit search and for opportunities to make use of new Pg features and opened a number of tickets.
Finally, some support issues on IRC or forums (e.g. data users had trouble with caching, David Bowie was undead for them).
fin
Freso
gcilou: Go.
gcilou
Here I go! This week I've done some pretty neat things, I finished adding the spotify play button to the review editor in CB, learning a ton the entire time from Gentlecat and others :) Also, I began and finished the MeB Intro to the Foundation and the projects video (On YouTube now!), and learned a lot from Freso, CallerNo6 and others helping on that one! So far, GCi has been awesome, and I'm very happy
We keep getting spammers creating users with links like "buy instagram followers" - but that's kinda ok because they don't affect the data
(the ones I see, because they post the links on Twitter, I just remove)
Freso
And report them to Twitter?
reosarevok
Yes, not that it's made any difference ever
Gentlecat
That seems like a waste of time
reosarevok
But this week we got one that also added an event with the spam link
And that's more worrying
Freso
I've seen Instagram being really good at removing spammers, but that's obv. not Twitter though.
reosarevok
I mostly would like people to think of what we can do to avoid this kind of thing
Freso
Did you make a ticket where we can collect thoughts/ideas?
ruaok
maybe have a keyword watcher that watches over edits?
chirlu`
I thought of checking new URLs against blacklists, but at least this particular URL wasn’t on the usual lists.
reosarevok
Obviously if people see them we can get rid of the offending entity / user, but if they're adding the stuff to the actual data, we'll be sending the spam forwards to customers and the like
ruaok
twitter and instgram are not terms that appear too much in actual music titles.
reosarevok
No, but they're linking to URLs
And they do appear in a lot of urls :p
Specimen joined the channel
"purchase" and "followers" in the same URL, not so much, but that's very specific to this one case
chirlu`
Have a report of “entities added in that last X time” for manual reviewing?
Because at the moment the only way to find these things is by looking through all edits.
ruaok
I wonder if we should upgrade our sign-up captcha to use the latest and greatest from Google.
zas
reosarevok: do you have examples of such account ?
Freso
(2 more minutes, then we're moving to chirlu`'s topic.)
reosarevok
zas: not at the moment, because I removed them. chirlu` might have been smarter and screenshotted it or something
zas
ok
chirlu`
Upgrading CAPTCHA sounds good in general, but I believe these particular spammers do it manually.
ruaok
yeah, I was afraid of that.
is upgrading the captcha a suitable task for GCI?
Freso
reosarevok: Make a ticket for collecting thoughts and ideas for how to handle this, and maybe we can talk about it again next week.
reosarevok
Ok
Freso
chirlu`: DR MBS-8451, go. :)
reosarevok
Is that MBS? OTHER?
ruaok notes that DR == Discussion Required
chirlu`
So, we clean up and standardize URLs.
ruaok
if chrisskye is still not bored to tears
Freso
reosarevok: I'd say MBS.
reosarevok
Ok
chrisskye
ummm....
Freso
ruaok: Decision, but good call :)
chirlu`
There are sites that support both http and https.
Up to now, we stored them as http, but presented it as scheme-less links on the site
Now Wikimedia switched to https-only, redirecting http requests.
And question is: Should we change all our Wikidata/Commons/(Wikipedia) URLs to https?
ruaok
is there a downside to doing that?
chirlu`
Or should we continue to store http, but always present them as https?
reosarevok
There are over half a million
Freso is very much on the HTTPS only and everywhere train, so would prefer to store https:// - but I'm not militant enough about to strongly object to storing http:// instead.