Slashdot Firefox Extension

christopherfinke writes "I've been working on Slashdotter Firefox extension for Slashdot users, and version 1.2 has been approved by the Mozilla admins. Features include the ability to auto-add cache links after story links (from any of Coral Cache, Google Cache, or Mirrordot), a quick-reply feature that adds a 'Reply' option to the right-click menu when you select text in a comment, the option of styling all of Slashdot's pages like a chosen Slashdot section, links in the comment sections that allow you to toggle open/closed all of a comments replies, and more. All of Slashdotter's features are optional, and the extension is compatible with Firefox, the Mozilla Suite, Seamonkey, and Flock."

Comments

Re:Awesome

[christopherfinke]

Looks like the select-text replies aren't AJAX, but it turns the reply to this link into an AJAX-enabled thingy.

The AJAX replies feature isn't for replying to comments, it's for those links that say "X Replies below your threshold." It makes it so you don't have to load a new page to see those replies.

Now we just have to wait for the VCs to come along and dump millions on the poor guy for using the word AJAX.

Woohoo!

It's really quite nice

[A Dafa Disciple]

This was the first I had heard about this exstension. I've been using it for the last half hour or so and I'm very pleased. It really does make browsing /. here a more enjoyable experience.

I find some of the additions of the extension to be things that really should have be built into /. anyways, such as things that you find at Digg like AJAX comment retrieval - things that are not at all hard to implement that can dramatically increase the user experience. Nevertheless, I'm not really too surprised by /.'s apparent slowness in embracing new web technologies considering how long it took them to simply make this site fully standardized in CSS

One negative aspect of the extension, however, is that it seems to me that, depending on the feature set you have enabled, /. pages in general now take a bit longer to load, but not so long that it makes the plug-in not worthwhile, especially since it facilitates the speed of navigation in other ways.

All of you should check this out for sure!

Re:trolly troll troll

[amliebsch]

The features belong to "Slashdotter," the name of the extension given in TFS.

LEARN TO READ! HTH HAND.

Re:Features

[Jugalator]

If it parsed the story tag "dupe" (which actually are in DIV's using the CSS class "tags", so they should be identifiable), and could associate these tags with their detailed story (DIV's with CSS class "details"), these DIV's can then be hidden by applying the appropriate collapsing "display:none" style, and if you've got this far, possibly also add a link to expand these collapsed stories if you're still interested.

Re:Aw nuts

[christopherfinke]

But now I can't see tags anymore, even though I unchecked "hide tags"

Whoops. That'll be fixed as soon as 1.2.1 is approved by a Mozilla admin; in the meantime, if you like Slashdotter and want to show tagging, you can download the new version from my site.

Re:Opera?

[appavi]

Opera 9 Beta supports greasemonkey scripts. Greasemonkey scripts should work in opera as is or with some minor modifications.

Re:Reply to text option

[rholliday]

any chance we could customise the reply to selected text option?

You can. It's in the Extension options.

Re:Missing one...

[appavi]

Camino doesnt support extensions.

From Camino FAQ

Q. Does Camino support Firefox extensions?
A. No, and it never will. Firefox extensions rely on XUL (a user interface toolkit made by the Mozilla Foundation) to interact with the user and draw their interface. Camino uses Cocoa (an interface toolkit made by Apple) and does not support XUL.

Also from the interview with Camino Project lead Mike Pinkerton

We recognize this is a problem for our users, but extensions only exist because of the cross-platform UI layer upon which Firefox is built. It's that same cross-platform UI layer that makes Firefox feel "wrong" on Mac OS X. Camino's use of Cocoa for the user interface makes it fit in with the rest of the platform, but prohibits us from using extensions. We feel this is a trade-off worth making. That said, we are investigating ways to allow non-user-interface extensions to register and work correctly.

Thank God...

[identity0]

Slashdot's comments section has such a broken UI, I was actually thinking the other day to write a program to help me navigate it. Props to you for making that unnessisary.

I have some ideas about what is broken on Slashdot. Some of them would require actual site modifications to fix, other could be fixed with a browser extention.

