I hear what you are saying. But our society is pretty fucked up if you “deserve” something bad because you bought a product without imaging how the manufacturer can make it worse in the future.

The owners should be able to return the product if something like this happens, no matter how long ago they bought it.

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.

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.

Sort of…

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.

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.

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.

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.