I am not staying logged into Fansly

[Zero3K]

Describe the bug
When using a script to refresh a model's page on Fansly, I notice that I will be logged out after a while and have to log back in.

To Reproduce
Steps to reproduce the behavior:

1. Install an auto-refresh extension.
2. Go to https://www.fansly.com
3. Login to your account on it.
4. Go to a model's page.
   4.. Set the refreshing extension to refresh every 30 seconds.
5. Start the auto-refreshing.
6. Wait and you'll eventually be logged out.

Expected behavior
It should stay logged in no matter how much time passes.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 11
• Bitness of browser: 32-bit.

[Half-Modern]

Needs to be tested on another browser with same base Chromium version.

[Zero3K]

Where do I download it?

EDIT: I tried replicating the issue with the Chromium build at https://github.com/macchrome/winchrome/releases/download/v128.6613.114-M128.0.6613.114-r1331488-Win64/ungoogled-chromium-128.0.6613.114-1_Win64.7z. It still happened. So, it is an issue with Chrome itself. I wonder if you could fix it and send it upstream.

[ZepopaOwleMukasa]

@Zero3K

Are you sure this isn't just a security mechanism of that website itself? Did this ever used to work for you? You could try Firefox too.

[Zero3K]

1. I am sure that it isn't a security mechanism of the website itself.
2. No.
3. It doesn't happen in Pale Moon 33.4.1.

It seems to happen after I put my laptop into sleep mode for a couple of minutes, resume from it and then view the tab containing the model's page.

[ZepopaOwleMukasa]

@Zero3K

Well, if it does work in Pale Moon, it would indeed be a chromium issue. However, are you using the exact same refresh extension on both browsers?

[Zero3K]

Yes, I am. I am using a userscript.

[billi857]

When using a script to refresh a model's page on Fansly, I notice that I will be logged out after a while and have to log back in.

Try "pinning the tab" (the option is in the tab properties). Perhaps the problem is related to Chromium resource saving: when you stop actively using the tab and go to another site, the scripts stop running on the inactive tab. If you make the tab "pinned", it should help.

The problem may also be related to caching: when your script is executed, the site (or some separate element of the site) is loaded not from the server, but from the browser cache. Try implementing the script differently (another update command), and also try the flags related to caching.

Why refresh every 30 seconds? Are you tracking some very important information? Usually authorization sessions last tens of minutes or longer. Constant refreshes (at regular intervals) can also be blocked for security reasons.

[Zero3K]

1. The tab is in its own window.
2. I don't think that is the case.
3. The 30 second refresh works in Pale Moon.

[ZepopaOwleMukasa]

@Zero3K

I really don't think it's a good idea to publicly post your raw cookie data like that. If not for security reasons, then for exposing your, let's say, "private preferences". You should probably take that down.

[Zero3K]

Then how can I help debug this issue?

[ZepopaOwleMukasa]

@Zero3K

There is nothing to debug. It's an issue in chromium (as you've tested), the best course of action would be to report this issue to the chromium project itself.

It's also entirely possible that Pale Moon behaves in a non-standard way in terms of handling cookies, causing it to "work" there, even though it shouldn't. You should test this in Firefox and see if it behaves the same way Pale Moon does to rule that out, ultimately, possibly, pinpointing the issue directly to chromium.

[Zero3K]

Wouldn’t they want me to debug it? Also, would win32ss add the fix if they make one to the latest source code?

[ZepopaOwleMukasa]

@Zero3K

Wouldn’t they want me to debug it?

Of course, what I meant was debugging it in this repository, should've been a little more clearer.

Also, would win32ss add the fix if they make one to the latest source code?

Supermium is currently following the chromium esr branch, if it get's fixed, you'd need to wait until the esr branch is up to date with the chromium version it got fixed in. This may take a while, so the sooner you create a report in the chromium repository, the better.

But again and I can't stress this enough, please test if Firefox behaves either like Pale Moon or chromium. This is important to see if this is proper behavior or if Pale Moon just handles cookies in a non-standard way.

[Zero3K]

This issue seems to be reported by another user(s). Here's the link to the bug report:

https://issues.chromium.org/issues/391763852

[Zero3K]

Maybe other people can try to replicate it with Chromium and offer their findings to the linked bug report in order to get a developer/developers attention.