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

Features

[donnyspi]

Does the extension automatically remove dupes and fix typos in the titles of submitted stories???

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.

At First Glance

[Dante Shamest]

I thought this extension allowed me to slashdot sites while I browse. :O)

Seriously though, I like this feature:

* You can choose to have all Slashdot pages styled like one of Slashdot's sections. For example, if you're a fan of the Games section's hideous purple and black color scheme, you can have every Slashdot page look just as horrifying!

Re:trolly troll troll

[Anonymous Coward]

I think you'll find that the grammatically correct version would have been "All your Slashdotter feature are belong to optional". HTH

What about IE?

[aw232]

Aren't you going to make one for IE? How about IE7?

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!

Yay!.. Taco did you see that?

[CptnHarlock]

I've been hoping for Taco to include the "colapse thread" feature for a long time. I still think it should be native instead as in the form of a plugin - then everyone could (and probably would) use it.

It would make it a lot easier to find the next real comment after a comment tree created by some Troll post... Another positive thing is that we'd get rid of the "high positioning" replies that normaly end up in the first tree. Are you listening Taco?.. :)

Cheers!..

Re:Wow

[christopherfinke]

This dude needs a job!

I've got a job. What I need is a life.

Re:Opera?

[appavi]

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

Re:Legitimate story?

[thrillseeker]

Seems hazy if an author should be allowed to submit a story to /. about his own project.

Yeah, we wouldn't want anyone knowledgeable about a subject starting threads.

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:The times they....

[Nimey]

I set any comment modded "funny" at -6 in my preferences. That cut down on a lot of the garbage.

I see a great need: a Bayesian function on this extension to automagically "mod" comments; e.g. anything with the word "Micro$oft" or "M$" modded at -4, free ipod spam at -6, and so on.