Instapy: Feature Dump - Interesting ideas

[timgrossmann]

Just dumping a few feature ideas I collected from several people if you want to start one of the features as a separate issue and post a bounty, feel free to do so!

• Filters: this option lets you make filter people who act on them. (More important filters:
  Check gender, Skip private users, Skip accounts with a website, Skip business accounts, Select Languages, Black list, Stop words, Skip used accounts)

• "Success" percentage: Some graphs showing how effective a given quickstart configuration file is.

[converge]

Great ideas @timgrossmann !! It's a big step forward, resuming what you said:

"less calls to Instagram server and more effectiveness in the actions, bringing better results"

Is it time to have InstaPy versioning ? It would be great to have a stable version before this step. We could list all the bugs we wanna close, before add more features.

[timgrossmann]

@converge Yes absolutely!

That's why this only serves as a dump for feature ideas.

The most important tasks now should be to get InstaPy, as you said, on a stable version... I'll be experimenting with xPaths to check if there is an easy way to get the least specific path to an element which still only delivers a single element. This could lead to way less errors when it comes to finding and clicking elements on a page

[arjunmurali1993]

@timgrossmann Hi Tim, I've just started using your excellent software and I have to say it's quite impressive. Great work!! I haven't had the chance to take a look at the code yet though. I'll take a look this weekend to better understand how it works and contribute whatever I can.

I was running the program today and saw that after about 3+ hours it finished the process with results like Liked - 18, Inappropriate - 120. Wouldn't it be better to initially scrape and create a list of x amount of users who match the set criteria and then go about liking the posts? This would save a lot of time and prevent it from going into each user's profile, finding it inappropriate and then coming back. Please excuse my lack of understanding if I've assumed something wrong. I haven't actually seen the code yet and I'm just guessing what is happening behind the scenes.

[pilotdude]

Sorry to bump a (somewhat) old thread but I wanted to share some thoughts here.

In the vein of: "less calls to Instagram server and more effectiveness in the actions, bringing better results" I think we should be noting info about users when the script interacts with their page. Info like post id, number of followers, hashtags used, etc. I think so long as we are scraping the page we might as well collect some data we can use later. For example if we have noted that a certain person has 10k followers then the next time the script gets to a post by them it can check the local DB to see if the follower count is to high instead of needing to load their profile page. I know this is quite a lot of extra work but it would make things run faster, loading less pages and appear more random to the Instagram server.

[46960]

Lately people have been DM'ing my account to ask me why I keep following and unfollowing them. Some of them were really pissed off. I've also noticed that some have blocked me. Since it is not our intention to upset users, it would be really cool for the bot to not follow users we followed (and unfollowed) before! What do you think?

[timgrossmann]

@46960 If you'd read the readme you'd see that there is a times parameter with the follow function that keeps track of the people you followed and how often you followed them :wink:

This might not be implemented for all of the methods

[46960]

Thanks @timgrossmann! Does it also apply to session.follow_user_followers (which is the function that I am mainly using)? I like to follow the followers of targeted accounts (10 followers per account), so I don't know the name of the accs I will be following beforehand. The times parameter would be really helpful for this function too :)

[timgrossmann]

@46960 Feel free to open up a feature request issue for that and post a bounty on it.

[converge]

@46960 take a look at the new blacklist feature

[hestuppfodarn]

Hi,
We would love the gender feature. Would it be hard to do? Please make a bountysource and I will place some money.

[converge]

hi @hestuppfodarn , the BountySource link is ~https://www.bountysource.com/issues/50786183-feature-dump-interesting-ideas~ https://www.bountysource.com/issues/51869268-feature-request-filtering-gender, feel free to place some money and someone can work on it.

[timgrossmann]

@converge Maybe it's smarter to open up a separate issue for the gender feature.
This issue has to be closed in order for the implementer to claim the bounty.

[hestuppfodarn]

Would Also be Nice to have a “avoid business account”. We will place bounty
for that.

On Wed, 22 Nov 2017 at 19:11, Tim Großmann [e-mail] wrote:

@converge https://github.com/converge Maybe it's smarter to open up a
separate issue for the gender feature.
This issue has to be closed in order for the implementer to claim the
bounty.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/timgrossmann/InstaPy/issues/820#issuecomment-346431666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATJJeKaJgsPnr4cmEQb0-7829nUvSjPtks5s5GPUgaJpZM4QHDjG
.

>

---

Emil Esselin
([phone]

[timgrossmann]

@hestuppfodarn https://github.com/timgrossmann/InstaPy/issues/980

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this problem still occurs, please open a new issue