Folder with name of the account when u dl media

[Go2v]

Hello,

First of all, thank you for creating and maintaining this fantastic userscript! It really improves the Snapchat Web experience.

I would like to propose a new feature that would be incredibly helpful for organization: automatically saving downloaded media into a folder named after the user's unique username.

Currently, all downloaded media from different conversations is saved into the same default "Downloads" folder. This makes it very difficult to keep track of which media belongs to which person.

When a user downloads a media file from a conversation, the script would get the contact's unique username (e.g., sarah143.74, not their display name "Sarah") and save the file to a path like Downloads/[username]/[original_filename].

A friend and I spent a lot of time investigating how this could be implemented on the web interface, but we ran into some significant challenges. Our findings were:

The unique username does not seem to be present anywhere in the conversation view's HTML.

The conversation data appears to be fetched from the server using a Protobuf format, which makes it unreadable for a simple userscript.

We did find that the unique username is visible in the UI of the "Add Friends" search results. However, trying to automate a process to scrape it from there seemed extremely complex and fragile, as it would likely break with every Snapchat update.

Interestingly, we know that this exact feature is possible on mobile, as some modded APK/IPA versions of Snapchat have successfully implemented it. This suggests the data is accessible somehow.

Given this, our question is: with your deeper knowledge of the application, do you see a viable way to implement this feature for the web version? Or were we correct in our conclusion that it's effectively blocked by the use of Protobuf on the web client?

Thank you for your time and for considering this suggestion!

[mixtapejaxson]

It would be possible with the extension, however for the userscript i don't think that's possible to have it so that automatically. I'll look into solutions.

[mixtapejaxson]

for clarification on my previous statement:

however for the userscript i don't think that's possible to have it so that automatically.

What I am referring to is the limitations of a userscript vs. an extension.

Some other point(s) I would like to address:

When a user downloads a media file from a conversation, the script would get the contact's unique username (e.g., sarah143.74, not their display name "Sarah") and save the file to a path like Downloads/[username]/[original_filename].

This hypothetically would be possible short term, however Google may remove the ability for extensions to work with the FS, additionally we would need to make sure folders get parsed correctly depending on the different filesystems.

Interestingly, we know that this exact feature is possible on mobile, as some modded APK/IPA versions of Snapchat have successfully implemented it. This suggests the data is accessible somehow.

I wish we could impliment a lot of the features from things like SE, however the web version does not give us a lot of room to work with in terms of API accessability, and featureset. It might be possible through the web, however that has yet to be seen.

A solution:
We could impliment a system where it exports all saved images to a zip file that can be extracted, this way we bypass any future chrome updates that will block us from creating such feature, however this has it's own challenges too. For example it could not automatically add it to your FS.

I'm going to tag @appelmoesgg and see what he would like to do or if he has any other possible solutions we can try.

[appelmoesgg]

I've checked the documentation and it is indeed possible for an extension to download files to a subdirectory lf the Downloads folder.

I don't know if this is possible for the userscript, so I'd suggest to just save files in this format: [username]_[originalfilename].jpg/png/webp
for both the extension and the userscript.

Protobuf decoding might be possible but it takes a lot of time to research so we probably won't use that. There might be a reference somewhere in the code that we can use but we'll have to investigate that.

Have a great day

[Go2v]

Another feature to add would be automatic chat recording. Instead of manually recording text by clicking, you could activate an option that does it automatically when you open the chat.