PayPal Reviews

1. AnnaBenjamin

   6 months ago
   PayPal: More Frustrating Than Useful These Days

   I used PayPal for years, but lately it’s been one of the most frustrating payment services I’ve dealt with. Their customer support feels almost nonexistent — long wait times, scripted replies that don’t solve anything, and nobody seems empowered to actually help you.

   One of the worst things is how easily they freeze or limit accounts, sometimes without clear explanation, leaving you unable to access your money for weeks. And when you try to dispute a charge or problem with an order, it often feels like you get brushed off rather than any real help.

   Overall, PayPal used to be convenient, but recent experiences on safety holds, opaque policies, and unhelpful support make it feel more like a headache than a reliable way to pay or get paid

   🏁 Competitors: Google Pay

   👍 Pros:    Widely accepted online payment method that can be convenient for basic transfers.

   👎 Cons:    Poor customer service, confusing policies, and frequent account holds/freezes make it unreliable
2. Sandra-G

   about 4 years ago
   PayPal is cool

   I like PayPal, it has a high security standard. Except when I am the one suffering a chargeback for some flimsy reasons.

HTTP Reviews

PayPal mentions (1)

• Trying to activate PayPal just brings me to PayPal's website.

  (I live in USA) When I go to payments under my shopify account to add paypal as a payment method I am having trouble doing so. I first click activate paypal > activate paypal express checkout which directs me to a "security challenge" (confirm I am not a robot). Then it just brings me to paypals website (paypal.com/us/home). When I sign in nothing happens, I am just on my paypal homescreen. Source: over 3 years ago

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / almost 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago