HN user

mbar84

314 karma

mbar84.at.hn

[ my public key: https://keybase.io/mbarkhau; my proof: https://keybase.io/mbarkhau/sigs/zqLAR3WN4NphbN28dV84wSpaCX4N2BJEFr7ZTVFnnWg ]

Posts2
Comments226
View on HN

I want you, I want you, I want some of you

What about what I want? What if I don't want what you want? What if my criteria for a recipe is perfectly well served by an AI and I don't want your project to be my project.

Time is scarce. People don't owe you their time. If the LLM can save me time, and give an acceptable result, I'll use it. If I had infinite time (which I don't) maybe I'd participate in your project and learn to appreciate the nuance and humanity and whatnot related to cooking. Until then, I have other things to do.

The connection between sludge and distrust in government is worth emphasizing. The narrow minded and short term focus on metrics leads people in the managerial class to lose sight of reputational damage. Dehumanizing treatment may lose a corporation a customer, but what does it do to government and citizens?

If you receive btc in a transaction, the question is, when you consider it to be settled. In other words, how much energy is enough for you to consider it infeasible for an attacker to rewrite recent blocks so that you no longer are the recipient of some btc.

One way to think about it is to relate the total fees to the value of your transaction. If fees in blocks with a block height above the block with your transaction total $10000 (the security budget) then an attacker might be willing to spend that amount on energy to rewrite the chain. Another way to think about it is to relate the security budget to all recent transactions, assuming the attacker is the counter party to all of them (worst case).

In either case, there is no obviously correct answer to how high the security budget has to be on a per-block basis. The question is how long you're willing to wait for the security budget to accumulate and cover your transaction. If the block subsidy decreases and fees don't rise to replace them, then settlement time increases. Don't hand out goods to a counter party if the value of your transaction hasn't at least been met by the security budget. No need to wait longer than the point at which the value of all transactions of the block which includes your transaction has been exceeded by the security budget. An attacker would be losing money at that point if they tried to scam you.

That wasn't the reason to restrict block size. There is no way to scale the number of transactions on the main layer to anywhere near the level required to cover daily transactions. The bitcoin main layer was always destined to be for settlements between financial institutions anyway. Making any accommodations for use cases that are fundamentally unsustainable never made sense. Buying coffee was always going to have to be on a second or third layer, so restricting the block size introduces an incentive to develop those layers that are needed anyway.

Why would you give your product a quite specific name that's exactly the same as another product? "Core 2 Duo" immediately brings an Intel CPU to mind and will probably make it harder to search for anything related to the watch.

None of this is settled economic theory. Even just the conclusion in the second sentence is highly debatable. Capital investments are a market and it is completely plausible that they will clear like any other with a fixed money supply, just at a different price level than with an expanding money supply.

I doubt many people are making purchasing decisions based on Intel branding. Any kind of speed advantage has not been a dominant factor in the minds of most low information/brand influenceable consumers who are buying x86 machines. Everybody else looks at reviews and benchmarks where Intel has to show up with a good product and their branding doesn't get them much.

For some, it's an ethical imperative. The government is at best wasteful, often what it does with resources is harmful. If you can make sure resources are kept in private hands and used for further capital accumulation then we'll all be better off.

Possession is not illegal anymore. My understanding is, that police now cannot use mere possession as a pretense for searches of your car or home. If true, this is great progress from a civil liberties perspective.

Do you know which of these would be best suited to customization? I'd like to create a linux live distro only run a single application.

I have a microwave with two knobs: power and time. Both controls are haptic and I imagine the circuitry is the same as what might have been built in the '60s. It's perfectly fine.

It's not as if crypto has a particularly good reputation or the scammy nature of crypto is a secret. I wonder if your former friend has the same kind of personality that just as well would have deluded themselves into thinking they have some amazing insights into horse racing or sports. Without crypto, would they have found some other way to gamble away their future?

I'm trying to think how I would ideally set up such a system. The person traveling is in the best position to determine the most cost effective way to travel. Ideally you could somehow determine or negotiate ahead of time what travel expenses should be and then just pay that to the employee. Then they would just travel as they like and either pocket any savings they can find, fly cheaper if they value their time less than the saved money or pay extra if they value flying first class.

Good incentive structures are hard.

My hypothesis about open source is that it's all about tax evasion. I can write some software for others to use, not charge them anything and thus no tax liability is generated. If they do the same, we've generated value for each other without the tax man getting a cut.

One of the most wonderful developments of the last decade is the "Command Palette" UX pattern. You can have a tool driven predominantly by keyboard and also make all the keyboard shortcuts discoverable (display them next to the command in the dropdown). Maybe just let the UX guys do whatever they want, just so long as I can press Ctrl-K and type the first letters of the command I want to do.