If you want more bugs, how about:

  - When I'm in the post writing screen, there is no text of the story or link to it, so I have to open Slashdot in another tab and go to the story to read it.

  - The comments index is very, very broken. The "threshholds" concept's three drop-down menus (-1:5), (Threaded/Nested/Flat/No comments), (Oldest 1st/Newest 1st/Highest 1st/Oldest 1st Ignore threads/Newest 1st Ignore threads), and the "Comments spill at 50" concept interact in bizzare ways such that I don't even know what it's *trying* to do.

  - I *hate* the fact that comments below your viewing threshhold are listed at the bottom of the thread level instead of between the posts that it was replying to and got a reply from. So you sometimes see people seemingly reply to themselves, or flaming others, but they are actually replying to something below your viewing threshhold. I've seen arguments start this way, because someone thinks a flame was directed at them instead of to the AC that replied to them earlier. Please. for the love of god, put in an indicator if there is a post below the threshhold that a post is replying to.

  - I would like to be able to view the whole comments section as a threaded, subject-only(that is, no expanded posts) view, and open up individual posts which will open up in a nested, all-open veiw. Perhaps allow right-clicks on post titles should allow you to open up the comment and its follow-ups with any pre-specified threshhold options?

  - Instead of three drop-down menus in the comment index, how about a list of rules which we can rearrange the order of to make settings? Might require AJAX.

  - Slashdot's user prefs allow me to "bias" the moderation towards funny, or informative, or other moderation types, but it is a PITA to change it for each story. Some stories I want to read in "funny" mode, others I want to read in "Informative" mode. I should be able to change the bias to one of several presets like on an Winamp equalizer on a per-story basis.

Re:*Gasp*

[christopherfinke]

No Bon Echo support? :(

I just downloaded Bon Echo and tested Slashdotter; it works, and I've uploaded a compatible version (1.2.2) to the Mozilla Addons site. It should be approved anytime within 1 day to 3 weeks (based on past experiences). In the meantime, it's available here.

Re:Features

[mrchaotica]

Nah, he's using <i> for good reason -- just to italicize the text to visually differentiate it from the rest of his post, because Slashdot doesn't support doing it with CSS like it ought to. He should only use <em> if it's actually emphasized, which it isn't.

On the other hand, he really should use <blockquote> instead of <p> because it is a quote, which was what I was going to point out until I saw your post. ; )

Personally, what I use for quotes (manually, until I install the extension) is <blockquote><i>%s</i></blockquote>.

(I just hope he notices and reads this post, since I replied to a reply instead of replying to his post directly.)

Re:Opera?

[pAnkRat]

I wrote a bookmarklet, which I personaly use in Galeon, but it should work in all Moz* browsers.
If you hover over the comment Link (#15013415) it will pull the moderation results for this post with xmlHttp, and display the result table in a DIV tag, beside the current post.
The bookmark name is "slash mod"
The URL is:
(AFAIK this should all be in one single line.)

javascript:(function(){ var currentUrl =''; function h(event){ var url = 'http://' + this.host + '/comments.pl' + this.search; if(currentUrl == url){ var theDiv = document.getElementById('kwsmodding'); if (theDiv != null) { theDiv.style.display='block'; } } else { var req = new XMLHttpRequest(); req.open("GET", url, false); req.send(""); var resultText = req.responseText; var tableText = '' + resultText.split('data_head">')[1].split('')[0] + ''; var theDiv = document.getElementById('kwsmodding'); if (theDiv == null) { var theDiv = document.createElement('DIV'); var mybody=document.getElementsByTagName('body').item( 0); mybody.appendChild(theDiv); theDiv.style.zIndex=100; theDiv.style.backgroundColor='grey'; theDiv.id='kwsmodding'; theDiv.style.position='absolute'; theDiv.style.backgroundColor='grey'; theDiv.style.display='block'; } theDiv.innerHTML=tableText; theDiv.style.right='30px'; theDiv.style.top=(event.pageY - 20 ) + 'px'; theDiv.style.display='block'; currentUrl = url; } event.preventDefault(); } function hout(event){ var theDiv = document.getElementById('kwsmodding'); if (theDiv != null) { theDiv.style.display='none'; } } var xpe = new XPathEvaluator(); var nsResolver = xpe.createNSResolver(document); var result = xpe.evaluate('//li/div/div/a[contains( @href , "comments" )]', document, nsResolver, 0, null); while (res = result.iterateNext()) { res.addEventListener('mouseover', h, false); res.addEventListener('mouseout', hout, false); } })();

Once this is added to the bookmarks you can use it in the following way.

• go to slashdot
• pick story
• click "read more"
• after the page has finished loading, klick the Bookmark
• mouse hover over a Comment Url (normaly the last part of: " by Poromenos1 (830658) Alter Relationship on 23:26 28 March 2006 (#15013415)" in the Comment header)
• wait a sec.
• read result
• mouseOut the let the table dissapear again.

The code does some cacheing, if the users hovers/mOuts the same link a few times, the URL request is done only once.