Hello, thank you for reporting your issues, in the future, please, file separate issues separately as you did in e-mails.

Regarding https://academy.patika.dev/sign-in, I interpret your issues as a duplicate of #148. If you believe, you have something to contribute, please, do so in that issue.

By gagura you mean pagure?

Are you sure that what you are observing is caused by JShelter?

I mean the logging-in procedure to pagure is kind of strange. When you click to the "Log in" button in the top right corner of this page, you get to https://id.fedoraproject.org/login/gssapi/negotiate?ipsilon_transaction_id=(some random string). Even when you log in correctly, pagure often displays an error. However, if you go back to the original pagure page and click on the "Log in" button, you are logged in.

Have you observed something different?

Have you experimented several times and have you observed differences in pagure behaviour with and without JShelter?

Please update this issue with precise steps on what you did, what followed and how your experience differed from the expectations.

It's not gagura, it's pagure. corrected.

Are you sure that what you are observing is caused by JShelter?

Yes. the problem persists even if you turn off javascript schield and fingerprint protector. If I turn off or uninstall JShelter from the Manage Extensions page (chrome://extensions/?id=ammoloihpcbognfddfjcljgembpibcmb) the problem should be fixed.
It is completely caused by JShelter.
Turning JavaScript Shield off doesn't help. Setting JavaScript Shield to Recommended doesn't work either. Manually weakening the settings doesn't work either. Turning off JShelter works.

The same goes for path.dev.

Have you experimented several times and have you observed differences in pagure behaviour with and without JShelter?

I tried a lot of experiments. I tried about 30 combinations of settings. I refreshed the page every time. Most of the time I clicked on the Remove button next to JShelter > Global Settings > JS Shield details > A list of websites with redefined JavaScript Shield: > I clicked the Remove button next to websites's , I changed the settings, refreshed the page. I tested many combinations. I also manually tested the settings one by one. Then I decided to report back here.

Click on the Modify button next to the JavaScript Shield label.
What is the highlighted level button text?

I tried Strict. It didn't work. I tried Recommended. It didn't work. I tried Ecperimental. It didn't work. I tried others. It didn't work. I changed the settings manually, still didn't work.

It's normal to get confused because I wrote a report at 4 a.m. and I was sleep deprived. I've fixed it.

You might have the same problem.
Why are you asking me to give you data I don't want to give you?
You can try it yourself

Whatever changes were made today have fixed this issue.
Even with JavaScript Shield and/or FingerPrint Detector ON, there is no problem.
I've deleted cookies a few times and tried a few combinations again and again and the problem is solved. I had no problem, I was able to log in, but we can't find out what's causing the problem. If you keep this thread open, you can investigate what's causing the problem.
Or you can close it on the principle of "if the system works, don't touch it".

The reported says:

I tried a lot of experiments. I tried about 30 combinations of settings. I refreshed the page every time.

In the future, please provide precise steps. It looks like you performed a lot of irrelevant steps, or at least it looks so.

Due to:

Why are you asking me to give you data I don't want to give you?

and:

Whatever changes were made today have fixed this issue.

I am going to fix the issue as invalid. The issue miss clear steps to reproduce.

For future records, by whatever changes were made, the reporter likely means 0.20.2. The only relevant changes might have been in NSCL, some parts of the library were rewritten and that might have fixed a bug lurking in the backend.