I have two ideas for implementing this: - either as part of the planned killfile - as an enhancement of the Default View logic
The pause button looks like it could be implemented as an interface to the killfile system, but more convenient, and extended to have the option to hide for only a certain amount of time. One thing, I'm not sure whether it is a pro or a con: This would hide comments in entries, and I think would also hide their entries in communities you have in common. If what you want instead is to pause entries from their personal journal, and only their personal journal, keeping their comments visible, as well as any entries in common communities, I think integrating it with the Default View logic would be better. It could be implemented so that it: 1. updates your "Default View" with one click - does not seem that complicated 2. offers the option to unpause automatically after x-amount of time. Stored in a separate table? - I think not extremely complicated, but not sure about the performance hit of needing to check every $period_of_time for upcoming people to unpause 3. some kind of page where you can list all the people you have paused/when they were paused/when the pause expires/option to manually unpause - not that complicated if #2 is done right 4. some kind of indication, when editing your Default View manually, that $user is not on the list because they're paused? - possibly not that important; you can go to #3 for that if needed Advantages of integrating the pause button with an existing system, either Default View or planned killfile, is that it uses existing logic, so less possibility of introducing new bugs. Also, with the default view, it only affects your friends page, and only personal journal entries (not community entries -- though undecided if this is an advantage or not); only one lookup "what users should show up in Default View?" versus "which users are in Default View + which users are paused?"), which LJ already does when building the friends page! So the only additional effort is a process running in the background which automatically updates your default view when the pause period expires. Fiddly details/edge cases which probably need to be kept in mind if pause is implemented as DV: - what if you remove the user from your readlist after they've been put on the pause list? When it is time to unpause, should they be added back? - what if you have your friends group management page open, the process unpauses someone by adding them to your default view, but you still see and save the old list of the default view. So the user is (permanently) removed from your default view, at least until you notice they're not there when they should have been unpaused - what if you're in the middle of your friends page, when someone is unpaused, causing you to accidentally skip some entries which are pushed back (probably unavoidable! but something to keep in mind?) - how about mobile view? I do not think that any of these are deal breakers; just need to be handled properly :) On Wed, Aug 27, 2008 at 6:45 AM, Jenett <[EMAIL PROTECTED]> wrote: > Don't know who else reads Merlin Mann's 43 Folders blog, but there's an > interesting new entry there that proposes a way to 'pause' reading someone's > stuff on your friends page (or whatever other term is used) invisibly to > them. > > http://www.43folders.com/2008/08/26/pause-button > > In other words, if you just need to take a break from their stuff for a > little, you'd push the little 'pause' link, and it'd just not load that > person's stuff for you. You could then unpause later (this also has a > benefit that you wouldn't need to reset custom filters, colors, etc. that > were related to that person on your own journal.) > > I suspect that in practice there are all sorts of good reasons this is > really a problem to do (the hit on the database would be very complicated), > but I thought it was worth mentioning for discussion. (Personally, I can see > both pros and cons and don't generally find myself in situations where this > would be partiuclarly helpful. Consider this a 'throwing out because it > specifically mentions LJ functionality by name') > > Jenett > > _______________________________________________ > dw-discuss mailing list > [email protected] > http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss > _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
