Have had a busy week! My foot's really starting to heal now so I've been walking about, enjoying movemental freedom and getting things done I couldn't before
I've also worked on instruments: added the reyong (INST-709), the calung (INST-698) (especially this was difficult, still not completely happy about it, see INST-832)
also started some seecrit work ♪😽
Finally summer has done a little comeback here so therefore I'm at Hovedøya right now :D
Last week I continued helping akhilesh along to complete the API project, as he described.
Freso
(People still up: Freso, spellew, aidanlw17, Cyna, amCap1712(?) – anyone else, please let me know explicitly ASAP.)
Mr_Monkey
I also started figuring out how to add elasticsearch to travis for CI tests of the search endpoints.
And that's it for me !
spellew: go !
Freso
Or maybe aidanlw17?
aidanlw17
Hi all!
I can go
Being the last week of GSoC, I spent most of my time cleaning things up and making sure everything was working well, across all aspects of the similarity pipeline.
Did some final testing and got some pesky things worked out.
Also wrote my evaluation and blog post
I’m happy with what we achieved and I can’t wait to see where it goes in the future.
KassOtsimine
:D
aidanlw17
Pretty sad that the summer is ending :( thanks to everyone for being part of this great community!
I’m honoured to have been part of it and I plan to stick around :)
Fin
Cyna, go?
Cyna
Hi
This week was most productive for me. I finally converted all the MB entity's editforms and added previews to them
Freso
(Only myself left on the list—and maybe spellew and/or amCap1712 if they show up. Last call for anyone else who may want to go.)
Cyna
Most of the time I spent on completing the gsoc project which is mostly now complete. I couldn't add test cases which I'll be starting to work on once the main code written during the gsoc period is committed
and all the issues with them are fixed
Thanks for helping me during the gsoc period bitmap, couldn't have done it without you :)
Fin !
Freso: wanna go next ?
Freso
Well, not really any other options currently. :p
But sure. Thanks. :)
(amCap1712, spellew: final ping; otherwise I’ll move on once I’m done with my review.)
🙋
KassOtsimine
..
Freso
So, by end of last week I notably tried to organise all y’all GSoC students’ blog posts.
I also looked into an issue with Jira, but unfortunately couldn’t find resolve for it. :(
KassOtsimine
was that he label thing?
Freso
Spent some time trying to get an overview of all the reports that came in over last weekend.
And other than that, trying to catch up and be around/about etc.
fin.
KassOtsimine: Yes.
No word from spellew or amCap1712.
So that’s it for reviews!
One more item on today’s agenda:
Freso: Options for blocking personae non gratae
So I was hoping to have this up for discussion at the summit, but maybe it’s great to start the discussion/thinking now and we may be able to have some more fruitful discussion/planning come summit time.
KassOtsimine
...
(also not everyone can Make the summit)
Freso
zas, bitmap, yvanzo, reosarevok: This will likely be mostly oriented towards technical "solutions", so please be around. :)
zas
I do
Freso
KassOtsimine: The discussion is mostly between me and MBS devs/sysadmins (ie., the four people I just pinged).
The problem currently is…
KassOtsimine
jeez
Freso
Sometimes we have people coming in to MB acting in bad faith.
And they get reported—sometimes massively so—and I will eventually either disable their editing/voting rights or just straight up delete their account.
But they are free to immediately turn around and make a new account. In fact, many people where I’ve disabled their editing/voting rights delete their own accounts and create new ones and continue on with their behaviour.
We currently have no way to block e‐mail addresses or IP address (ranges), no way to find editors via e‐mail, or any way to see what IP address a given editor comes from.
Would these (or some of these) be feasible to implement?
Any other ideas for tools that we might be able to implement?
KassOtsimine
i don't see a problem this for user admin like freso
bitmap
we have a way to block ips on the gateway, don't we? though I don't think we'd want to block them permanently
zas
We have, but it's not easy to manage atm
Freso
bitmap: Yeah, but we can’t associate editors with IPs.
So we won’t know which IPs to block to begin with.
rdswift
Throw-away email addresses are easy to obtain, and you can't always rely on an ip address (spoofing, vpn, etc.)
zas
To prevent creation of new accounts we could start by blocking emails they previously used
Freso
(And yeah, I agree that we won’t want the blocks to be permanent.)
bitmap
but yes, we'll need to show editor ips to admins in mbs
Freso
rdswift: Yes, but we can make it harder.
bitmap
in fact I think there is a ticket for that
yvanzo
We can associate editors with IPs in Sentry.
KassOtsimine
instead of blocking emails (that will mean they realise they just can use a throwaway
bitmap
if they happen to trigger an error that gets posted to sentry, I guess
KassOtsimine
notify admin when new user uses email on "blacklist"
Freso
rdswift: Right now you can registers 100’s of accounts with a single e‐mail address. (Which in general is fine, but we also can’t search via the website interface for accounts by e‐mail address, so I can’t find all the addresses with the same mail.)
rdswift
Freso, I agree it will help. Just won't catch all of them.
Freso
Anyway, I’m not sure I necessarily want a specific actionable path forward—but I would love if y’all could think about this and then maybe we can talk about it in a week or two and then again at the summit?
yvanzo
bitmap: yes, we can make that happen when needed.
Freso
*actionable path forward right now/today
yvanzo
but zas’ suggestion seems simpler and less efforts to implement.
rdswift
Sounds like a great first step.
bitmap
showing the ips in mbs doesn't seem too hard
Freso
But since I can’t search for e‐mail address pattern, I can’t see if there are more sleeper accounts matching this pattern.
Being able to see different accounts associated with a given IP would also be a great help.