Discussion on Digg autobury submissions | Userscripts.org

looks like it's time for another update, replied by Bhima

Bhima — Mon, 12 Oct 2009 20:28:54 +0000

Brilliant! Works great, thanks!

looks like it's time for another update, replied by pwlin

pwlin — Mon, 12 Oct 2009 19:36:27 +0000

Hi Bhima,

I fixed the issue with the new design. The script should work now. I also added a new variable at the beginning of the script: delay_on_page_load which is defaulted to 5 (seconds). There you can control how long you wanna wait before executing the script on the page load.

Please upgrade to v. 0.3.3

looks like it's time for another update, replied by Bhima

Bhima — Mon, 05 Oct 2009 06:01:23 +0000

Digg made another change to their site and so the script no longer works.

as I think we should add a delay on the first bury on each page loaded.

please revisit: down-mod cretins, replied by Bhima

Bhima — Tue, 03 Mar 2009 09:05:30 +0000

Right then... I will add 50 Euros to Pwlin's bounty. One other thing: I would like the key-word blacklist to allow for spaces, special characters, and regexps

please revisit: down-mod cretins, replied by pwlin

pwlin — Fri, 23 Jan 2009 00:27:16 +0000

I think you are confusing "hacker" with a "cracker"

http://foldoc.org/index.cgi?query=hacker&action...

hacker

< person, jargon > (Originally, someone who makes furniture with an axe) 1. A person who enjoys exploring the details of programmable systems and how to stretch their capabilities, as opposed to most users, who prefer to learn only the minimum necessary.

2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than just theorizing about programming.

3. A person capable of appreciating hack value.

4. A person who is good at programming quickly.

5. An expert at a particular program, or one who frequently does work using it or on it; as in "a Unix hacker". (Definitions 1 through 5 are correlated, and people who fit them congregate.)

6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example.

7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations.

etc...

please revisit: down-mod cretins, replied by Avindra V.G.

Avindra V.G. — Thu, 22 Jan 2009 22:09:58 +0000

the first hacker

"hacking" has taken a whole new meaning nowadays...

please revisit: down-mod cretins, replied by Good To Too

Good To Too — Thu, 01 Jan 2009 10:45:27 +0000

mwahaha!

Digg banned me for using this, replied by Good To Too

Good To Too — Thu, 01 Jan 2009 10:44:19 +0000

this is exactly why there needs to be much much wider variance on time between actions of this script.

Digg was started by a G4 fop therefore it cannot be too difficult to game the system.

Digg banned me for using this, replied by is

is — Tue, 30 Dec 2008 20:39:43 +0000

I got banned for using this, so I made a new version of the script that just hides the stories instead of burying them.
Get it here: http://userscripts.org/scripts/show/39537

Thanks for the great script!

please revisit: down-mod cretins, replied by pwlin

pwlin — Sun, 28 Dec 2008 03:00:47 +0000

Autobury comments - Bounty Award
I will donate 50 USD to the first hacker who manages to write a user script/firefox extension for autoburying user comments.
Requirements:
- Open source
- Quality code
This offer stands until the end of 2009.
I'm sorry, but I really have no time to write this. So go ahead and win this bounty contest.
Spread the word.

please revisit: down-mod cretins, replied by Good To Too

Good To Too — Fri, 26 Dec 2008 10:22:41 +0000

http://userscripts.org/topics/12282

"plan to release a userscript to down-mod morons: either by username flatout, or by keyword/phrase in comment?" -- HatastiX

Archived Comments, replied by Bhima

Bhima — Sat, 18 Oct 2008 11:37:28 +0000

Right... I had no idea what a profile was, so I googled it. Mozilla has a page describing how to deal with them (as the "profile" does not appear on the main surface of the Firefox GUI): http://support.mozilla.com/en-US/kb/Managing+pr...

As a side note Mozilla figured out what OS and what version of Firefox I was using and displayed the correct info... That is pretty clever :)

Now I am not using Digg Lite and I've learned something important: Always turn off scripts which could interfere while testing!

Archived Comments, replied by pwlin

pwlin — Sat, 18 Oct 2008 10:36:19 +0000

By 'clean profile' I meant a new Firefox profile! It's always good to test these stuff with a new Firefox profile so you know there are no interferences with other scripts as in this case.

I tried to find an easy solution so it works with Digg Lite but I have to change so many logic. Can you please not hide Digg's footer? Just comment the line with 'this.addCSS( "#footer { display: none; }" );' in Digg Lite. Sorry about that.

Archived Comments, replied by Bhima

Bhima — Sat, 18 Oct 2008 09:03:20 +0000

I am using the Current version of Firefox (it updates itself and I just go along with the flow). What do you mean by clean profile? Should I make a new user and test from there?

D'oh! I am such an idiot! On Firefox I also have the script "Digg Lite" running which hides the footer. I wonder is there an easy way to replace the footer that Digg has with the Autobury infobar?

Below is the code from Digg Lite... that's a very simple thing.

