Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For Instagram posts with multiple images, Is there a way to append a number specifying the order placement? #45

Open
Ecdldaiiere opened this issue Jan 31, 2025 · 2 comments

Comments

@Ecdldaiiere
Copy link

Browser(Chrome/Firefox/Firefox for Android): Chrome
Extension Version: 2.2.5
Reproduction of links:

These days a lot of Instagram posts have many images in a single post. When I download them, the file name is random and they become out of order. Is there a feature that could be added so that when I download images from a post with multiple images, it appends a number at the end specifying the placement of the image in the post?

For example in a post with 10 images, if I download image number 6, it would automatically put (6) at the end of the filename. Now when I look back on the 10 downloaded files, they are all in order instead of random like they are currently.

TheKonka added a commit that referenced this issue Feb 3, 2025
- fix: Download cover image only works on first column(#46)
- feat: append a number specifying the order placement(#45)
@HuskyZa
Copy link
Contributor

HuskyZa commented Feb 21, 2025

Hi @TheKonka, I just realized that this feature has just been shipped.

Questions

  1. Does this indexing feature also apply to Instagram Stories?
  2. Does the feature mean that the filename will be in the format of <post_id>_<img_index>? In addition, is this post_id unique compared to the original feature where the filename is guaranteed unique for each picture in the same post?

For Instagram post

Personally, I prefer the unique file name since it guarantees that if I download the same image or video, we will know from our local file system. But if the post_id is unique, then adding the index after the post_id will yield the unique filename, which is fine with me as well.

For Instagram Stories

We are okay with not using this index feature with the stories. I love it when IG Story media uses a unique filename.

But if we do use this indexing feature, how can we determine the IG Story index? Each story lasts only 24 hours, and the index will change constantly. Is the index determined at the time of the download? In other words, if the index is determined at the time of the download, we could have the same filenames where each refers to a different story, e.g., the 2nd story becomes the 1st story after the 1st story has pasted its 24-hour lifespan.

@HuskyZa
Copy link
Contributor

HuskyZa commented Feb 22, 2025

Hi @TheKonka, I just realized that this feature has just been shipped.

Questions

  1. Does this indexing feature also apply to Instagram Stories?
  2. Does the feature mean that the filename will be in the format of <post_id>_<img_index>? In addition, is this post_id unique compared to the original feature where the filename is guaranteed unique for each picture in the same post?

For Instagram post

Personally, I prefer the unique file name since it guarantees that if I download the same image or video, we will know from our local file system. But if the post_id is unique, then adding the index after the post_id will yield the unique filename, which is fine with me as well.

For Instagram Stories

We are okay with not using this index feature with the stories. I love it when IG Story media uses a unique filename.

But if we do use this indexing feature, how can we determine the IG Story index? Each story lasts only 24 hours, and the index will change constantly. Is the index determined at the time of the download? In other words, if the index is determined at the time of the download, we could have the same filenames where each refers to a different story, e.g., the 2nd story becomes the 1st story after the 1st story has pasted its 24-hour lifespan.

To address these issues and cater to users' preferences for unique filenames regardless of download instances later in time, PR #50 introduces an option to disable the indexing feature. When disabled, filenames will revert to the original functionality, providing unique filenames as we had before the introduction of the indexing feature in this version 2.2.6. And if the indexing feature is enabled, this feature introduced in 2.2.6 will be activated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants