Even without knowing of these, they seem off. I'm not sure they are a benefit to illustrate actual human reviews, it makes these reviews feel off too, when you're aware of their source.
This might be a very personal thing, but I'd feel better reading reviews with just drawings of faces than this.
But if any part of that review is fabricated or deceptive, then you have done 2 things, you've successfully duped some people, and proven to other people that nothing on your site should be believed. The reviews can only be considered pure fiction.
If you don't want to show someone's real face for privacy or permission reasons, then don't show anything at all, or use some kind of graphic that makes no attempt to appear like a real person.
Same goes for the names. I have no reason to believe these are anyone's real names, and if they're not the reviewers real name, then why put any name at all?
There is no answer to that question that actually holds water. You can't say "because a name is more appealing because it looks more authentic"
If I had to guess, it’s a subtle manipulation with the idea that we more heavily weigh the statements and opinions of those who resemble us or are appealing to us
For webapps... Given that in that time there will be probably many vulnerabilities discovered, maybe it's better you just have backups and restore it from them once your credit card declines, given e.g. GDPR - or equivalents - implications. Assuming you don't have employees (if that, see below).
And if you die.. if you don't have dependants, who cares. If you do, that's basic business continuity operation.
Therefore, probably at the next billing cycle, as a dead man makes no credit card authorizations.
Please let me take care of it after you die!
Visa now has Visa Account Updater [1], and Mastercard has Mastercard Automatic Billing Updater [2]. It looks like American Express has their own too [3].
If one configures some form of automatic payment on their cards (AutoPay in the US; direct debits or GIRO in other parts of the world), along with using a "wallet" comprising multiple cards or bank accounts like PayPal [4] — it feels like paying for services would go on for longer than expected.
[1] https://usa.visa.com/dam/VCOM/download/merchants/visa-accoun...
[2] https://developer.mastercard.com/product/automatic-billing-u...
[3] https://www.godaddy.com/help/about-credit-card-account-updat...
[4] PayPal's more than happy to also take money from your bank accounts without your consent if your cards fail, if you have the accounts added, just to keep your bills paid.
No need to use cloud if you are careful.
2. Service providers automatically detected that the user is violating policies, and need to contact to re-activate the account.
3. Service providers update technique requirements or API, making running app failed.
Related: https://news.ycombinator.com/item?id=34954111
> What's the best way to preserve the artifacts of your own life and ensure they're disseminated after you're dead, or at least available, especially if you're a solitary person with no foreseeable descendants?
There should be some kind of service where people will keep your digital stuff running (until running out of the funds you gave them access to), like how lawyers manage one's estate.
18 months later, we started getting disk-space alerts as the DB file system filled up. As it turns out, we'd gotten rid of all of our alerting & monitoring except for the "last resort" fallbacks, which were starting to fire. The system had performed its task flawlessly for the entire time.
It worked perfectly up until 2019 or 2020; Crunchbase didn't change their HTML and the server would run the scrape on user load (no db/caching). I don't know what the billing situation was, maybe Dreamhost, and I had moved on to other projects and left the renewal to auto.
Finally, it died because of some required manual updates to server/PHP version for security or something.
Not too sure how COVID impacted things[0].
The "benefit" they had is having a direct debit (preauthorized payments).
Interestingly people seem to have taken the "hint" and stopped trying to contact them.
If it's hosted on the web, until the hosting company cuts off your service for non-payment.
Someone misplaced a comma (hello YAML), prod dies, yor site doesn't come up because never it happened to test the infra against the bla kout
