anotherjesse's profile

Default-avatar

anotherjesse

  1. 6
  2. 13
  3. 47
Open ideas
  1. 4 votes
    3
  2. 6 votes
    2
  3. 4 votes
    2
  4. 68 votes
    2
  5. 8 votes
    1
Completed ideas
  1. 3 votes
    3
Comments
  1. Renamed to watched topics. I'm going to close this and create a bug to improve the feature (privacy and better UI - topics not posts)

  2. Johan said: "Showing proper error messages is of course always a good idea, though. :-) "Scripts uploaded to userscripts.org must be saved as unicode encoded as utf-8; this script was not legal utf-8. If you do not know how to do that, we suggest you paste the script contents into the text area instead to let your browser do the work for you." for instance."

  3. Perhaps everyone can review (which is different than a comment). But reviews can be flagged and reviewed by moderators.

  4. I agree that unlisting is better. I think this will be part of the change that will allow authors to mark their scripts as deprecated.

  5. I've added support for the (optional) fields of: version, and copyright. I have to test a few more things but hope to have the fields visible soon.

  6. The models are separate now (userscritps & versions) so I can start showing versions soon!

  7. Should watched topics be public?

  8. BBCode exists for ruby exists! http://code.google.com/p/ruby-bbcode/

  9. @znerp, I've added a suggestion to this to fix that - thanks for the notice

  10. vBm - added

  11. I've added it to the script itself, the number isn't stored in a manner that allows it to be shown on the script listing page, but I'll create a new suggestion to do that.

  12. so correct

  13. What I worry about is people claiming other people scripts (which already happens), and monetary gain would cause more people to try to claim other's scripts. So I think we need to address this issue before we do this.

  14. I like this idea a lot - the site isn't making tons of money (I don't put ads on the homepage, I don't show ads for logged in users, ...) but it does make enough to pay for server cost with a bit left over (I was planing on done something special for the authors, I've talked with a few of them about getting shirts).

  15. plus there is a comment feed for comments on all of your scripts, to find it go to /users/me

  16. This is discussed on http://userscripts.org/forums/3/topics/2130

    perhaps crop the width until you hover over it.

  17. The images would be uploaded on Amazon's S3. So I wouldn't worry about scaling for this. What I do worry about is the site in general is about to break out of the current box. There are a few hours a day where the site is hitting a high load, which means I'll probably need to upgrade the server in a month or two.

  18. Thanks for the update Mikado, I didn't check the CSS library I was using (blueprint), I just checked the CSS I created.

    I re-opened the bug and will do the conditional you recommended for urchinTracker.

  19. I don't specifically store this information right now. I could add it and display it as well (perhaps with progressive disclosure - it wouldn't be there by default but you could click for more information)

  20. interesting idea. I think having a lot of details available via progressive disclosure would be helpful. Having too much on the screen by default could just make things even more confusing.

  21. I finally realized you probably mean the number of installs and comments on _your_ scripts.

  22. I think I got all the css issues, let me know if you still see any. Also, what page do you see the urchinTracker? are you blocking google-analytics.com ?

  23. what do you mean by new installs?

  24. I show this on the display of a script, if you want it on the listing page let me know.

  25. What about spam? Do you have to be "friends"/"followers" with someone in order to send them a message?

  26. Would tracking the number of logged in users who have installed give you the information you are looking for? This is actually a rather complicated issue since some scripts do auto-updating which mess up counts

  27. editing of comments works. let me know if you see any issues.

  28. deletion of your own comments work, now to allow editing.

  29. I'm kinda leaning towards allowing voting on comments and then hiding comments below a certain threshold by default (with an option to show all of them). Kinda like how SongBird did comments on their addons site

  30. it would be more for looking at how the script evolved over time, not for installing older versions.

  31. This is a good idea, assuming the script has been seen by the public. There are scripts that are not ever shown to the public, since they fail "spam" checks. (does't mean they are duplicate/bad, but that they were caught by the over-zealous checks we had to add to the site)

  32. Ziru, the RSS feed has been implemented. There are feeds for comments on a single script and comments on all of your scripts. You can use an RSS to Email type system if you don't use RSS

  33. jerone, can you rephrase this since I don't know what you mean.

  34. twice daily users older than 3 days who haven't activated are now deleted.

  35. It wouldn't replace, you could do either html or bbcode then

  36. I agree that external services is easy. With internal screenshot it would allow thumbnails to be shown on the script list page (visual search/browse)

  37. Not sure about the blinking but I agree with the idea.

  38. I just pushed an update that displays a comments feed on the script page, and if you go to your user page there is a feed of all comments and updates to your favorite scripts, and scripts you are the author of.

  39. I agree. We had this in the database tables for a while but never exposed the functionality. If I get a worker queue going it should be easy to add multiple authors back in.

  40. ya, this is annoying. once I get a few more things fixed I'll get this!

  41. Last time I looked at bbcode, I couldn't find a ruby library that implemented it. If this is voted up, I'll look again.

  42. This would be useful. Does the script author give the info or anyone?

  43. I've had requests for this so that new visitors to the site can see good scripts with context. Perhaps featured script of the day isn't a good way to do that though.

  44. @LouCypher, I agree. USO should be themeable if you are a member :p

  45. What if the reply form was position: fixed as it is in the forum section?