Recent submissions

Comment · 4 years ago
Bitcoin is as obsolete as POSIX. It's ossified, and not changing is a feature.
Comment · 4 years ago
- Why is KyuWeb limited to HTTP/1.1?

- This might be a silly question, but could you explain to me why did you pick a new header, instead of something like `Accept: text/kyu`?

Comment · 4 years ago
Regarding the distribution of users on Mastodon servers, the article seems a little biased. The author complains about how "an average of six hundred users per server" doesn't look like "every user knows the system admin where their data is stored". The median users per server would have been a fairer metric than the mean, specially because it later points out that three servers have over 50% of the users in the Mastodon ecosystem...
Comment · 4 years ago
Needs cost-based querying paid for with lightning network to be viable at scale.
Comment · 4 years ago
Comment · 5 years ago
I heard that truffle is a little outdated unfortunately, and doesn't add much value nowadays over hardhat.
Comment · 5 years ago
Breaking down Google is not gonna work.

I guess that the simplest solution is to forbid Google from being in the ad exchange business. Take down AdX and most of the monopolizing effects they have on the ecosystem would be dampened.

Comment · 5 years ago
I think this will potentially be the lawsuit of the year. Really interesting read.

A lot of the monopoly advantages seem to focus on AdX. I wonder if demanding that Google shall not participate in the ad exchange business could slowly open up competition in all the other markets...

For example, they were concerned that header bidding would make AdX fees go down to 5% instead of 22%, thus they used their advantage in the ad server market to stifle this (plus the FB deal). They are able to do this because they control both markets and can modify the data protocols between these two pieces. Same applies to scrambling IDs (ad servers and display markets)

Comment · 5 years ago
Comment · 5 years ago
1. I'm not sure we agree on that... Bitcoin doesn't protect against attacks, it provides you with a relatively simple model to measure the cost of attacks.

At equilibrium, any Bitcoin network participant will look for two fundamental things: (a) being able to move their own assets and (b) relative market price stability of their bitcoin. In case of a sustained 50% attack, both properties start to crack, but not completely. But after the attack, they are regained -- (a) immediately, and (b) eventually.

Consider the attacker to be a government, for example, an actor with a relatively high amount of resources, and the Bitcoin participant a dissident citizen of such government. The dissident wouldn't like to have its assets frozen by the government (through strict censorship of the dissident's transactions), so the market value for Bitcoin drops comparatively to how wealthy was the dissident selling its bitcoin savings. But, also, the dissident might avoid selling if they have enough financial capacity to withstand the attack.

In order to carry out such attack, the government needs to increase its energy spending on Bitcoin, up to the point where the attack is successful for a prolonged period of time. Bitcoin production is intrinsically bound to energy generation, thus to its economic realities (variability of demand, climate conditions, political affairs, just to name a few).

It would cost a government X dollars a day, or Y watts a day, every day, minus the price of the coins generated to attack the network. I estimate X to be the total miner rewards: at the time of writing, 38M USD [1]. Y seems to be at around 456 GWh [2]. Is it worth it for your adversary? That number is the dissident's security parameter. As long as their savings are less valuable than the cost of the attack and they can sustain the attack financially, the dissident should be fine (or really scared about an enemy irrationally spending a lot of energy/money with the purpose of just preventing them to access their money temporarily).

In the end both miners and users just want the chain to move forward. If one particular actor or coalition potentially prevents it, users/miners outside the coalition (if they detect it) would raise their investment to continue chugging blocks.

I think there are no "legitimate" vs "attacker" uses of hashing power. It's more about coalitions between miners and how costly/profitable would it be for them to centralize the network, and how hard is it on the other participants to coordinate a decentralized counter-attack (which ends up profiting them). But eventually, the equilibrium between all participants is to spend as little money/energy as possible. And if it's not decentralized it becomes censorable: next, it loses its value: now who's gonna want to mine something worthless?

2. We see it the same way. I'd add that if Bitcoin is staying around (I don't think it can be shut down), one solution is to use Open Timestamps or other hacks that don't require "block real estate", thus in no way compete with transactions, essentially piggybacking the PoW and getting the timestamp for free.

[1] first result I got for "block rewards Bitcoin last 24 hours": https://bitinfocharts.com/bitcoin/

[2] first result for "24 hour bitcoin consumption watts": https://digiconomist.net/bitcoin-energy-consumption

Comment · 5 years ago
1. My point is that you lost me here:

> This immediately produces an incentive for both the network to make use of as much computational capacity as possible to keep itself safe, and for any attacker to amass enough computational capacity to mount an attack

This seems false to me. Could you elaborate on what incentives you see at play here?

On another note, I feel one of the finest design details of Bitcoin is that its "decentralization-failure-mode", a.k.a. under a 50ish-percent-attack, is technically indistinguishable from normal operation.

2. The DID spec doesn't require the use of Bitcoin. So we agree with your last statement-disguised-as-question. Thus, it shouldn't have been listed as a reason for the rejection of the proposal (which spawned this thread)

Comment · 5 years ago
Comment · 5 years ago
I understand how mRNA works. I've got a background in both Chem and CompSci and I read https://berthub.eu/articles/posts/reverse-engineering-source...

But I wouldn't use it for the same reason I don't use Bluetooth headsets -- tech is just way too new, and of for some reason there are long term unexpected side effects, we won't know until a decade or two goes by.

PS: I'm vaccinated with the viral vector AstraZeneca one

Comment · 5 years ago
Yep, this is just the introduction to these kinds of thing. Then, they start to get accountants in both countries to agree on what seems a reasonable rate, say 30%? And the other 70% can be delayed earnings or whatever, and then maybe they decide to reinvest it instead. The list of resources is bottomless and continuously increasing.

What matters is that because the savings are potentially huge, your BigCo is incentivized to reduce that tax exposure and they've got the legal and accounting workforce to find that optimization.

Comment · 5 years ago
I met aome of the creators back in the day. The RedHat model is working well for them: open source and sell consultancy. It doesn't scale exponentially but as long as their OSS product is good they won't have a shortage of incoming deals.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton