petronio

In my view scores are relative to expectations, usually tied to price. A restaurant with a $50 meal and a 3 star score will likely have better food than one with a $5 meal and 5 stars on an absolute scale, but the people who got their $5 meal were happy with it and the ones with the $50 meal were disappointed.

If you have a license, take a road trip, they can be quite relaxing solo. Every morning when you wake up just look at the map and figure out where you want to reach that day and take it from there.

I'm not seeing how digital nomads have an additional negative impact compared to tourists though. If we're comparing not having wealthy foreigners vs having them, then yes, nobody will deny that has an effect on housing stock, but having digital nomads vs tourists is either a wash or a benefit to the digital nomads.

As for public resources, people who commute for work most likely use more than tourists, but digital nomads doing so would be an outlier.

The differentiation between digital nomads (people on a tourist visa/waiver) vs expats is an important one, as expats do get more entitlements to public services due to their legal residence.

Why do you expect them to crack down? The intent of disallowing working on tourist visas is to protect the local labor market. Digital nomads work for foreign companies and don't get location based market benefits that would be restricted to locals (consensus among the various communities seems to be that having local clients was a big no-no), so they add no pressure to local labor markets. In regards to the local economy, digital nomads are nothing but tourists.

Rather than cracking down, the current direction is legalization. Countries where digital nomads are common know what's happening and they ignore it as it's beneficial to them and are now legalizing to get an even larger slice of the pie (by attracting those who were previously fearful).

Others have mentioned the issue of housing stock, but regular tourists are actually more inefficient in that regards (very seasonal and short stays. Think about how many empty room-days most hotels have).

In regards to government debt (since the thread was originally about it), the government's debt is denominated in its own currency and the US is in the very cushy position where the USD is core to global trade, so the government can print itself out of any problem up to the point that the USD loses the trust of the international community. For the above reason, the number that makes up the US government debt is actually meaningless and is only good for political maneuvering around "increasing the debt ceiling".

In regards to the wider US economy, creating pain via high borrowing costs is the whole reason the interest rate is being increased. People and companies see the higher borrowing costs and change their mind on borrowing to spend, demand is choked, inflationary pressure reduced. The hard part is finding the rate that chokes it enough to control inflation while not choking it so much that you cause a recession.

Chrome has support for casting to Chromecasts. While not enough reason to daily drive Chrome, it does come in handy for the random video player that doesn't natively support it.

If the data is ordered by row as in your example (e.g. {1,a},{1,b}, etc), a relatively straightforward option would be to read all columns for the row and use the values as a key such that hash(columns) -> list(rowNum).

This may not give you the lowest number of leaves depending on your dataset. If you're looking for the absolute smallest number of leaves, you could use each column as an individual key and start intersecting their lists to see if that produces a reduced leaf count.

Should be noted that a significant portion of Berkshire Hathaway's usual cash pile is not for deal making, but as a backstop for their large insurance portfolio.

Venezuela is not only almost completely dependent on oil exports (extreme price fluctuations) but it's also not agriculturally self sufficient. It's not the only country with those problems, and they're not insurmountable problems, but it requires good economic planning to be able to handle downturns in those conditions, something Venezuela didn't have.

Argentina, on the other hand, has somewhat more varied exports (though soy and corn products are a large portion) and is agriculturally self sufficient. Unlike Venezuela, which had a "export oil, import everything else" mentality, Argentina has a large degree of economic protectionism and so they do have other sectors to help supply domestic demand to some degree.

There's obviously many other factors, but those are the largest ones in my opinion.

I suspect Sony will be getting $154M in cash rather than as bitcoin, as that's what was initially stolen. Whatever is left after the US government auctions it off stays with the US government.

Most likely, because if they refuse and it's infringing then it's them (WhatsApp) getting dragged to court for not following the court's orders. I suspect it'll end up similar to how most service providers handle DMCA takedowns: honor it without question. If it's invalid, the affected party can take it up with whoever submitted the request as far as WhatsApp is concerned.

It says "when provided with evidence", so I would assume it doesn't require active monitoring from WhatsApp and is more like a DMCA takedown request.

You can't stop it absolutely, but you can in effect by taking away the economic reason that it occurs. The primary reason the deforestation is happening is to open up land to produce agricultural products for export (primarily soy and cattle). If the importing countries cease to import the product, Brazil loses the economic reason to produce more (and as much) and open up more land via deforestation.

If a business behaves in a way you don't agree with it's perfectly reasonable to cease purchasing from them. Of course this move punishes soy growers who aren't responsible and turns them into collateral damage, but a move like this isn't meant to punish the soy growers as much as it is the Brazilian government (who are much better able to control the situation than a foreign power) for allowing the behavior to continue.

My experience has been similar. The most important thing that can't be easily resolved is if the server's IP is already on the blocklists, but other than that DKIM, DMARC, SPF, and reverse resolution together solves the ~~magical ritual~~ heuristics that make the big guys happy.

