AZJazzyJ's dashboard

My bad, I thought Get Satisfaction would allow links. The URL for the tutorial is http://plurkskins.com/2009/01/modifyi...

/* Center Friend Icons */
.friend_holder table {
margin-left: auto;
margin-right: auto;
}

.friend_holder td {
padding: 5px 6px 5px 6px;
}
/* End Center Friend Icons */

/* Change Friends/Fans Picture Size */
.friend_holder .user_link, .friend_holder .user_link img {
width: 25px !important;
height: 25px !important;
}
/* End Change Friends/Fans Picture Size */

/* Change Personal Avatar Picture Size */
#profile_pic {
width: 87px;
height: 87px;
}

#profile_pic:hover {
width: 195px;
height: 195px;
}
/* End Change Personal Avatar Picture Size */

I have written a tutorial that explains the code and what it does if that helps.

thanks Amir. It looks like it may have taken a while to propagate to the servers but is now working for me. I can reload the page, log off, and visit another profile and when I return the system remembers the state of sound notifications.

Thanks for the quick response and action. And thanks for adding the "f" in shift-reload your static files, I wasn't sure what to do without the "f" in there. :-)

thanks Amir. It's a nice feature it just gets in the way if you are trying to concentrate. Having it settable in the profile would give the user an opportunity to turn it on or off depending on the circumstances or the surroundings.

I appreciate your quick response and commitment to looking for a solution.

thanks Alvin, it's still messed up on my end which means I probably have a conflict with a Firefox add-in. If I find a solution I'll add it here in case anyone else may have a similar problem.

this is due to the anti-aliases on the existing graphics. I've downloaded the emoticons and cleaned up the edges saving them without anti-alias in gif format. I've also saved them in .png format for a much cleaner look. I have a zip file with the cleaned graphics. Can Plurk use these new graphics?

I thought I read that the back to the oldest was the cause of the messages overlapping on the timeline which is why they switched back to most current. I would think back to oldest would be relatively trivial if the data has a date-userID index. (Of course that is just a wild guess on my part.) – AZJazzyJ, on September 13, 2008 18:53

People will post for attention regardless of whether it increases or decreases a number. Not seeing a number will not make the "noise" go away. Posting to some adds value to their existence regardless of whether you think the message helps the discussion or not. I don't understand the whole "opt-out" concept. If that is implemented then Plurk would need to now account for 2 groups of people, those "in" and those "out". This additional logic increases complexity as the app would need to reach decision points and check to see if you are "playing the game". I would think adding this logic could cause scalability issues. Karma is not hurting anything. If it calculates and you don't like how it calculates then don't look at it. I'm not sure I understand your analogy of the water. How is Karma filling your house in water? A more appropriate analogy is buying a house that has a telephone trunk box in your front yard. You want to use the phone so you know that the box is necessary you just don't want to stare at the box out your front window. You can therefore plant a bush between you and the box. You see a bush and landscaping while the box remains for everyone to use. I am not sure how much easier we should require this to be. The code is there, it's simply a cut and paste. Why make the application be changed? Wouldn't we rather have the developers working on other aspects of the system? Coding resources are finite, they can work on this or something else. I would prefer them to spend their time on something else. – AZJazzyJ, on September 10, 2008 16:24

likes the idea of Karma and thinks it is valid. I find it almost comical that this is an issue at all. Plurk provides you with an ability to hide it from view using CSS. Numerous sites have provided the code necessary to do this so that all the user has to do is cut and paste the code into their profile making is extremely easy to eliminate seeing it yet there continues to be discussions and complaints about it. The CSS gives you the ability to opt-out of seeing your Karma and if you don't care about it that would be the appropriate thing to do. Why make the application more complex by introducing this? I think we have all the tools necessary for the user to choose whether to see Karma or not without having to make any changes to Plurk itself.