init: function() {
// hide the page footer
if( this.config.hide_footer ) {
this.addCSS( "#footer { display: none; }" );
this.addCSS( "#contents { padding-bottom: 0; }" );

Archived Comments, replied by pwlin

pwlin — Sat, 18 Oct 2008 09:00:42 +0000

Bhima, I tested it with a fresh Firefox 3 profile and infobar is showing. What version of Firefox are you using? Please test it with a clean profile and let me know if it works. Thanks for trying out.

Archived Comments, replied by Bhima

Bhima — Sat, 18 Oct 2008 08:28:13 +0000

Wow, that was fast. And marvelous. Now it works as before on my Mac using Safari (with Greasekit) but using Firefox the Autobury Infobar does not appear (but the burying is still going on)

Archived Comments, replied by pwlin

pwlin — Fri, 17 Oct 2008 22:10:44 +0000

I fixed the issue, Bhima. Please check if it still works in Safari.

Archived Comments, replied by Bhima

Bhima — Fri, 17 Oct 2008 18:20:58 +0000

Well... once again Digg rolls out a series of upgrades and thus the script no longer works

Archived Comments, replied by Pasta2000

Pasta2000 — Thu, 09 Oct 2008 13:02:14 +0000

In both copies of the script, show_infobar was set to true. Not having this working is not a big deal to me so don't worry about this bug since it sounds like it is just me and my set up.

I don't hammer Digg too hard. There are a few things I have done to prevent this. The 'bury_interval' in one copy of the script is set to 22 and is set to 7 in the other. Also, I have customized the default view of Digg to a few categories so that I am not blindly doing a bury across all of Digg. Lastly, I remain positively active so that my account isn't seen as just doing buries.

To answer your last part - calculate how long do you need to stay on a page so all the bury requests can take place - Maybe a second. Two seconds max. There usually isn't much to bury on the pages i am viewing unless I do a deliberate search.

Thanks much. Keep up the good work.

Archived Comments, replied by pwlin

pwlin — Wed, 08 Oct 2008 16:58:19 +0000

There is another variable on line 27 of the script:
show_infobar : true ,
if that's set to false, you won't see the info bar. Maybe you changed that somehow. Other than that, unfortunately I can't reproduce this bug to tell you where the problem is.

Now i just need to make sure I don't get banned for using scripts.

Try not to hammer Digg and set your 'bury_interval' on something high. If you really won't see the info bar, calculate how long do you need to stay on a page so all the bury requests can take place.

Archived Comments, replied by Pasta2000

Pasta2000 — Wed, 08 Oct 2008 12:22:13 +0000

@pwlin

Correct, I do not get the "info bar" at all. This is not an issue outside of testing this out. Thanks for the info on how to check this with Firebug. Because of that tip, I can see that this is working correctly with the script installed twice. I can see that the 14 code for the script that buries things as inaccurate. I can also see the 16 code for things that are a general bury.

Thanks Much Again. Now i just need to make sure I don't get banned for using scripts.

Archived Comments, replied by pwlin

pwlin — Mon, 06 Oct 2008 18:59:21 +0000

@Pasta2000

I just don't get the report of what it 
had done or is doing (never did show)

You mean you never get that 'info bar' at the bottom of every page which shows the progress of burying? That's pretty strange! You should always see it.

To check if this is burying DIGGs correctly, 
is there an easy way to tell after something is 
buried how it was buried?

You can check that with Firebug extension. Enable Firebug and its "Show XMLHttpRequests" option, go to Digg site and open Firebug console.
You should see bury requests one by one appearing on the console. Expand one of the requests and click on "Post" tab. There is a line like:
token=xxxxxxxx&id=xxxxxx&code=xx
the number in "code" is what Digg uses for recognizing what kind of bury it is.
for example "code=14" means inaccurate.
Other numbers used by Digg are:
16 : general bury
8: duplicate
15: wrong topic
12: OK, this is lame

Archived Comments, replied by Pasta2000

Pasta2000 — Mon, 06 Oct 2008 14:56:48 +0000

So far it looks to be working as expected. Things I want buried get buried. I just don't get the report of what it had done or is doing (never did show). I suspect that is because of how I have my FF3 set up. I also installed the script a second time under a new name. One copy of the script is for users that I do a "bury". the other copy is for keywords (or in my case submitted web sites) that bury as "inaccurate". I did learn in doing this not to leave variable list empty ( //ig; ) because it reads it as a comment and the script doesn't work then. I just put in something so odd that it should find nothing to bury.

To check if this is burying DIGGs correctly, is there an easy way to tell after something is buried how it was buried?

Thanks for the updating this so quickly.

Archived Comments, replied by pwlin

pwlin — Sun, 05 Oct 2008 12:32:37 +0000

@Pasta2000
I added a 'bury_type' variable at the beginning of the script.
use the following numbers to indicate the type of your buries:
for general bury, use 1
for duplicate story, use 2
for spam, use 3
for wrong topic, use 4
for inaccurate, use 5
for OK, this is lame, use 6
This is a global variable though, meaning it works for ALL the users/keywords.
Right now implementing it on a per user/keyword basis will destroy the simplicity and robustness of the script so i hope you still enjoy this added feature.
Please let me know if there are any bugs.

Archived Comments, replied by Pasta2000

Pasta2000 — Fri, 03 Oct 2008 20:29:07 +0000

What would it take to change the script to "Bury as Inaccurate"? I ask because some if the places that are DUGG are complete BS. A plain Bury isn't good enough. - May I suggest updating the script so that one can choose how something can get buried. Thanks