>Frequently they need to close emergency services in major (& minor) cities at night due to staff shortages. The wait times for basic diagnostics is on the order of months (not days or weeks).
Part of this is COVID burnout. It wasn't this bad in 2019. Wife works in healthcare and sees the difference every day. Nurses crying etc.
Clasp is actually a word, and CLISP is part of GNU now so they should probably rename it something childish and cringe inducing like LURP, which is a recursive acronym for LERP: Universal REPL Programming or something.
>A lot of totally valid opinions out there about this, but I personally _love_ how the browser is becoming a very well-featured sandbox for shipping applications.
Unfortunately what's convenient for you as a developer is more often than not hostile and awful UX for me as a user.
A few months ago I wrote a comment on HN about algorithmic trading and someone emailed me about it. I sent him a reply from my self-hosted email domain, and I have no idea if he got it. I'm on a clean IP and clean domain, with a reputable hoster. I have SPF, DKIM, and DMARC set up correctly. Just last week I sent my gmail account a test email and sure enough it went to spam. There appears to be no rhyme or reason about it.
I believe the difference between people who say "email self-hosting is dead" and people who say "email self-hosting is trivial" is probably the volume of mail sent from their domain(s).
At my busiest, I was sending dozens of emails per day, but they were all from my work account. My personal account is pretty close to recv-only and probably averages an outgoing message count in the single digits per week. How can I reasonably keep an IP/domain reputation score fresh/warm if I send such a low volume? The answer is I realistically can't.
Self-hosted email remains an extremely difficult and time-consuming endeavor unless you happen to have some good luck, it seems.
Run your own email servers, but relay through there for better delivery?
Maybe this is what we need more of -- A class of mail system participants who exclusively maintain trusted IPs and do the legwork of trying to get through the gnarly systems set up by the other large email providers.
[EDIT] - "forward" -> "relay" for clarity
I don't know the solution but I know it needs to be discussed.
I don't understand using email alias in professional environments. At the time of replying to a forwarded email, will make you look very informal, as you would have to use your gmail address now. I wonder will it break the threading as the recipient now receives the email from gmail while at the time of sending used your personal domain.
The idea isn't actually to use an email alias -- it's to use an email relay.
Sorry if it's confusing (email as a whole is kind of confusing at first glance) -- relaying SMTP through a different server is kind of like using a VPN or a proxy.
Services like ImprovMX and Mailgun can be used for aliasing emails, but they can also just be used to deliver your emails for you (no aliasing to a new address).
The idea is to send all your email (like web traffic through a VPN) to those services.
All my incoming email goes to mailgun, which then forwards it to gmail. It's a so-so solution; it's cheap, extremely simple, and has catchall by default.
The big problem with this, is that gmail considers all messages forwarded to it as coming form the forwarder, not the original sender, and therefore spam harms the reputation of the forwarding domain.
But I don't understand how to configure mailgun to relay messages to gmail instead of forwarding them? Can you explain?
GMail understands ARC ("Authenticated Relay Chain"), a technology that signs a chain of deliveries, which is supposed to allow the right party to be blamed for spam. I don't know if any of these email forwarders respect ARC signature chains, but it would obviously be to their benefit if ARC's attributions were more widely recognised.
Postscript: Neither the Improvmx nor Mailgun sites have easily found information about ARC. It's a relatively complex and not widely used technology; nonetheless, the point I made about its adoption being in their interests stands.
Almost certainly a large part of your problem is that your individual IP address is in a shared net block that has other neighbors that have historically been a source of spam.
Unless you can get hosting at an ISP that does not sell low budget, commercial virtual private server, virtual machine or dedicated hosting to random people with $20 and a credit card, this will be an ongoing problem.
>The author seems under to be under the wrong impression that Mastodon servers are isolated communities (and therefore compares them to subreddits). This is incorrect. Mastodon is a platform where a server of your choosing hosts your account, like an e-mail provider hosting your inbox. From that account, you follow any other account on the network, regardless of which server hosts that account. Everyone you follow appears in your home feed, and everyone who follows you receives your posts in their home feed.
I've been aware of Mastodon pretty much since its inception and I had no idea that this was the case. The messaging really needs improved.
>I've been aware of Mastodon pretty much since its inception
You must be part of an exceptionally small minority then. I, too, have known about Mastodon since it's inception, and this was not news to me. As another commenter said, a debate during that time was that users were beaten over the head with too much discussion of federation and instances.
This is always how it's worked, and it's nearly impossible to join any instance without following & interacting with people from other instances on a daily basis. It's like the one thing about Mastodon you can't escape knowing about even if you actively try.
>This is always how it's worked, and it's nearly impossible to join any instance without following & interacting with people from other instances on a daily basis. It's like the one thing about Mastodon you can't escape knowing about even if you actively try.
I don't use Mastodon, so perhaps that's why. It always seemed like a Twitter clone except with fewer people and, importantly for this particular discussion, where you can't interact with anyone.
Guess I was mistaken, but that's why I never bothered to learn anything further about it.
The sixth sentence on the project homepage: "Joining a server on Mastodon provides you with the power to communicate with any server across the globe."
Really? Their biggest donors are large and extraordinarily profitable tech enterprises. (Like Google, Microsoft, and Facebook)
And thus the success of BSD-style licensing is thrown into sharp relief. (Also the fact that you or I can go use it as much as we want for free and do whatever we want to it.)
The flip side of course is that improvements also come at the pace of volunteerism, and there are no boardroom meetings where a manager tells the BSD developers that they didn't type enough lines of code that week.
If a corp wants a feature improved or implemented if it doesn't exist, they will have to pay someone and then they have to decide whether they will contribute it. If they do not, then they have to maintain a fork themselves which requires ongoing resources.
At the end of the day, I don't think it really matters that much. The corps are providing a service not a software application. If they weren't using BSD, they'd be using something else.
Part of this is COVID burnout. It wasn't this bad in 2019. Wife works in healthcare and sees the difference every day. Nurses crying etc.