Archived Comments (locked)
|
|
The following is an archive of comments made before threaded discussions was implemented (November 16th, 2008) |
|
|
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! |
|
|
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. |
|
|
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() {
|
|
|
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. |
|
|
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) |
|
|
I fixed the issue, Bhima. Please check if it still works in Safari. |
|
|
Well... once again Digg rolls out a series of upgrades and thus the script no longer works |
|
|
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. |
|
|
There is another variable on line 27 of the script:
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. |
|
|
@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. |
|
|
@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 |
|
|
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. |
|
|
@Pasta2000
|
|
|
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 |
|
|
@smaulz:
The user names should be added as a regular expression like: /user1|user2|user3/ig Also Digg is sometimes slow so you may need to change 'var bury_interval' to something higher. 15 would be ok. |
|
|
ATTENTION: Anyone who hates spammers on Digg, please visit the following page that I have set up to fight spammers, 'smear artists', and the rest of the scum on Digg. Help our community out by leaving a comment with any user(s) you think should be added to this list! |
|
|
This working for anyone? Just found it and installed, edited the blacklist, and don't see any results. Has Digg done another redesign or something that I missed? |
|
|
Excellent! Now it works well with greasekit and Safari on all the Digg pages. |
|
|
Bhima: Thanks for reporting the problem, I have fixed most of the issues with Digg's new design. Please let me know if there are still bugs. yellowriver: I'm sorry but this script doesn't autobury comments. It only works with posts. I've been busy a while back writing the parts for autoburying comments but then Digg changed the design and I had to rewrite a lot of stuff and there were some real projects waiting for me so I never finished that part. I'll be back on it as soon as there is some free time. |
|
|
Well... the new Digg changes interfere with the autobury script. Some pages work and some don't. Pity that. |
|
|
----- How can this be modified to auto bury comments by user or is there a version availble? Thanks.. |
|
|
I don't use a lot of greasekit scripts but I use this one everyday. One more observation: keywords which are made up of multiple words do not work in the way I expect or understand. Some get buried some don't. Anyway, thanks for the update. |
|
|
Bhima, it's great that this script still works! I just fixed a small issue. Sorry for not updating in a long time because I've been busy with other things but I have your requests in my mind and will add them gradually. |
|
|
Well, it's been a while since I've started using this script. And I have the following comments: This script works on Safari also (via greasekit).
I really, really wish there was a comment autobury script (digg comment enhancer script is also nice) |
