I would rather have more integrations with third parties rather than this.
My main problem is that I have to put a lot of effort to not use gmail for my business because most of third-parties (like CRMs) work only/better with gmail.
Do you mean to access Fastmail as a client for your Gmail-hosted inbox? How about using the fetch feature that moves all emails to your Fastmail inbox, and the 'send as' feature where you can send emails out from your Gmail SMTP via Fastmail. Those two features already exist.
Although when setting this up, Gmail really make you feel like they might pull support at any minute.
I wonder if Fastmail could log you in to Gmail in a way that's consistent with Google's security model, similar to how you can "log in with Google" on many services. I'd much prefer it over the app password thing.
Now that you mention it, I remember that's how Fastmail works today. They use app passwords for non-Google-hosted email inboxes, and 'login with Google' for Google-hosted inboxes.
What a bummer the website https://www.calligraphr.com is a subscription model. I could impulsively pay $100 to get my handwriting as a TTF font and be quite happy about it.
TFA goes into this in some depth: there's an option to subscribe for one month with a one-time payment. After the month is up, your account automatically reverts to the free plan and you get an email with your fonts attached.
The subscription is only for backups and ongoing changes - you get to keep your font forever. I think the author mentions that the whole experience cost them about $10
Lit's just a JavaScript library published as standard modules, so it doesn't require a bundler. Using Lit efficiently is the same as using any other library.
HTTP/3, import maps, and HTML preloads can make unbundled app deployment almost reasonable in some cases. You'd still miss out on minification and better compression form a bundle. Shared compression dictionaries will make this better though.
I can tell that the on-premises will be deployed on AWS accounts. We can manage the resources ourselves.
We have few fanouts that can be refactored. So Redis/Valkey for SQS is OK, hopefully it can also cover our SNS use case.
I am afraid Kubernetes is overkill for our lambda needs.
If we manage to bundle our whole app in one server and have only 1-2 clients on -premise, do you still suggest Kubernetes or a simpler rsync on all servers is enough?
Also, should we have a separate database instance for each client, or a Postgres cluster sharded? The latter seams more manageable.
> If we manage to bundle our whole app in one server and have only 1-2 clients on -premise, do you still suggest Kubernetes or a simpler rsync on all servers is enough?
rsync is nice and simple. Personally I'd say at least use Ansible, with its built-in rsync support. Then you can do more than just copy files.
> Also, should we have a separate database instance for each client, or a Postgres cluster sharded? The latter seams more manageable.
Depends on the size. Run postgres separately for your on-prem clients. For your cloud clients, I'd say keep them on the same server until you start to get over 100GB-1TB of data, then start to think about sharding. RDS gets super expensive, so sharing too early may be uneconomical.
> I am afraid Kubernetes is overkill for our lambda needs.
For just Lambda, I agree. But if running everything outside of AWS (i.e. racking servers) then it shines, because then you have your app, postgres, valkey, etc, all balanced between servers.
All your points are valid and can be included in the contract:
- We'll be the ones to choose the cloud provider,
- We'll take servers that are big enough,
- The client should upgrade their server according to our specs,
- Upgrades are mandatory.
Any idea what other (simpler) recovery plans we can have besides on-premise?
You could demonstrate the app working on a different cloud platform. If you can make it work on Azure for example that could satisfy them that you have a backup plan.
Thanks to LLMs, many of the spam messages I receive have synonyms for unsubscribe, instead of the magic word itself. I once talked to a B2B outreach company, and they touted the fact that they basically rewrite all of their emails in minor ways to evade spam filters. They pitched it as "personalization" but in reality it was just spam filter dodging.
I would say the "unsubscribe" rule still catches about 80-90% of the SPAM for me. (I thought the US had a law that any promotional email must include a link with "unsubscribe")
Then my "uninteresting sender" rules catch most of the remaining SPAM/uninteresting emails. These are accounts like "noreply" that automated emails often come from.
I had to set up a very special rule for a single company because they successfully dodged my other filters but always started with "Because you're a valued Vanguard client, we thought you'd be interested in this information."
This x100. I move it all to a folder called “Unsubscribe” and go through and unsubscribe from everything once in a while.
You can also make it a bit smarter by searching for the header “List-unsubscribe” instead. Less false-positives when someone forwards you an email that contains the word unsubscribe.
You have to be a little careful about this. That works for semi-ethical marketing departments, but for actual spammers it can send a signal that there's a warm body behind the email address, making it far more valuable and more likely to receive even more spam in the future.
A few years ago, I did the same and started unsubscribing from newsletters as soon as they arrived.
Now I keep only emails in my inbox that require action - everything else I archive or delete.
Despite being terrible, Yahoo mail has a bulk "delete all from sender and block" button that's way more convenient than Gmail. Found out when helping an elderly family member with 200K unread of spam. She's blocked thousands of addresses on her own now.
If you are interested in the topic, you can check the autobiography of the biggest manufacturer of LSD in history:
"The Rose Of Paracelsus" by William Leonard Pickard [1].
It is both poetic and fascinating. It's not an easy read but I recommend it.
There is the story in Dr. James Ketchum‘s memoir of a barrel containing 40lbs of LSD turning up in his offices. He worked on the Edgewood arsenal as part of the US military. This was enough LSD to make several hundred million people trip and worth nearly $1 billion at street value. Are you suggesting that Pickard manufactured more than that?
Where’s the demand for all that LSD. I can’t imagine more than 30 million people ever doing it and probably less than 2 million habitual users in the US.
The production of LSD was highly concentrated, the DEA claimed that after Pickford's arrest, availability dropped by 99.5%, it looks quite a while to recover. His supply basically was the entirety of demand at the time.
In Australia during university around the second the summer of love period we ended up doing acid at least once a week (mostly weekends) for near two years.
Probably about half time in the city at clubs and parties, and half time out in the forests and remote beaches.
Strawberry double dips were prevalent, a few other designs, microdots etc.
I'm pretty sure it gave me a perspective still today, that I would not otherwise have.
I don't think it caused any "damage". I still graduated with one of the hardest 4 year degrees and went on to use the degree in a career. I don't have any regrets about it all and the events that unfolded.
There were, however, many, many notable incidents and events, most of them more than little bit funny, even today.
I don't really remember expressly how, why it ended, it was like organic decay. I think it just ran it's course with availability of LSD, us having the time and places to do it, and eventually I think life just took over.
But, definitely, there were some regular repeat customers.
Mesmerizing number of views. I must admin I refreshed the page multiple times to see the count increase. If I increased the view count several times, I must admin I did not read the article multiple times.
My main problem is that I have to put a lot of effort to not use gmail for my business because most of third-parties (like CRMs) work only/better with gmail.
Fastmail team, how about a Gmail compatible API ?
reply