But yes for outbound email, if you can't control reverse DNS you will have pain. (Inbound is totally fine) You can in theory just use whatever hostname the ISP's reverse DNS resolves to however you will get some spam score (or be rejected) as it doesn't match your "from" domain.
Outbound email is a huge pain really no matter what. Unless you have a long-term lease on the IP and it isn't in a bad network you really have to pay someone else if you want reliable delivery.
Yeah, it is very important to consider how dependant you are on third parties. At the very least the more dependence the more power they have over you. But also how screwed you are if they just go under.
If you use SaaS they can interrupt your use at any time and you can only react (for example demanding a reversal or lawsuits).
If you host closed source software they can't interrupt service on an existing contract but can legally require you to stop using it if they don't renew the contract. (And if the company goes under you can likely get away with using the software as long as it doesn't need code fixes.)
If the software is open source you can continue using the software indefinitely including making code fixes. (Maintenance may be expensive as it is now your problem but that can be costed and an exit plan made if required.)
Yeah, I finally pulled the trigger and moved to my own domain from matrix.org. Man, it is just so much faster. Which is sad, because the performance is pretty bad. (Element Web seems to do some per-room request as part of the initial loading screen which is obviously not scalable) but getting off of matrix.org is a huge performance improvement.
That being said there is nothing really wrong with matrix.org. The problem is really public rooms. People will join and spam. It is true of any protocol (have you heard about email?) but Matrix definitely needs to (and they are slowly working on) make it more expensive for spammers.
/favicon.ico is the only "default" URL. /favicon.ico is usually not an actual "icon" type anymore but PNG or JPG (but with the same URL). Other than that you need to load the HTML and check for Link headers or <link rel=icon> elements. While URLs like /favicon.png may be popular they aren't part of any actual protocol.
You can just hope that /favicon.ico works. But 1. it often doesn't and 2. it is often of low quality.
To find a favicon on a modern site you need to load the HTML and check Link headers and <link rel=icon> elements. However you likely can't do this client-side for most sites because of CORS. So you need some server (at the very least to strip CORS). That lets you get the URL but 1. you probably don't want to have connections to external domains for user privacy and 2. some domains will have hot-link protection so you need to fetch the image via your server. You will also want to consider different image formats and sizes to serve the right image to the right client. On top of all of this the site may be using some sort of bot protection which you will have to fight. Google is almost always whitelisted. The site may also have temporary outages so having a cache would be nice, especially if that is almost always populated before you even know the domain exists.
At the end of the day you do want some sort of API. And while it isn't complex it isn't trivial. So it is nice to just let Google handle it. (Other than tracking risks, but you could proxy Google's API.)
Its a problem but it isn't a major problem. I am using rspamd without any sort of exotic configuration (basically just enabling things that are provided, not my own rules) and I only get a few spam messages leaking through a week. Maybe slightly worse than GMail but not considerably slow.
IMHO the only real missing thing out of the box is contacts checking. Which is a huge thing because it is great to have reliable delivery from contacts. But my false-positive ratio is so low anyways that it isn't a big issue and things like the known_senders module mostly mitigates it.
Yes, blocking port 25 outbound is incredibly common by default. Even on some server connections. It is probably better overall for exactly the reasons that you mentioned.
Or just don’t self-host email
IMHO this is a bit overblown. Hosting inbound is fairly easy. Mail senders (probably for the worst) are very forgiving even if your TLS cert is expired you will probably get mail. Plus senders are supposed to retry for days if you have downtime.
However it is unfortunately true that due to spam sending is a huge pain because IPv4 reputation is a huge component. Sure you can get GMail to trust your domain after a month or so of sending if you have decent volume. But other providers who you may mail once a year are just going to go off of IP reputation. However email was basically designed for forwarding and you can use a service like AWS SES to forward your email from a trusted IP pretty easily. If you are low volume (like personal mail) there are tons of services that will do this for free.
But holy shit a marvel of marketing. Better be a case study in business school. They had little to no actual implementation for years and years but are still the go-to name for autonomous driving and selling subscriptions to something that doesn't exist. Absolutely wild.
Off topic. But I can't help but rate the trash cans.
1995: Excellent can. Obviously not that many pixels to work with but it is clear, legible and clean.
1998: I mean its fine, but a bit of a downgrade. Why so much black? Especially that top rim that apparently was painted black. The shading on the arrows also just hurts legibility, why do 2D arrows have shading anyways?
2000: Nope. The only good thing about it is that it is throwing away Windows. The shading is to simple arrows are strange colours and lacks a sense of depth.
2001: I don't love the theme but the execution is great. It looks clean shiny and bright. The only real weird thing is the bag inside, it is a bit strangely round despite seemingly not going over the edge.
2006: This is a nice refinement of the last one. Cleaner look, skip the bag, more realistic trash. This is the second best executed after 1995.
2015: This one is bland and lacks contrast and detail. The arrows are also oddly stubby for some reason. It's not bad, but also not good.
This is the advantage of decentralization over federation. IMHO the fact that Lemmy is only federated really hurts it. Not so much for user accounts (in theory these can be backed up restored and moved. Not ideal but not awful) but in that communities are tied to servers. When the server a community is on goes away it is hugely damaging to that community.
And I would go so far as to say that nobody who is buying 36 TB spinners is doing offsite backups of that data.
Was this a typo? I would expect that almost everyone who is buying these is doing offsite backups. Who has this amount of data density and is ok with losing it?
Yes, they are quite possibly using tape for these backups (either directly or through some cloud service) but you still want offsite backups. Otherwise a bad fire and you lose it all.
I don't think the target audience of this drive is buying one. They are trying to optimize for density and are probably buying in bulk rather than paying the $800 price tag.
with no changes to the salary they received during the production stage
But this just isn't how it works. These people aren't paid minimum wage. This will definitely be played in salary negotiation as part of the compensation and will almost certainly result in less base salary.
So now the studio is shifting some risk onto the workers.
I don't know if I really buy "not doing much of the work". Middle management maybe but to own and run a company is serious work. Especially starting a company is huge risk. So if you take the risk you get a lot of the reward.
IMHO ways to help even this out are:
Higher taxes on the wealthy. Keep that progressive tax curve going (and not regressing). I think these people do deserve to be rewarded, but up to a point. Honestly I think the tax rate should approach 100% as you approach the very highest percentile of income.
Universal basic income. Make it so that people don't need to work. They get to choose to work when the compensation is worth it to them. This makes explotation much harder and makes it much easier for people to negotiate fair compensation (whether that is salary, profit sharing, a mix or something else).
I would also like to see some way to change the natural goal of a company from "make as much money as possible" to "bring as much value to people as possible", but I think these two things would be a good start.
It is incredibly hard to define each worker's contribution to any particular profit.
It means that the worker's compensation depends on the overall success of the product which may have little to do with their work (for example bad management tanking a project or it getting cancelled before release).
Accounting can move profits around in a lot of cases. Look at how every movie makes no money.
In many ways having it be a transaction (work x hours get paid x dollars) is nice. I means that the employee knows exactly what they are getting upfront.
Reverse DNS is different than static IP.
But yes for outbound email, if you can't control reverse DNS you will have pain. (Inbound is totally fine) You can in theory just use whatever hostname the ISP's reverse DNS resolves to however you will get some spam score (or be rejected) as it doesn't match your "from" domain.
Outbound email is a huge pain really no matter what. Unless you have a long-term lease on the IP and it isn't in a bad network you really have to pay someone else if you want reliable delivery.