One in the hand is worth two in the bush.

Sell it. Invest that money in a less risky asset. You win no matter what that way.

I’m skeptical that you’re giving the full story

No, you’re right. There’s a much bigger story here. I was just trimming out a lot of it since I don’t normally run into people who can follow along easily. Akamai, for example, uses the proprietary AKAMAICDN record to allow the functionality of a CNAME. For example: foo.com AKAMAICDN’s to foo.com.edgekey.net (edgekey.net of course being the Akamai edge server suite). So someone using Akamai can do that to allow them to use the apex (but will still very likely have a www.foo.com CNAME foo.com setup to catch people who did a www anyway) Cloudflare uses CNAME flattening to “cheat” the CNAME rules by doing the CNAME DNS lookup internally and pretending to be authoritative for the request.

You don’t typical have your webpage itself delivered by CDN, you have your static assets delivered by CDN. Why can’t you put your static assets in a subdomain that gets a CNAME?

You can most certainly put static assets in a specific subdomain (and in fact, that’s how most setups are), but the CDN itself often requires handling the entire request at the beginning. You don’t want, for example, an A record at the apex pointing directly at your origin servers (terrible idea for security & performance; kind of defeats the purpose of the CDN), instead you want the user to connect to an edge server and have that edge server immediately serve the static content while the origin is contacted by the edge server for any non-static content that the user needs. This allows the CDN to do their cloud magic while your origin servers can do as little work as possible with as few people as possible. Effectively, you can block all requests to your servers that are not from your CDN. Many CDNs these days are also a major security feature.

There are many many reasons you don’t want to (or can’t) have the apex of your domain (what you’re calling the “default domain”) the primary domain name of your site. I thought you were going to argue in favor of like “home.[domain].com” or something.

The first and foremost issue is that if you wish to use a CDN, many CDN’s require a CNAME to function properly. You can’t have a CNAME share space with any other record (RFC 1912) which completely precludes using an MX record (for email) or TXT records for DKIM, SPF, and DMARC. (You need those for a secure email service). Having the CNAME sit as a subdomain of the apex (such as www) allows you to maintain those records in your domain while also serving people using that CNAME. (Some CDN’s such as Akamai even have special proprietary records that function like a CNAME while returning A records just to make this work)

Why not? (Serious question, I’m a DNS engineer so this is super relevant to me)

But notably, it does shield them from prosecution for crimes which are tangentially related to their official duties. For example, granting a presidential pardon is an official duty. Taking a bribe in exchange for that pardon would be a crime. But now the president is allowed to openly and blatantly take that bribe, because the bribe is tangential to their official duty, and they are therefore shielded from prosecution.

Not at all. While granting a pardon is an official duty, taking a bribe in exchange for a pardon is a criminal act. The decision does not shield the President from prosecution for such criminal conduct. Criminal acts are just as prosecutable as there were prior.

Excerpt from the ruling:

“As for a President’s unofficial acts, there is no immunity. The principles we set out in Clinton v. Jones confirm as much. When Paula Jones brought a civil lawsuit against then-President Bill Clinton for acts he allegedly committed prior to his Presidency, we rejected his argument that he enjoyed temporary immunity from the lawsuit while serving as President. 520 U. S., at 684. Although Presidential immunity is required for official actions to ensure that the President’s decision making is not distorted by the threat of future litigation stemming from those actions, that concern does not support immunity for unofficial conduct. Id., at 694, and n. 19.”

Unofficial conduct includes taking bribes.

Many experts disagree with the second half of your sentence, because ordering an assassination could easily be argued to be an official duty; After all, the POTUS is the commander in chief of the military. According to this ruling, ordering it illegally would be protected, because the illegality is tied to the official duty.

“Many experts” isn’t someone I can talk with or argue against. They’re just weasel words.

Ordering an assassination is illegal. It violates the fifth and fourteenth amendments to the constitution (as they deprive persons of “life, liberty, or property” without fair legal procedures and protections). as well as Executive Order 12333 in which assassination is explicitly deemed illegal.

Hey so there’s some echo-chambery stuff going on in Lemmy right now, so I want to provide some clarification:

1. The court decision did not create a new law. It provided clarity on laws already in place. Presidential immunity is not a new thing. It’s a well established power. See: Clinton v. Jones (1997), United States v. Nixon (1974), United States v. Burr (1807), Nixon v. Fitzgerald (1982), Youngstown Sheet & Tube Co. v. Sawyer (1952)

2. The court decision does not expand on the law either, it clarifies that:

The President has some immunity for official acts to allow them to perform their duties without undue interference. However, this immunity does not cover:

• Unofficial acts or personal behavior.

• Criminal acts, (to include assassination).

The decision reaffirms that the President can be held accountable for actions outside the scope of their official duties. It does not grant blanket immunity for all actions or allow the President to act as a dictator.

People who are giving opinions based on what they read on Lemmy instead of going and reading the supreme court opinion that is totally online and right here for you to reference are spreading misinformation and fear.

Hackers mad

Hackers mad

Hackers mad