Let me add that blocking outgoing requests to non-standard ports should also not break payment systems, yet I've encountered exactly that.
If your checkout system connects over anything but port 443, you done fucked up.
Ad block shouldn't break your checkout
151–160 of 204 posts
Re: Ad block shouldn't break your checkout
#152I remember trying to order from a pizza place that talked to a third party delivery site, I hit "Order" and the browser didn't do anything. DevTools told me it tried to talk to the 3rd party using HTTP although the page was in HTTPS, and the browser blocked it (this was years ago when browsers started blocking HTTP content on HTTPS sites). Modifying the submit URL to https solved the problem. I found it pretty funny…
I've gotten a little more paranoid in recent years and started blocking outgoing requests, just as a defense in depth. So I would prevent clients from connecting to anything but 22, 80 and 443 (to start; I added more for things like WebRTC and Amazon Streaming which uses AWS). I found a checkout that was connecting over some random port and wouldn't work until that was unblocked. Fucking annoying and I'm just left wondering how long until they have a security breach through their non-standard proprietary bullshit.
Re: Ad block shouldn't break your checkout
#153Earlier quoted context omitted.
> Yeah, but who are you? I am none of your business.
If you're trying to buy from me, who you are is literally my business.
And I'll happily fill out a form to tell you any information I feel is relevant to my purchase. If you want to covertly fingerprint and track me, I'll gladly take my business elsewhere.
Re: Ad block shouldn't break your checkout
#154Earlier quoted context omitted.
> And they'd be absolutely blind without GA. Good. > If you were actually in a physical store then they could look at you through the cameras. That's a gross idea to have.
You must think a store is just a place managed by genies or something.
No store owners I know manage their store through camera feed.
Re: Ad block shouldn't break your checkout
#155Earlier quoted context omitted.
That's not on TeeSpring, that's on Ublock Origin, which replaces the GA object with a dummy. The user is running code on their local machine that breaks his/her own ability to complete the sale.
And practically speaking, the back-stop is that if uBlock Origin causes too many high-profile websites to break, it'll get a reputation for degrading user experience and fewer users will install it. When two independently-owned systems on the web break each other, "who needs to fix their stuff" is a question more of social networks and business politics than technology. TeeSpring's "fix" could be to pop a banner that…
That's not how it ends up working, though. People just share screenshots or tell friends of the broken website and people stop using the website not uBO.
And there are sites that will throw up a banner that says 'Adblockers might break this, if you have problems disable your Adblocker and try again' which is pretty effective. Funny enough, in my experience, sites with that banner tend to work with uBO enabled (probably because they're testing it).
Re: Ad block shouldn't break your checkout
#156Earlier quoted context omitted.
The *adblocker crowd. I think I'm in the "technical crowd" but I've never used an adblocker. Running non-compliant extensions is your right, but the results don't need to be supported. I've run into this situation a number of times, although not with adblock. My advice has been to disable the extensions, or use a different browser without them.
> non-compliant extensions Compliant to who/what exactly ? Extensions are executed in a user agent, ie a software acting on behalf of a user based on the settings they prefer. If anything it's the website that's non-compliant with the user's choice.
HTTP, HTML, CSS, ECMAscript all have formal specifications.
It's your choice to use things that don't conform, such as IE11, but I wouldn't assume it's the server's problem.
Re: Ad block shouldn't break your checkout
#157Earlier quoted context omitted.
The *adblocker crowd. I think I'm in the "technical crowd" but I've never used an adblocker. Running non-compliant extensions is your right, but the results don't need to be supported. I've run into this situation a number of times, although not with adblock. My advice has been to disable the extensions, or use a different browser without them.
> My advice has been to disable the extensions, or use a different browser without them You're leaving out the option of "not using the website." Let's face it, nothing for sale on TeeSpring is essential. Just thank them for putting a roadblock on your silly impulse buy.
When I'm providing support, it's for my company's application, and it really is essential in those cases.
Re: Ad block shouldn't break your checkout
#158Your checkout shouldn't trigger ad block. Stop slavishly bowing to GA everywhere. I'm about to give you money. That's the only 'analytic' you should care about. I'm tired of being treated as little more than a data cow, always ready for milking. Just. Stop. To the person who ignores people who complain because their 'non-standard' browsers fail on their site, why do you have a site if you don't care about your users…
> I'm about to give you money. That's the only 'analytic' you should care about Yeah, but who are you? Are you an impulse buyer? Returning? Did you spend an hour on the product page? Did you jump between 20 different product pages? You can't deny that this kind of analytics can be very useful for user conversion and website design. And the site in question tries to do the proper thing, checking if GA works before try…
I always try to just these things based on physical analogies. The clear analog for visiting an ecommerce store is walking into a physical store with a shopping cart. Maybe the physical store has cameras or some other way they track people. In any case they probably aren't watching every single customer to determine which aisles they walk down, if they pick up an item without putting it in their cart, etc. Let's say they are doing that though, for the sake of analogy. It's strange to me that people are ok with that, but let's move on..
Now, since an adblocker doesn't change anything anywhere except on the end user's computer, the analog should be something on the customer's person, or some part of their behavior. So let's say the customer tries to avoid identification by wearing a hat, and they purposely grab every item and put it back on the shelf to mess with the data about their shopping habits.
Do you think it makes sense for the cashier to refuse to checkout anyone who is wearing a hat? Or if they spotted someone who picked a few things up without putting them in their cart?
Because I sure don't.
Re: Ad block shouldn't break your checkout
#159Re: Ad block shouldn't break your checkout
#160I am an author of a photo editor https://www.Photopea.com . Whenever someone reports a bug to me, I ask them if they use any site-modifying extensions. If they do, I ignore them completely, even if they wrote a long, detailed report. Web authors make websites for standard web browsers. I do not consider a browser with site-modifying extensions to be a standard web browser, and it is not my job to test my website with…
An update: almost nobody pays for Photopea, and all my reports are from users who use it for free. I fixed over 3000 issues so far, some took minutes, others took weeks: https://github.com/photopea/photopea/issues?q=is%3Aissue+is%...
A "popular" issue is, that people use an extension, which renames files saved by Photopea to .TXT. It is reported several times a week and every time, I tell people to disable an extension. They often argue, that it can not be caused by an extension, or even lie, that they disabled it and it did not help.
https://github.com/photopea/photopea/issues/3246 https://github.com/photopea/photopea/issues/3227 https://github.com/photopea/photopea/issues/3194 https://github.com/photopea/photopea/issues/3187 https://github.com/photopea/photopea/issues/3116 https://github.com/photopea/photopea/issues/3110 https://github.com/photopea/photopea/issues/3049 and so on.