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.

Of course nixpkgs has it. It was added a few years ago, I can’t vouch for if it is up to date or still working.

The owner of the domain owns DKIM. It offers no protection against that.

The only actual protection would be PGP because it provides your key as an identity rather than the domain itself.

The purchaser of that domain will be able to send and receive email from your addresses.

The biggest concerns here are probably:

1. The new owner taking over accounts that use the old email (either via password reset or email or by contacting support).
2. Sensitive personal information intended for you being sent to the new owner.
3. Someone spearphishing people you know from your old email address.

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 uh, wouldn’t recommend that with fire bars.

aren’t striping

I think you mean “are striping”.

But even with striping you have backups right? Local redundancy is for availability, not durability.

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:

1. 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.
2. 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.

I would be a bit careful with this.

1. It is incredibly hard to define each worker’s contribution to any particular profit.
2. 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).
3. 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.

Yeah mp4s with h264 will play basically anywhere if the audio format is a common one. Must be the most supported setup.

I’m pretty surprised that all of the audio formats work. I’m not so surprised that the TV has h265, although maybe a bit surprised that it is exposed to the browser. The container support is also pretty surprising. Unless your MKVs are so simple that they are effectively WEBM.

Or maybe it pops the link out of the browser into a dedicated media player which has decent codec support.

iDevices do expose h265 in the browser, but the container support is still a bit surprising. But then again WEBM is basically MKV, so maybe that is why it tends to work.

In China there is no such thing as a throwaway number (at least outside of black markets). All numbers require ID to acquire.

For the US it would be a bit different. VOIP numbers do exist but they are often also blocked by services (this isn’t black and white but there are services that will quite accurately map numbers into ranges like home/cell/business/VoIP).

But of course the assumption would be that if they start requiring phone numbers for WiFi access the logical next step would be to make all numbers traceable to humans.

There are a handful of common reasons.

1. The client doesn’t support the formats. Browser clients are notoriously picky not supporting some common video (for example few browsers support h265 and it isn’t generally considered web-safe) and audio formats. But embedded devices may also cause trouble if they don’t have enough CPU to do non-accelerated playback and don’t have hardware support for the codec used.
2. Playing at a lower bitrate. In that case you can transcode at the fly.
3. Remuxing. This is things like the moov atom where the actual codecs are supported but not the container or exact packaging of the file.

But yeah, especially if you are using a player with wide format support you may not need it.

IMHO for 2 drives you don’t want redundancy. (I assume that is what you want RAID for, mirroring?). The per-drive failure rate is so low that you are unlikely to encounter it and nothing you are running seems particularly availability sensitive. Having a bit of downtime to rebuild in the very rare case of a drive failure is fine. The extra storage space is way more valuable.