petronio

Doctors in the US generally won't prescribe medications they deem unnecessary, but there's a few issue that reduce the effectiveness of that. Two big ones are:

1. If an individual sees drug advertisements with particular symptoms they might think that they have them, which would make their concerns sound more probable to doctors when they complain about it.

2. In the US medical malpractice suits are a big issue, so that fear often causes things that might be considered on the edges of unnecessary in most countries to be converted to "maybe, I don't want to get sued if something does happen". This is magnified by point 1.

Take more people thinking they are sick, multiplied by multiple conditions, multiplied by doctors effectively excessively afraid of false negatives in diagnosing, and you have one big public health concern and some big marketing bonuses.

A prime reason why other constellations have been deployed or are currently being deployed, such as GLONASS (Russia), Galileo (EU), and BaiDu (China). India I believe also has their own, but it's not global, just regional.

Yes, but then it's all or nothing. In advanced mode you can have a global configuration to block all third party scripts and frames, and then allow scripts from specific domains (or neutralize the global deny for that domain, so that block lists still work). Particularly useful when you just want to move forward and Google's captcha is blocked, but don't want to allow all the other 50 scripts on the site.

Good old PEBKAC

The UK and France are both NATO members and have their own nuclear stockpiles.

That's a really good point, they'll be able to place VPN endpoints near their CDN endpoints and minimize additional latency, while still knowing the client's original IP for filtering, analytics, and providing geography based views. There's value added for both the VPN users and Cloudflare clients.

I also use Resilio Sync for distributing backups with encrypted peers, but I use Borg to backup into the folder for compression, de-duplication, and really easy PIT recovery. I've also added rdiff-backup on one of the encrypted peers in case the write host gets hit with ransomware and the backup overwritten.

That is also true, but that is something that can be mitigated and resolved with government policies. However, that is unlikely to happen effectively in societies that have a work as a core component of personal value as they will say "they're not working? Why should we help them?" At some point the policy changes will NEED to happen, but the societies with that core value will have a very difficult time adjusting as value systems can't be changed overnight like laws can.

People still fear the "robots will take all of our jobs!" dialogue. Many societies still have work as a core component of personal value, so the idea of people having to work less doesn't translate to "Great, I can let these robots do the work and I can enjoy myself" but to "I can't find work and so I'm a worthless disgrace."

I think that's fine, because then you know that at least the wallets still exist. I wonder how many bitcoins are forever gone from the early days when they were literally cheaper than dirt. I know I had some and failed to backup the wallet properly.

Minor addendum: Unless you decide on a plan whose cost is greater than the base plan provided by the employer, in which case the difference is deducted from your salary.

Having looked into this before, the big issue is actually the web scraping. If you don't mind pulling the data manually there's software like GNUCash that can do not only what Mint does but even more. Maintaining the web scraping rules for numerous banks is a full time job (probably multiple) in itself though.

There are a few companies that rank educational institutions and their programs by various metrics. "Top" programs are just the ones that tend to be at the top of those rankings. For MBAs, Harvard, Stanford, and UPenn's Wharton usually take the top three globally.

That's true if an IP only serves requests for a single domain. With ESNI it's now possible to connect to a server that hosts services for multiple domains without the domain being divulged in the clear on the wire.

I think it depends on who you're trying to protect against. While using DoT to a public resolver gives the public resolver the ability to build a history of your queries, running a recursive resolver yourself means anyone who's watching the wire (ISP, local government, etc.) can build a query history instead. Some people trust Google or Cloudflare more than those other entities, or figure that Google already knows pretty well what they're up to since Analytics is pretty much everywhere and they use Gmail.

The most useful option I've seen for trying to get the benefits of both has been rotating between a list of DoT resolvers, so none get all the history and end up with fragmented profiles. There's issues there since people access the same services and thus they'll get the full list over time if the software doesn't record who got what request and stickies it to them. There's always the option of doing it over Tor, but then you're introducing multisecond latencies to your DNS queries, which isn't exactly a great experience.

That makes a lot of sense, thanks.

Probably better to withdraw and eat the penalty then, inflation will make it worth peanuts by the time I'm 65.