You can have multiple cranes working on a ship in parallel, like in https://www.youtube.com/watch?v=590t6mbebsc

You've really just described profiles, Firefox just needs to make them easier to use like Chrome. On Chrome they're easier to find, allow you to configure the profile icon, and give you the option to create a desktop shortcut to the profile. Mobile is probably more tricky.

The risk is much lesser, but there's the possibility of poisoning the binaries or release package.

There's also the whole "just because open source allows people to review code doesn't mean that they do" problem, but I don't expect that attack vector to be used by state actors because it would make the beneficiary of the attack too obvious to the public.

It is a fundamental problem, because you need specialized knowledge to understand what is being presented and asked of you in the UI.

The average user knows absolutely nothing about routing, most will throw their hands up or their eyes will swim if you so much as mention something like IP address.

They also know nothing about DNS and don't have to: because we always give them defaults that they never see and they go along with their lives.

As for wifi, once again, largely automated. Most people never change the default SSID and password. There's some manufacturers that will make a good UI, but it stops at the SSID and passwords because that's the extent of most users' understanding. Some users have a vague understanding that 2.4GHz and 5GHz is different, but don't know the significance of the difference. Channel, authentication type, and other options aren't given to users in those UIs because they simply wouldn't know what to do with it and people don't read manuals anyways.

A lot of the devices mentioned ("routers, printers, and self-hosted IoT devices") don't give ways to change the certificate. Besides, not every individual or company wants to or is knowledgeable enough to manage their own CA. For the audience in HN it might be an hour one evening, to others the instructions read like black magic.

On Intel: For some mitigations disabling hyperthreading will disable them as some vulnerabilities are only present with it enabled. That being said, the overall performance impact will be greater from disabling hyperthreading than by enabling the mitigations (though some vulnerabilities remain so long as you don't disable hyperthreading).

I wouldn't expect lower energy energy consumption from disabling hyperthreading: completing tasks faster allows the CPUs to reduce frequency faster.

Yes, and since it's just a URL even if you perform an audit it could have malicious code injected at any time in the future without your knowledge.

That's not necessarily true, there's been several security layers added these past few years. The YAMA LSM prevents user processes from reading the memory of processes that are not its children. It's already enabled by default in Ubuntu (but not Fedora, they decided to keep it disabled by default so that user gdb still works).

There are definitely still holes in the Linux security model, especially regarding file access (any user process having access to all the user's files is far too broad), but that doesn't mean we should just leave known vulnerabilities open, especially since an attacker may not have all methods of attack available.

To my knowledge it's always vulnerable on Intel processors, but not on AMD ones due to architectural differences. The nosmt option, when added to the mitigations option, should only disable SMT on vulnerable processors according to the Linux admin guide.

Thank you for that link, reading through the filenames was quite humorous. Agreed, what is considered "adult content" varies significantly between people, and whether children should be able to access what is considered medical/anatomical reference is a frequent argument.

For household usage I think it might be helpful to separate items into categories:

- Frequent use

- Infrequent use & stock needed

- Infrequent use & stock not needed

The first category I wouldn't worry about: you know how much you have stocked due to frequently using it, so just jot it down on a simple shopping list as you feel more stock is needed. Both short and long shelf life items can be placed here, you know when you need more sugar or toilet paper, or when something you use frequently might go bad soon.

The second category would be very good to put in a system like this, complete with expiration dates. These might be emergency supplies and medications, things that are easily forgotten about but shouldn't be lacking at any time. Keeping track and being notified of expiration dates would be pretty important.

The final category is personal choice. Since you don't need a stock of it, then it's non-essential. You could place it in a system like the second category, or you could just throw it on a shopping list when it's running out like the first.

You have to remember that companies compete with others for human labor. If your company moves to a city nobody wants to move to, you'll lose labor resources to another company (in the case of SF companies, highly skilled labor that's not easily replaceable and has high training costs).

While I also think companies should spread out more, the very fact that so many companies are paying the significantly inflated property and labor prices in the SF area shows the tremendous economic value in having access to that labor market.

Phoronix has done a few DB benchmarks on EPYC 2. https://www.phoronix.com/scan.php?page=search&q=EPYC

Don't forget that if comparing to old benchmarks, there's a bug with Intel's TSX now and the mitigations once again seem to take a nice hit if your database engine makes use of it.

In addition to what onychomys stated, there's also the matter of locality. If you were to assume they would be equally likely to exploit you, your ISP is more capable of doing so because it's local. For example, the VPN provider can sell your data to spammers that get filtered, but you ISP can shove spam in your physical mailbox.

I've had good luck with dehydrated (https://github.com/lukas2511/dehydrated)

It takes a file with a list of domains to check and you can write your own hooks to handle the DNS management and certificate deployment however you want.