Outreachy and Rails Girls Summer of Code

Outreachy and Rails Girls Summer of Code

Had a productive discussion today about Outreachy and RSoC with the newcomers. Since the deadlines are at the end of this month we’re going to try and make this a regular/daily thing until the end of February.

Come say hi!

Reddit – Is that a puppet account?

I can imagine this being a handy tool for mods of subreddits. Find blacklisted users parading under a new account. Unlike Twitter or Facebook, finding the similarity between users in Reddit is a bit harder. From the official Reddit API, the data we have to work with is (the ones that look promising anyway):

  • GET /api/v1/user/username/trophies
  • GET /user/username/about
  • GET /user/username/where
    • → /user/username/submitted
      → /user/username/comments
      → /user/username/upvoted
      → /user/username/downvoted
      → /user/username/hidden (not accessible?)
      → /user/username/saved (not accessible?)
      → /user/username/gilded
  • GET /api/multi/user/username

A few assumptions and possible features about puppets:

  • Age – They’re new – the account is barely a few days old. Not a very good indicator though in my opinion. Users could have been using the alt account for a long time. This is a better feature for detecting trolls.
  • Karma – A lot of controversial posts/links, again a better indicator for trolls. I would rarely expect the Karma for two users to match unless they’ve been equally active.
  • Activity – Time of submissions of posts and links would be a good way to find out a users time zone. Days when they post, could reveal posting habits.
  • Links they’ve submitted – find similar interests.
  • Upvoted and downvoted content – again similar interests
  • Subs they post in – similar interests

And finally their literary style or fingerprint. This could include emojis and emoticons.

Breaking up the problem:

The individual problems I see are:

  • Similar user interests
  • Find the time zone of a user
  • Troll detector
  • Literary style of users

I’ll start with literary fingerprints for my next blog post in this series.

Week 3

I’ve never written tests for any of my code.

Though I did write some for a class I had, a few semesters back with JUnit. But I wasn’t planning on becoming a tester so I didn’t see the point of digging deeper back then.

I spent the weekend reading up on nose, testr, pytests, mock etc. part of the blueprint requires me to write unit tests and integration tests; so now would be as good a time as any to really learn about it. I won’t try to squeeze in everything in this post, so maybe a series and I won’t be covering everything there is to testing, just the stuff I think is relevant to get things done. One huge benefit (from a non-tester’s POV) I see for writing tests for the code is that you can figure bits which could be made reusable. And reusable code = less typing for me.

Backups on Trove Part 1

Week 1-2 OPW 2015

Late blog post (already 2 weeks into the program) but better late than never.

I got in :D !

Huge thanks to my mentor Iccha Sethi and the rest of the OpenStack community for helping out with the bug fixes! I’ll be working on a blueprint (in review) to help users retrieve log files from a DB instance for the next 3 2 months.

Before the start of the internship, the first task assigned to me by Iccha was to read up on the architecture of Trove. YouTube has a good number of helpful videos on it.

She gave a rundown on the code flow for the creation of a DB instance and gave some pointers on how to track the calls made on various modules using logs. I’ll do a blog post on that soon and another one on debuggers.

Merry Christmas!

© 2019 Anna Philips

Theme by Anders NorénUp ↑