This big warning gave me pause, too. Why not have a compression option that automatically checks the data after compression (by decompressing and checking against a hash of the original data), which would reduce the probability of undetected errors to that of a hash collision? i.e. like `7z a` followed by `7z t`, but in one command.
A "Message Echo" textbox that makes it look like you can get a response to a prompt without logging in, only to redirect to the sign-up page. Such a classic dark pattern - and such a sure way to get me to leave your site immediately.
I've literally taken one step on your website - the one your site design invited me to take - and immediately got tripped up. I'm not coming back.
Then the creator should have a sign up button, not a fake chatbox.
This dark pattern is reminiscent of those online test sites in the 2000's where you spend 10 minutes filling out some quiz, then get prompted for an email address to see the results.
Even worse, I've seen the JetBrains AI auto-complete insert hard-to-spot bugs, like two nested for loops with i and j for loop index variables, where the inner loop was fairly complex and incorrectly used i instead of j in one place.
GMail disagrees with you, because GMail users disagree with you. They are clicking "report spam" on your emails. Whether or not you think what you're sending is spam, the recipients think it is, and that's what matters. (Based on the other comments in this thread it's not hard to see why they might think so.)
Users definitely click "report spam" in large numbers on things that are not spam. At work we've long had problems of getting reported for spam when the only things we send are:
• A receipt when a person comes to our site and purchases something.
• Their license key if what they purchased requires a license key.
• Replies if they send email to customer support.
• If they have purchased an automatically renewing subscription we email a receipt after it renews or a notice that it was declined if the charge does not go through. This is required by the major credit card companies.
• If they have an automatically renewing subscription and they are on a plan other than monthly we send a reminder before it tries to renew. This is required by the major credit card companies and by the consumer protection laws in many jurisdictions.
> If they have purchased an automatically renewing subscription we email a receipt after it renews (..) This is required by the major credit card companies.
The problem here is that "we are legally required to send it" and "our customers want to receive it" aren't necessarily the same thing. I'd probably be pretty annoyed by those if I had more than a few subscriptions!
I have a really simple algorithm to reporting something as spam:
> Was this email solicited by me?
The author describes unsolicited emails and somehow misses the point that spam is a term for unsolicited emails.
The reminder email in your list sounds unsolicited, so I'd probably report that one as spam as well. I wasn't aware it was mandatory, probably because it's not where I live.
My transactional inboxes are mostly clean as a result. My "spam" inbox, however, is full of crap (the email I use to sign up to freemium services).
I would describe myself as strict and dogmatic about email etiquette and consent as they come, but I am with avianlyric about the subscription reminders.
Legal requirements aside — when I have an ongoing business relationship with a company, "we are about to take money from you again" is an expected, useful and welcome message.
Last week, my monitoring system sent me 20k emails in a few hours in response to a server attack.
When those hit my gmail inbox, gmail marked them all as spam. Myself, the user, did not mark them as spam. Gmail did that for me. But their reputation system is behaving as if 20k people marked 20k emails from us as spam.
In response to those 20k emails marked as spam, now our domain sender reputation with gmail is LOW, and our low volume of legitimate email with customers goes to their spam folders.
The gmail client gives me no way to unmark these messages as spam, except to click on each message, one at a time, and dig into a submenu to find the "Not spam" button.
Perhaps a stupid question, but why do notifications need to be stored in a database in persistent storage at all?
OK, maybe they can be stored until they're dismissed in case the battery suddenly dies, so they can be displayed again on next boot and are not lost, but it sounds like they are being stored long after they are dismissed.
This is the sort of economics that small companies face when working with large companies, particularly when physical things/CAPEX are involved. Large companies expect net 30/60 terms to pay you. That's much simpler for their accounting/purchasing department. This bureaucracy occasionally necessitates nudging, especially if the intermediary you're dealing with didn't set up the invoice request on time in whichever SAP/Salesforce/Oracle system they use.
This is usually the same the other way; many vendors will give business clients net 30. That's nice if you're a small company and need to plan ahead. But occasionally, because you're considered small (liability), some vendors will want the money up-front. So unless you're very careful with cashflow, you end up in situations where your main sources of income (big contracts) are coming in after you need to spend money on a widget to fulfill deliverables.
Depending on the situation, the contract can demand the client purchase/ship things and work doesn't start until you have them in hand. This is usually the best route as you now have an out, and it's not an unreasonable request, but it doesn't always pan out that way!
I took "good client" to mean, "is easy to work with/communicates well/knows what they want", not just "pays on time". The inverse being, the ones who don't pay on time were already a pain in the ass to work with.
There have been so many cases of Apple, Google, etc. doing this that it's hard to have any sympathy for them at this point. If it was some grandma who didn't know better that would be another story, but the author was surely aware
- that Apple *can* always *just* disable their account
- that Apple regularly *does* do that
- that Apple does not care about them at all
and they chose to bet their entire digital life on Apple's benevolence anyway. They lost that bet.
We need more stories like this hitting the mainstream news until even a non-technical person's reaction to this is "well, what did you expect?"
The number of monsters on the screen doesn't seem to affect playing speed for me, but when the wall of fire appears it slows down the game very noticeably. (Using Firefox on desktop.)
reply