Notices tagged with rdnrefresh, page 7

  1. @jojoax !rdnrefresh

    Thursday, 16-Feb-12 11:35:31 UTC from web in context
  2. by the way, to all new RDN members, if you'd like added features and autorefresh on this site I suggest installing the Greasemonkey (Firefox) or Tampermonkey (Chrome) plugin and visiting the !RDNrefresh group for a very useful script

    Thursday, 16-Feb-12 11:34:15 UTC from web
  3. @purplephish20 It's one of the things I have !rdnrefresh highlight for me, so when I see it I go looking for whomever needs stomping.

    Wednesday, 15-Feb-12 21:43:19 UTC from web in context
  4. @minti !rdnrefresh has a couple features I like having, that's what's really keeping my from switching, but the context issue doesn't help either.

    Wednesday, 15-Feb-12 03:54:26 UTC from web in context
  5. @pinhooves !mintrefresh is like !rdnrefresh but [i]better[/i]

    Wednesday, 15-Feb-12 03:53:43 UTC from web in context
  6. @zimzap it's !rdnrefresh but [b][u]better[/u][/b]

    Wednesday, 15-Feb-12 03:41:10 UTC from web in context
  7. @laserpon3 Heh, we've gotten around the refreshing issue by making scripts that fetch the new notices for us. !rdnrefresh and !mintrefresh

    Wednesday, 15-Feb-12 03:33:23 UTC from web in context
  8. @laserpon3 There's !mintrefresh or !rdnrefresh to fix the refresh thing.

    Wednesday, 15-Feb-12 03:33:04 UTC from web in context
  9. @minti If you use !rdnrefresh you can set the background to anything you like.

    Tuesday, 14-Feb-12 23:47:10 UTC from web in context
  10. @ruby Yes, there's a "Hide username" option on !RDNrefresh

    Tuesday, 14-Feb-12 23:37:53 UTC from web in context
  11. @derpy128 !rdnrefresh

    Tuesday, 14-Feb-12 23:03:13 UTC from web in context
  12. @solisbrony @scootnukem #: I'd suggest getting !rdnrefresh (or !mintrefresh #), it'll extend the sites features and auto-update the timeline so you don't have to F5F5F5F5F5. :p

    Monday, 13-Feb-12 19:37:10 UTC from web in context
  13. @alias that why I have !rdnrefresh :3

    Monday, 13-Feb-12 07:37:49 UTC from web in context
  14. @chiefanchor I agree, though I tend to use the in context links a lot so I've been sticking to #

    Sunday, 12-Feb-12 07:18:31 UTC from web in context
  15. @pony If you want less of a hit to computer performance, use !mintrefresh - # is a resource hog, since it loads the entire page at a time.

    Sunday, 12-Feb-12 07:17:10 UTC from web in context
  16. @sillyzen BTW, if you get tired of refreshing or if you want to read and post spoilers about the newest episode I recommend installing the Greasemonkey (Firefox) or Tampermonkey (Chrome) plugin with either the !RDNrefresh or !MintRefresh script.

    Sunday, 12-Feb-12 07:16:13 UTC from web in context
  17. @chipper64 oh haha! yeah, if you use the GreaseMonkey (FF)/ Tampermonkey (Chrome) plugin with the !RDNrefresh script, you can encrypt and decrypt spoilers

    Thursday, 09-Feb-12 07:23:34 UTC from web in context
  18. @purplephish20 Oh, he didn't do anything. He fighted with some mods when the colour codes and all that was released for !rdnrefresh, because they didn't let people abuse them for test. Then he said he was going to left forever. Then cerulean started encouraging colfax to ban him because he was "trying to make drama saying he's not coming back" and colfax silenced him so he's forced to say "I'm sorry I didn't mean to say forever etc." to be able to post again. As it became a matter of pride, he felt offended and decided not to come back and give colfax and cerulean that pleasure.

    Wednesday, 08-Feb-12 13:34:56 UTC from web in context
  19. @bladeshadowmane !rdnrefresh

    Monday, 06-Feb-12 05:16:23 UTC from web in context
  20. @template93 !rdnrefresh

    Monday, 06-Feb-12 01:16:20 UTC from web in context
  21. @pony I find it functions better than #, personally - cleaner, etc.

    Sunday, 05-Feb-12 20:04:01 UTC from web in context
  22. @zeeraw Yeah, but right now both !rdnrefresh and its newer counterpart !mintrefresh are the quickest ways to get that functionality.

    Sunday, 05-Feb-12 19:55:36 UTC from web in context
  23. Looked at rdnrefresh, looks like a pretty tedious way to solve the "live" issue. I'd stick to web sockets :D #

    Sunday, 05-Feb-12 19:54:30 UTC from web in context
  24. @zeeraw are you already aware of !rdnrefresh ?

    Sunday, 05-Feb-12 19:46:01 UTC from web in context
  25. @alias @cupcakinator !rdnrefresh

    Sunday, 05-Feb-12 17:12:49 UTC from web in context
  26. Holy crap... !RDNrefresh is actually...WORKING for me?! o_O It's...it's not possible! Well, best not look a gift horse in the mouth and uninstall StatusNet Desktop, which is now utterly redundant.

    Friday, 03-Feb-12 00:01:02 UTC from web in context
  27. @leonkfox Just follow the links here !rdnrefresh , im using firefox and its working fine, and just a little thing you should know... I'm currently listening to "ask a fox! Episode 1"

    Thursday, 02-Feb-12 23:41:00 UTC from web in context
  28. @leonkfox Get Tampermonkey for Google Chrome, and install !rdnrefresh though it.

    Thursday, 02-Feb-12 23:39:33 UTC from web in context
  29. !rdnrefresh # Any reason why my Stream keeps highlighting instead of new posts since last refresh?

    Tuesday, 31-Jan-12 15:09:37 UTC from web
  30. @nerthos And this netbook's resolution doesn't allow me to click "ok" to install !rdnrefresh. I'll have to fin an older version, with a smaller url list, and then update.

    Tuesday, 31-Jan-12 11:25:40 UTC from web in context