I left the US recently with a few thousand in an HSA (a pre-tax account designated for healthcare expenses). I have no idea how I'm going to get that out of there now.

Actually, if we assume the previously posted £10,000/year, and three years for a Bachelor's they'd have a £30,000 debt. Assuming no interest, since it's only the amount over £25,725 that's taxed they'd have to average £25,725+((£30,000/30)/.09), or £36,836.11, over 30 years to fully repay, which I think is a much more reasonable number outside of HCOL areas.

I'm not sure if they account for inflation or have any fixed interest on the loans. 30 years without any would be pretty crazy.

After running into this a while ago when I was rebuilding my system and getting annoyed by all the different things that try to modify it, I ended up giving up and just setting the file to immutable. It has been working fine for the past couple of months as nothing seems to autodetect the flag and try to remove it.

  chattr +i /etc/resolv.conf

Either the server is sending pushes through APNS or the client is simply not getting messages reliably when the screen is locked or the app backgrounded, as the network restrictions very much apply to those clients as well (and to everything, to save power by sleeping the NICs).

Yes. It's sort of like using undocumented API calls: even if it's been unchanged for a decade, if it's undocumented it can change at any time without the usual deprecation warnings and versioning considerations.

Text output, particularly warnings and notes, isn't usually intentioned to be machine parseable and consistent in the first place, but rather is meant for humans to read and may be changed to be better read by humans at will.

There's a big difference between the two. Tax evasion is breaking the law to pay less tax. Tax avoidance is working within the confines of the law to pay less tax.

Putting money in a retirement account is a form of tax avoidance, but it was provided and is working as intended. The issue is not the definition, it's that legal loopholes allows unintended tax avoidance. The way to correct it would therefore be to close the loopholes, and many of the remaining loopholes span international borders and are tough to close without negative unintended consequences.

There's many valid reasons for accumulating profits, such as planning buyouts or expansions. That being said, sometimes it can be done for reasons such as waiting for a preferable tax regime. Due to that, some countries have a separate accumulated earnings tax that is similar to individual wealth taxes to disincentivize accumulating without a business purpose.

There's a couple. Some samples:

* If the hammer manufacturer decides not to sell you any, you'll still have hammers.

* If the hammer manufacturer gains enough power to fix prices, you won't be paying them exorbitant prices.

* If the hammer manufacturer or their country gets embargoed and you're unable to legally purchase their hammers, you'll still have hammers.

All the above grant you a strategic advantage since you'll still have the necessary tools to continue your business while your competitors won't (or will have to pay much higher prices for their supply of hammers).

Yeah, I'm waiting to see if when a child dies due to a disease that could've been vaccinated against but parents refused if a state prosecutor will try to slap them with criminal negligent homicide. I guess that will be the real test.

One of the options I've thought of (and I'm sure many others have as well) is to have all zones distributed in a P2P manner via ICANN. To not put too much burden on ICANN and keep things decentralized, have ICANN at the root of the DNS PKI and have all zones signed by the responsible party.

This would solve a few of the big problems we have:

* All sorts of MITM and evil resolver attacks would be prevented.

* Since DNS queries are local, there would no longer be a privacy concern with resolving a name.

* Even if the P2P network mechanism were to be blocked, since every host connected keeps a full record (though not necessarily with history) it can still be distributed via sneakernet.

* DNS updates are as fast as the network is, no longer depending on turtles caching all the way down.

* DNS amplification? That's gone, as resolvers no longer need to query external sources.

As many will quickly notice, we would likely still need remote resolvers for battery constrained devices as this would keep the network interfaces busy.

The one big political issue that would put a stop to this is that this would cause all zones to be world readable. Many people treat zones as something private and to them exposing the zone file is the same as exposing their network. My view is that if it has a publically routable IP then it is already exposed, but not everyone shares my view.

Are they disabling suites that don't use DH exchanges on the clients? Maybe I'm behind, but I can't imagine that happening on any major client.

At least for local development, disable the cipher suites with a DH key exchange and configure wireshark to use the private key.

I believe SCTP would fill in for that use case. For server-server communications there shouldn't be a problem, but I recall there's issues with client support & firewall rules, and I don't know if that status on that has changed if you need that. I also recall there being SCTP over UDP, but you lose some features there.