Check if Instagram username is valid

Added check if entered Instagram username even exists. Please take a look and review it.

I can not apply patch in my local drupal environment and also on the simply test me site.

Because this patch is related to the #3021391: Check on configuration block if profile is public or private and if profile exists, you first need to apply that patch and then this one. The patch then applies and works. Tested through simplytest.me site. On my local environment I still can't apply the patch, so I'm marking this as needs review, so somebody else can also test it and confirm that everything works as designed.

Hi,

thanks for the patch and review. I reviewed the patch and on its own, it does not work, but as said by @DeaOm it works if you apply the patch from the other issue it works.

I would mark this as RTBC since it does what it needs. And as already mentioned these issues are part of the same problem.

Targeting correct branch now that branches have been fixed.

Patch needs be re-rolled to 8.x-2.x

I'll re-roll the patch!

@ipwa Hey, I was doing the re-roll, but I realized that what this issue propose to do already have. I tried to put a invalid Instagram username and the block don't showed to me, I don't know how it worked before, but I think it's already fixed, Am I right?

i talked to @ipwa about this issue so I'm unassigned so he can look at it again

I'll work on this :)

I installed the module and placed the block but it did not rendered in HTML. I tried in Drupal 8 and 9 versions. Leaving this "Unassigned".

Hi, I will try to work on this. =)

I did the following:

0. Installed a backward compatibility module.
1. Installed the module.
2. Added a valid instagram username.
3. Placed the block on the footer.
4. The block did not show.

I added an invalid instagram username and it does not show either.

After that I tried applying the patch, which did not work.

So I followed comment #5 and created a branch with the date of comment #14 of the other related issue.
This way the patch from #14 applies and the patch from #2 of this issue as well.

After applying both patches the validation prevents any username, valid or invalid from being entered and displays an error message about
the invalid username.

After that I tried rerolling the patch, but without much success.
There are conflicts when trying to rebase for a reroll that I could not fix.

Hi I wll try to do a reroll.

Hi I made a reroll but I used that patch as parameter https://www.drupal.org/files/issues/2019-01-07/instagram_without_api-che...

I followed these steps for to do a reroll (https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupa...)

With reroll I was able to apply both patches ( https://www.drupal.org/files/issues/2019-01-07/instagram_without_api-che...

https://www.drupal.org/files/issues/2019-01-17/check_if_instagram_userna... )

Please revise.

Sorry it's the right file.

I'll review this :)

I was able to apply the #20 patch, but the module is still not working properly. The method JsonService::retrieveJson always returns 'null', what makes the validation of the username always throws an error message. I'm leaving it unassigned.

It seems that Instagram has removed the window._sharedData object from the document returned from the GET `/{username}` resource, making it impossible for most of the data necessary for this project to be retrieved.

I'll try to work on this, over the patch #20.

It seems that Instagram has been blocking the known workarounds to access to users posts without the need of public APIs.

Any documented endpoints available requires authentication, and the known methods to gather user posts (i.e., the one used by this project), seems to either have been ended by them, or it sits around a very restrictive firewall.

This project relies on the existence of such methods, that can be deprecated at any moment, without notice.

#Instagram Without API

It is a very simple module that integrates with Instagram without API and creates a block containing your most recent Instagram posts.

I searched how other projects scrapped this information from Instagram without the need to authenticate, and the most reliable method seems to consume the web application by a browser, like using a headless browser automation process.

Here are some materials I've found about the issue:
https://www.reddit.com/r/webscraping/comments/uxt2ns/instagram_doesnt_sh...
https://scrapfly.io/blog/how-to-scrape-instagram/#scraping-user-posts

Forgot to unassign me from the issue.

Fixed as part of #3021391