Subject: oSokker

Nope, maybe you have first to update your Java and Flash-Player, Shockwave-Player....

You can also use SkUnk instead of oSokker. It has most oSokker functions implemented and there is no problem with the firefox verification.

http://sokker.org/forum_topic/ID_forum/1259/ID_topic/3014566/pg/1

If You did what Trevor suggested and addons page says it's all ok, but You still do not see oSokker working then it probably means that You are using some bad/old/deprecated version of oSokker

use oSokker downloaded from one of the links in this post

ad of course do what Trever said, it is essential to get oSokker, SkUnk or whatever extension You are installing fron non-official source working

Thanks Trevor. Changing to false worked. Skunk link for Firefox says maintenance so I tried your first suggestion.

Thank you for help.
I try to explain one more time. Java and all other stuff is up-to-date.
Firefox is not. I went back to version 43.0.01

But, I got it to work!

And, skunk link is not working...
(edited)

If you still want to use SkUnk, try this link:
firefox: https://www.dropbox.com/s/uy43zccjbnz8byd/skunk.xpi?dl=1
I just checked it - this works.

@ kryminator : Have you read it? The SkUnk-link for FF on page 1 doesn´t work!

(edited)

which one is better by the way? and maybe it's possible to use both of them ?

which one is better by the way?
For me SkUnk, because it has more options. For others oSokker... Everybody has different reasons ;)

and maybe it's possible to use both of them ?
Yes. In this case you have to deactivate some common options, so that you have e.g. only 1 NTDB-flag - otherwise you see 2 NTDB-flags...

For me it was a problem when I used ossoker or skunk, whenever I wanted to watch one of my matches I was waiting 300 seconds after which another 300 seconds and so on continuously in a loop.

After deactivating both of them I was finally able to see my matches....

I was waiting 300 seconds after which another 300 seconds and so on continuously in a loop.

lol, greg dream ^^

SkUnk has a bug which is hard diagnose, its hard to find its to find cause but I am almost sure it was causing this "continuous loop" so disabling it would be probably enough and even better would be if You would disable one SkUnk option (that about skipping 300s match ads) responsible for this functionality.
Also, I wouldn't recommend using SkUnk next to oSokker - just choose one of them. I try to develop SkUnk to be able to work with oSokker enabled, but since I am not using oSokker these tries may be not enough so in some cases they mey interfere with each other.

@Tsolias
I know that these links are not working but somehow I didn't feel like changing it. Nonetheless, I have changed them a moment ago.

(edited)

I have tried disabling that option in skunk, I disabled one or the other program and for me it's started to work, to be able to see my matches, only after I disabled and uninstalled both programs.
I was sorry because in the past I was using all the time osokker.
I liked the idea of skunk better now but not all the options were working, many didn't...

could someone please explicitly explain how does someone install the oSokker for Chrome? I have tried several times, downloaded, installed, chrome closed and reopened, still no oSokker....

Thank you.

1. download the .crx file
2. treat it like it was a zip archive and extract content to some directory, lets say c:/osokker
3. now, You should have oSokker.js and other files directly in c:/osokker, what I mean that path c:/osokker/oSokker.js should be valid - I am writing this in case that there is more directories in directory tree during .crx extraction;
nevertheless the c:/osokker or any directory where manifest.json and oSokker.js and other files from .crx content are is our osokker directory
4. now open Chrome, go to chrome://extensions
5. check developer mode or somthing like that if it is unchecked
6. click on load unpacked extension and select osokker directory there and maybe click ok or do some other kind of confirmation
7. osokker should be loaded and working even after browser restart

Thank you Krimy!!!
(edited)

:(( it is too complicated for me :( cannot. I know I am stupid as far as computer things are concerned...maybe for FF is a bit less comlicated.