591 karma · joined November 28, 2021
I want to clarify that this isn't just a technical point: if I have $100 in account A, and I use a card processor to move it to account B, and then the holder of that account withdraws it, then the card processor can still reverse the transaction, leading B with a debt of $100.
(This is actually a common scam: you send someone $1000 with a 'soft' payment method, like a check, then you have them buy gift cards and send the codes. Once the check bounces, you split.)
If I do the same thing in Bitcoin, that's not possible. If Bitfinex hackers had used Bitcoin qua payment processor to move $70MM, then exchanged the Bitcoin into something else, the Bitcoin transaction could never have been reversed. Only the custody, which is a different thing.
If we look at the current issue[0] of The Threepenny Review, the pathology is quite obvious. The three "poems" in the list all share certain features:
- A variable amount of syllables per line (e.g. no metre)
- No rhymes
- No other discernible differences from prose
At that point, why even bother calling it a poem? You might as well save yourself the time by opening up the day's newspaper in a text editor, clicking randomly, and pressing enter. When you feel there's enough line breaks, you're ready to publish.
Even their industrial buildings looked good!
Grant that they don't have anything interesting to write about and it's too expensive to build decent buildings, but the poetry is indisputable.
For a serious site, the cost of allowing passive reading is going to be ~0.
That said, if they respond, I'll edit the post.
Is their site really so sensitive as to make reading with Tor impossible?
The egress traffic is also trivial - a page seems to clock in at below 50k. If they're paying $0.02/GB, that's $1 / million requests.
More importantly, if it really were a DoS attack, there's way less obtrusive methods, such as a CAPTCHA or similar verification screen.
> The most dangerous thing you can do is to take any one impulse of your own nature and set it up as the thing you ought to follow at all costs. There is not one of them which will not make us into devils if we set it up as an absolute guide. You might think love of humanity in general was safe, but it is not. If you leave out justice you will find yourself breaking agreements and faking evidence in trials "for the sake of humanity," and become in the end a cruel and treacherous man.
There's other things in the world than money. Even if that is your philosophy, consider that learning obscure functional languages might make you a better programmer across the board.
So it's a cryptocurrency scheme?
That being said, 85% of conversations about NFTs are non-consensual, so you may very well find a market for your service.
You mention Brexit. If it was a foregone conclusion that people weren't sharp enough to vote either way, why not just ask Queen Elizabeth whether they should stay or leave?
In addition, it's more stable. If you just get money once in a while, planning is harder. If you have so and so many subscribers, you can make better guesses on what your budget will be.
> The central criticism of ENS in this blog post - that the multisig (in the past) or the DAO (now) could take away your .ETH name - is not true. No one has the ability to take a .ETH name away from someone. The DAO (which launched Nov 8, not Nov 10 as it said), wasn't created to take over that power from the multisig because the multisig didn't have that power either. The multisig does manage the ENS root, but the .ETH TLD is permanently locked.
But I do not, in fact, state this:
"ENS is censorship-resistant in the sense that nobody can directly seize your domain."
> Re the fact the DAO controls the pricing and registration parameters of .ETH names, it's true that it would be possible for the DAO to change them to something that targets a specific user or name. The DAO cannot take away a .eth name that is registered (it could only make it difficult or practically impossible to extend or register anew).
Now see, I would personally contend that "mak[ing] it difficult or practically impossible to extend or register" is a form of censorship.
> To guard against this, a user can pay ahead for as many years as they want, ensuring they have the name for that period (e.g. 100 years).
Well, if you assume that the registration fee never is increased above $5, sure. This also raises the question of why to even bother with expiration at all, other than as an opportunity to extract more rent.
Likewise, if people will just go out and buy the names for two thousand years whenever the renewal fees go up, this raises the question of why you would even bother and not just grandfather the old names in. (I mean, I suppose for throwaway names or trivial fee hikes, but it's not entirely obvious)
And I can still see some attacks about that business. For example, you start off by raising the fee to $6. Assuming this doesn't trigger them to buy it for 100 years, you raise it to $7, and so on. By the time the fee has reached let's say $100 p.a., hedging for 100 years would cost $10k, which is not exactly pocket money. And at that point, you can raise it even higher, etc.
Also, on an aesthetic note, having to register names for 100 years because the renewal can be pulled out from under your feet at any time seems like somewhat of a kludge.
(All this assumes nothing gets migrated, as happened in <https://docs.ens.domains/ens-migration-february-2020/technic...>. Based on the high degree of centralization inherent to ENS, my money is on this being an easier process than it ought to be.)
> Given that DAO proposals have required voting periods, it wouldn't be possible to surprise this on someone, and they'd be able to simply extend their registration for 100 years (or whatever period they want) before it went through.
If I'm reading this right, the voting period is either 9 or 14 days: https://docs.ens.domains/v/governance/process
Are you suggesting people keep a close eye on the voting process of the infrastructure that controls their domain? If so, would you say that them feeling necessitated to do so indicates confidence in this infrastructure?
> As you mention, the ENS constitution also prohibits it.
Ah yes, but does it prevent it?
> I find this attack vector extremely unlikely to be attempted and near impossible to carry out successfully.
Well, a lot of people thought it would be unlikely for Ethereum to pull of a hardfork to override the steadfast iron will of unstoppable code, but here we are. In the end, it's not about what you think, but about what actually happens.
What happens when someone registers and actually starts using dailystormer.eth, causing a rash of bad headlines and the token price to drop precipitously?
In the end, there's only one way to find out:
Every man's work shall be made manifest: for the day shall declare it, because it shall be revealed by fire; and the fire shall try every man's work of what sort it is.