base

The page needs some code examples. It's just marketing talk, needs to be more oriented to it's audience.

Akismet is a paid service and their apis are tailored for comments. An advantage with comments is that you can just mark as spam if some contents have dubious links or keywords.

An issue you have in many forms (e.g.: login form) is that there is limited data to decide if it's a real user or a bot.

That's what most big e-commerce websites already do. From the moment you have a login the content is personalised to you.

Drug Checking is also done in some festivals in Portugal, example: https://boomfestival.org/boom2023/guide/kosmicare/#:~:text=D....

The Next Web: https://thenextweb.com/

It's amazing the impact this had on the stock value of the company: +25% at the moment.

Service Health Status: https://status.cloud.google.com/incidents/dS9ps52MUnxQfyDGPf...

Depending on the app might not have better performance. The reason is that a host with more connections might not be using more resources than one with less connections. The busy connections might be waiting for a reply from an external service.

There a lot of ways to reduce, just some ideias: turn on 3dsecure authentication whenever available. Check user location vs card location. Validate cvc code and postal code. Check for user activity and user signals (user agent, screen size etc) on the website, and other methods.

Would be interesting to study if there is a correlation between layoffs and remote work and employee churn. It's easier to layoff people if you don't have a connection with them.

Better to correct the title. It's 10% of 7000.

With online payments I had a different experience. Tried to pay in a store that had coinbase payments with a binance account. So many issues:

- The QR code to pay didn't work with the binance app

- Had to find a way to copy the hash tag of the account from desktop to mobile to pay (luckily if you have a macbook pro and iphone this is easy)

- Initially chose the incorrect network for payments on binance so the transfer didn't go through. Had to read online which network to select.

With a card payment is normally just putting the cards details and in a few cases do an additional authentication.

They workout the issues like everyone else, and at a certain size the issue is minimized as you are either in several whitelists or human moderators recognise your domain.

Most of those services also let clients setup their own domain name, so a ban is a more of a inconvenience to deal, than business critical like in OP case.

I don't have a specific solution for you, but I also run a domain with some thousands of subdomains and is always a fight to not be banned from Google, Meta, internet operators etc. Sometimes is enough one bad actor under one of your subdomains to have a full ban on the whole domain.

What I suggest is for your and your clients to contact Meta through the Business Center support. Their support for paying clients is much better. I would also recommend you become a Meta Business Partner if Facebook/Instagram is important for your SaaS.

Is there an easy way to have ClickHouse Cloud ingest data from MySQL hosted in Amazon RDS?

I think that's one of the reasons, but the main one is economical.

For a long time they dealt with the free accounts, so in a way they have already a lot of protections in place, and if they wanted they could keep the existing free accounts and just not accept further signups for this account type.

If you need to access the client IPs for several reasons (throttling, analytics, security etc), be aware that AWS Global Accelerator still only supports IP preservation in some specific setups: https://docs.aws.amazon.com/global-accelerator/latest/dg/pre...

There are a lot of options in e-commerce, all of them with thousands of shops: WooCommerce, Magento, Jumpseller, Bigcommerce, Prestashop, Wix WooCommerce etc...

In small business stores most users checkout as guests, so the website only has enough info to provide a shipping estimate after they have your address.

The issue a lot times is clients, for example if you work with small business.

I noticed a similar thing happens with their regional offices, while Google and other companies show their branding outside the buildings, in buildings with FB offices most of the times you don't know there is one just by looking outside or even at the building reception. At least this was the perception I had from the ones I have seen.

Most of there APIs are for preferred partners only, see for example their ecommerce, whatsapp or events apis, almost nothing can be accessed by a programmer working on his own.

io1 also has a slight better performance than gp2

If you have cross zone load balancing disabled and you only have one instance per AZ, how do you ensure that when an instance is down or during a deploy, when not all AZ might have instances, that you don't have downtimes? Cross zone load balancing in NLB seems a must to me if you are constantly deploying new targets.

Portugal have needle exchange programs and places with health practitioners for people to shoot drugs, this last point was very controversial when it was implemented. Nowadays there are even mobile sites for this: https://idpc.net/alerts/2019/07/inside-portugal-s-first-mobi...

Denmark has 18 deads per 1M people, on the european situation I would it's on the average. Infections started much earlier in Italy and Spain, most of the other countries had the advantage of learning from these 2 and having the time to prepare.

Currency conversion fees are also quite cheaper on Adyen 1.2% vs 2% on Stripe

There is the old AWS Beanstalk https://aws.amazon.com/elasticbeanstalk/

We switched from stripe to local payment gateways in some countries because some banks automatically convert any charge by stripe to USD making it more expensive for the end client and refusing in some cases the charge, when in local gateways everything goes through in the local currency.

Additionaly stripe charges their 2.5% to 3% + 2% conversion fee making it impossible some business models that are low margin.

We used other payment gateways before Stripe.

We built the abstraction around the requirements for our business model, although after some iterations it became similar to the model used by Stripe (customers, sources, plans...). We support saved payment options and on them we do recurring billing and one-stop payments.

A user for us can have multiple sources and a source is a saved external card or payment method, in the case of Stripe a source is a combination of the Stripe customer id and Stripe source token.

Most payment gateways support some kind of token that represents a saved card or similar on which you can do a charge.