They are legal if you follow the regulations. The problem with the “rideshare” companies is that they don’t. We should just call them “unregulated taxis” rather than pretending that they are a different service. I think just about every taxi company these days is on some app or another (often the same that call unregulated cabs in countries that actually got their shit together and banned the unregulated ones).

Nah it’s worse. Bitcoin actually has legitimate uses. (Yes, they are a minority of actual usage, but they exist.) NFTs are only useful for speculation, gambling and money laundering.

“Rideshare” is also the least accurate term used to dodge regulations. It is just a taxi/cab. You are paying someone to get you from one place to another. They aren’t sharing their ride, they were never going where you are going before you told them to.

I use https://difftastic.wilfred.me.uk/ which is well, fantastic. I have it set up as the default diff for Git and it is really nice.

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.

/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.

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.

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.

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.

lol, I assume he means 1000 Mbps aka 1 Gbps which is reasonable. Maybe even a little low as transferring files around fast is nice.

IMHO this isn’t really worth it.

1. x264 is very fast at lower profiles. Especially if you aren’t streaming across the internet often the size hit from the fast profiles is fine. Even if you are streaming over the internet it is probably fine. Getting a slightly faster CPU will also get you super far and is more useful to have lying around than a GPU as it will benefit most things that you do on the server. And worst-worst case a bit of CPU usage isn’t going to hurt much of the things that he is running (except maybe a game server if people are playing at the same time and you are really maxing out all of your cores).
2. Integrated GPUs are fine for a handful of concurrent streams. Especially the Intel ones which have amazing media engines.
3. Even if you are going for a dedicated GPU I would go with an Intel ARC. They are way better at media encoding and cost less.
4. You can always add a GPU later. Wait until you have a need and are seeing problems without.

While I agree, I think that getting more games on Linux is far more useful. When Linux is almost 3% very few studios will care much. If they can do a small bit of testing on Proton and maybe work around a bug or two they are far more likely to do that then make and test a native build. If this then gets Linux usage to 5, 10 or 20% that will drive more native builds.

So I agree that it somewhat reduces the incentive to release a native build. But I think that is outweighed by the benefits of making the Linux gaming experience better today which will have a greater impact on availability of native builds in the future.

poweroff or shutdown will work on almost every distro. Even systemd ones (they are usually symlinks but doesn’t really matter because they work).

Huh?

I’ve used Vim for a decade and I would be offended if it made any noise.