Closed Rakshae closed 2 years ago
I am also having this same issue, but with the latest commit.
Same issue, fansly scraper is totally hosed. I tried wacking everything and downloading latest nd same issue. This project has not been updated in months and I fear it is dead
Happens on the message portion of scrape.
Name: fansly creator
Type: Stories
Type: Posts
Type: Archived Posts
Processing Scraped Posts
100%|███████████████████████████████████████████████████████████████████████████████| 461/461 [00:01<00:00, 325.19it/s]
Processing metadata.
Finished processing metadata.
Renaming files.
100%|████████████████████████████████████████████████████████████████████████████████| 461/461 [00:23<00:00, 19.47it/s]
Type: Archived
Type: Chats
Type: Messages
Traceback (most recent call last):
File "M:\OnlyFans\start_ofd.py", line 66, in
I wonder if we can set it to exclude the messages section of the scrape as a temporary fix, so we can at least get the feed stuff.
he's been aware of the problems but he's on another project before the fix. The project is getting better and better, not dead, check it here. https://github.com/DIGITALCRIMINALS/OnlyFans/issues/506#issuecomment-1182555394
well, i cannot downloading from fansly anymore too. BUT: Fansly shows me a message that im browsing to fast thru the site. i think it blocks because of the speed :/ maybee there should be some pause in it or so.
The "fix" is just to not scrape messages. If you have "auto_api_choice": "0"
for Fansly in .settings/config.json
, which would normally scrape all APIs, then set it to: "auto_api_choice": "1,2,3,4,6,7"
0
would normally be "All" - while 1,2,3,4,6,7
is every other API except "Messages":
Choose Contents: 0 = All | 1 = Stories | 2 = Posts | 3 = Archived | 4 = Chats | 5 = Messages | 6 = Highlights | 7 = MassMessages
(I'm not sure if all of these are even used, but might as well include most of them)
This seems to work for me at least, though of course it won't scrape messages, but it should at least scrape the posts.
works for me too, thanks :)
The "fix" is just to not scrape messages. If you have
"auto_api_choice": "0"
for Fansly in.settings/config.json
, which would normally scrape all APIs, then set it to:"auto_api_choice": "1,2,3,4,6,7"
0
would normally be "All" - while1,2,3,4,6,7
is every other API except "Messages":
Choose Contents: 0 = All | 1 = Stories | 2 = Posts | 3 = Archived | 4 = Chats | 5 = Messages | 6 = Highlights | 7 = MassMessages
(I'm not sure if all of these are even used, but might as well include most of them)This seems to work for me at least, though of course it won't scrape messages, but it should at least scrape the posts.
Worked like a charm
@Rakshae Just my opinion, but I think it might be better to keep the issue open for now since it's still a bug in the application.
It'll also increase the odds of anyone else with the same problem to find this issue (so there aren't duplicate issues created).
Agree, this issue is not completed, there is just a work around that restores partial functionality.
It was working fine last week, I haven't made any changes.