karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
Time to get this rolling again!

The medium that I've chosen for scheduling office hours is a site called Sign Up Genius. It is pretty easy to use in my experience, and all of my kids' teachers use it for conferences, parties and such. You don't have to have an account on the site to sign up for time slots, which is pretty great - just give them your email address. They will send you a confirmation and a reminder, and nothing else. But if for whatever reason you have trouble claiming a time slot using that site, you can also comment here and I can take care of it for you.

I am only doing signups for a week at a time, because that's about how far in advance I can be fairly confident of my availability. Each week will start on Friday, and I'll post the signups for the following week on Tuesday or Wednesday.

Each signup slot is scheduled to run 90 minutes, but since they're non-adjacent, it's OK if we need to go longer. Anything Dreamwidth-related is fair game: we can talk about code you're writing, code you want to write but don't know how to proceed, code someone else wrote, or things that don't involve code at all (I hear such things exist). My only request is that you don't take more than two slots in a single week, to make sure there is enough of my time to go around. Of course, you're still welcome to catch me on IRC at other times if I seem to be around, and PMs are open 24/7. :)

Here's the link for my available meeting times for the seven-day period starting July 1:

http://www.signupgenius.com/go/4090D45AEAD2DAAF94-office2

Date: 2016-06-29 02:41 am (UTC)
batrachian: Dom (from the webcomic Megatokyo) talking on a phone (Dom)
From: [personal profile] batrachian
I wasn't sure how computationally expensive the datestamp bit was (though now that I think it through, i guess it's just one simple less-than comparison, isn't it). Still not sure that it'd do the Right Thing for entries with multiple pages of comments, though. e.g:

  • Comment #65 posted at 10:00 - ends up on page 2

  • User loads entry at 10:05, views page 1. "newness" data updated to 10:05 after loading page.

  • User clicks to page 2 of comments at 10:10. Comment #65, being older than the stored value, is not marked as new

Discussion in the -suggestions entry included commentary about including newly-unscreened comments in this spec, and I think that it's entirely reasonable to do so - if the user hasn't seen the comment because it was screened, it might as well be new to them, and not marking because they "could have" seen it may cause more confusion.

Date: 2016-06-29 04:18 am (UTC)
kareila: (Default)
From: [personal profile] kareila
Those are some good points. My main concern with including unscreened comments is that I don't think we store a datestamp when a comment is unscreened, so the data simply isn't there to use. You might be able to work through the pagination problem by adding the datestamp to the page arguments, but then you'd have to discard it on a refresh...

It definitely sounds like a more detailed spec should be discussed and agreed upon before diving into the implementation.

Date: 2016-06-29 04:30 am (UTC)
batrachian: Dom (from the webcomic Megatokyo) talking on a phone (Dom)
From: [personal profile] batrachian
Seems like, yeah.

(this is, of course, why i wanted to talk to folks - of the bugs I grabbed before last year's OSB, the simple ones are all already done now. XD)

Profile

karzilla: a green fist above the word SMASH! (Default)
Karzilla, Destroyer of Bugs

November 2022

S M T W T F S
  12345
678910 1112
13141516171819
20212223242526
27282930   

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Feb. 17th, 2026 04:13 pm
Powered by Dreamwidth Studios