What can we do then? Stripe's own documentation recommends us to use Stripe Checkout because it's the most secure against card testing, and that checkout page is owned and operated by stripe so it's not like we can add custom card testing detection logic there.
But OP doesn't specify whether he's using Stripe Checkout integration (where stripe 100% control the landing page hosted in stripe domain) or other integration types (e.g. direct API call / embed which has higher risk). With Stripe Checkout integration type, you redirect users to a payment page hosted by stripe and have no ability to check whether the user is performing card testing there because the payment page is in stripe's domain, so stripe should be the one responsible with card testing prevention when using this discussion integration type.
I only started using Home Assistant about a year ago, but it has been rock solid to me. I even made my own (simple) custom integration and publish it on HACS and it's been rock solid (no API changes that break my custom integration so far). Could it be that Home Assistant is becoming more stable these days with less breaking changes on every updates?
Old reddit doesn't have many of those newer features in the main reddit ui that's geared to steer users to pay for premium. For example, old reddit users don't see avatars, which can be customized with premium stuff in the main reddit ui. Awards are also less pronounced. As an old reddit user, I'm sure you have no desire to spend money buy avatar gears and more awards. Users of the new UI got exposed to those stuff more often and thus more familiar and more likely to buy them.
Weather simulations and forecasting are very useful to society and practically almost all available public weather forecasting datasets were computed in some supercomputer cluster.
> Second, it is highly antagonistic to Google - who is probably still a partner to Lyft in many other aspects (advertising etc). Taking shots at your partners is generally considered bad for business.
Wasn't it Google that significantly raised their map api price a few years ago that prompted ride sharing apps to pursue open source solutions to replace google maps? Google took the first shot here. Other ride sharing apps are doing this. Grab is another ride sharing app that invest heavily in open street map.
It's like subscribing to Dollar Shave Club and later finding out you can't shave your beard with the blades already sent to your home when your subscription expires because the TOS said the subscription is for shaving x times per month and the blades are owned by the company. Complete nonsense.
Money can't buy everything. But if you lend the money and the borrower can't pay it back, suddenly you can ask something that normally can't be bought directly with money.
If they don't, they can't get new loans anymore, which will doom the country. It's really hard to grow your economy without foreign reverses. Even North Korea, a hermit kingdom, works really hard to grow their foreign reserve.
Chat clients like whatsapp don't allow you to link text to an arbitrary link, but instead will automatically turns text "attachment.zip" into a link to http://attachment.zip
For every request that generates an order, there are probably a dozen or more requests that doesn't generate any order. Also, OS these days are so bloated a $6 vps will barely has any memory left on startup before you actually run any workload on it.
That's how thinkpad trackpoint works, right? Hold the middle button and you can scroll horizontally and vertically using the trackpoint. It works on gnome/wayland, so maybe there is a way to configure generic trackball to behave like that too.
Not all X features are going to be implemented in wayland, right? If a feature has security implication, chance that it won't be implemented in wayland. It took them years to get screen sharing working, and that with a significant proportion of wayland users begging for it on every release. Chance that other insecure but useful X features won't be implemented in wayland unless they can be implemented with security in mind AND the features somehow got prioritized for development (or some l33t programmers suddenly show up with a patch and got accepted).