webcompat-bot
commented
4 years ago Thanks for the report, but this is not a Compatibility issue.
For this project we try to focus our effort on layouts, features or content that works as expected in one browser but not in another. Closing the issue as Invalid.
URL: https://theinstaprofile.com/instagram/jessiej
Browser / Version: Tor Browser 68.1.2.Oesr (32bit)-Firefox 68.0 Operating System: Windows 7 (IE11) Home Premium 32bit Acer Aspire Tested Another Browser: No
Problem type: Something else Description: Hi!... In the website called, theinstaprofile.com/instagram/ (add the celebrity or other identifier at the end of the URL string)... incidentally, an "Instagram-like spinoff (created-- I assume-- to provide netizens with a form of the PUBLIC INSTAGRAM that/ which Instragram no long provides)"... I used to secure a segmented strip of image and/ or brief micro-video panels (called "STORIES"!) inches from the top of the screen, with rows of "micro playing card-sized" image and/ or brief micro-video panels beneath these. Now I'm receiving one or the other, neither (with a popup stating that the "Account is Private"!), "Discovery Users (celebs tagged to a highlighted celebrity)" or the full options... and with inconsistent "help" from my Tor Browser's "New Circuit" menu option! And frankly, and re the latter, there is no SOUND RATIONALE for a NUMBER of Account Holders to be jumping (consistently!) from "Stories" only, "Personal Cards" only, neither, "Discovery" and the "Account is Private" within a couple of secs of hitting, New Circuit!... unless, and of course, the MANY Account Holders (and sometimes, dozens of Accounts!) are all (coincidentally, and simultaneously!) BIPOLAR (or should I say, POLYPOLAR!)! To sum up... I don't know whether this is a spiteful targeted Instagram attack, a Net/ "network targeting" of my very use of Tor's New Circuit (only recently deployed with the URL in question), theinstaprofile's response to my use of Tor's New Circuit, or, theinstaprofile's recent response to a "flagged, tagged and bagged" polluted Tor IP Address! And, in the latter case, there is little I can do to correct things, as tapping New Identity or closing and reopening the Tor Browser will only result in the issuance of another corrupt IP Address!... i.e., if the "IP Address checking sites" that/ which I've used to check my-- ironically said!-- CHECK.torproject.org homepage-issued IP Addresses are any indication! Incidentally, just because a Tor user cannot see one's assigned IP Address (and, therewith, have it checked against a database of FLAGGED IP Addresses!)... because one has chosen not to use check.torproject.org as one's homepage!... doesn't mean that the problem (the ABUSE!) has gone away! It just means that the latent cause of the cyber victim's victimization is hidden from the victim's sight... and who must then INVENT an alternative explanation in one's head, for having "cyber doors" slammed in one's face, and otherwise "flagged, tagged and bagged" by networks and websites alike! But I digress! I fear, that CYBER ROAD-RAGE, CYBER DRIVE-BYS and CYBERJACKINGS might become real concerns on the info-highway!... and what these might entail, is anyone's guess! Steps to Reproduce: Greetings!...
To add a footnote to the problem tied to the Tor-Firefox Browser (downloaded from: torproject.org/download/languages/... their STABLE 32bit release), I would throw in the ensuing nonsense that/ which I received when I switched to the Alpha (test) 32bit Tor-Firefox Browser release (downloaded from: torproject.org/download/alpha/)... the latter, an ongoing EXPERIMENTAL VERSION of the former STABLE release. And believe, or not, the Tor-Firefox Browser behaviours I'm citing are CONSISTENTLY REPEATED by the respective releases!... i.e., the STABLE release now only gives me the problems I've citeed (i.e., within the last couple of weeks), and the ALPHA release only gives me the following problems (i.e., within the last couple of weeks)! WEIRD! And I've switched between the two a number of times... and always ensuring that all of the folders and files of one version are completely removed, before reinstalling the other! And I repeat, these respective distinct issues have only cropped up within the last two weeks!
I've received nasty Cloudflare-generated bot notifications afterupon my attempt to enter the said "Instagram alternative site"!... a notice that has popped up between me and the theinstaprofile[.]com) numerous times... and afterupon additional hits of this search engine search result, I'm sometimes able to get through. But on other occasions, I haven't been so fortunate. Indeed, of recent, this mysterious "Cloudflare robot" has kept me from accessing theinstaprofile(.)com altogether. And it will be interesting to see whether the other alternatives to Instagram sites have also been-- or, will soon be!-- targets of this aforenoted bot. This full-screen, "pop-up notification/ filter" has presented itself at websites that/ which haven't had such "filtering" previously, and that/ which wouldn't be inclined to use the "services" of Cloudflare! VERY suspicious! And so and thus, my comments to Cloudflare's main "pop-up text" is appended, in square brackets, in the presentation below...