Hacker Newsnew | past | comments | ask | show | jobs | submit | more doragcoder's commentslogin

Agreed that the argument is a bit weak, but we would still end up with a major centralized repository for a decentralized protocol. And the changes to make Gitlab more like the proposal would probably be more work than just making the proposal a new project.


I think we would end up with multiple major repositories and many smaller ones. One of the first steps towards more decentralization would be an issue tracker that doesn't under numbers but hashes and that stores its content in a git repo (like the wiki already does). EDIT I noticed in the comments the Fossil already has this, interesting http://fossil-scm.org/index.html/tktview/3711fc7cfd21d7f8684...


Can't good survey question design, mitigate this? Haven't psychologists and researchers been doing this for decades and solved the problem of asking verb questions properly?

Because at the end of the day you have to ask what people want, right?


I need to go more in-depth on the proposal. But the first thing that strikes me, is if you're going to use the Blockchain (with a capital "B") as storage of usernames and such. Why not use namecoin? It has the process for name consensus down. Also it won't pollute the main Bitcoin blockchain.


Hi, author here.

I have a mild bias against altcoins, and have heard bad things about Namecoin in particular: that the anti-spam incentives aren't good, leading to illegal files stored in the blockchain itself, and that there's no compact representation (like Bitcoin's Simplified Payment Verification) for determining whether a claimed name is valid without consulting a full history.

As I understand it, these two design flaws combine to mean that you have to store some very illegal files to use a namecoin resolver, which doesn't sound good to me. (I may be mistaken, since the bad things I heard about Namecoin came from Bitcoin people..)


There aren't any inherent protections to storing illegal data in the Bitcoin blockchain, either (short of evading the issue by using a thin client, I suppose). The nature of what is illegal being so encompassing, in that you can ultimately encode the information into some integer of sorts either way, means it's impractical or unnecessary to provide full protection for such things.


No inherent protections, just different incentives. Storing a 4MB image at 80 bytes per $0.08 OP_RETURN transaction would cost you $4000. Why would you do that when you can use namecoin for practically free?


Which makes the statement you made that, "this currency stuff is frankly kind of uninteresting to me," kind of funny (I assume that was on purpose) because the currency stuff is exactly the thing that makes bitcoin work so well.


Fair point!

I made that statement because a lot of people don't realize that Bitcoin, ignoring the fact that you can trade it, has solved a fundamental consensus problem in distributed systems that we should care about and use :)


> I have a mild bias against altcoins, and have heard bad things about Namecoin in particular: that the anti-spam incentives aren't good, leading to illegal files stored in the blockchain itself, and that there's no compact representation (like Bitcoin's Simplified Payment Verification) for determining whether a claimed name is valid without consulting a full history.

Security-wise Namecoin is a weaker Blockchain, but I think in this case it's not that important. -- Are not the anti-spam measures hurting users as much as spammers in this case? Since you end up with higher-costs for what is otherwise practically free with a centralized service.

From the looks of it there is no reason that Bitcoin's Simplified Payment Verification wouldn't be usable with Namecoin either.

edit: Also this may be interesting to take a look at https://people.csail.mit.edu/nickolai/papers/vandenhooff-ver...


The notion that a file can be illegal makes as much sense to the internet as a plant being illegal makes to the earth.

Especially when it has the side effect of inhibiting what otherwise might be a compelling solution.


Right, and the notion that murder is illegal makes no sense to the universe as humans are "merely" an aggregate of matter no different than any other. Nothing makes any sense to entities not capable of reasoning, that is a pointless tautology with no relevance to the discussion.


Your analogy doesn't hold up, as (for one) we have society and plants don't. I'm glad that child porn is illegal (which is usually distributed in files), as it makes the world safer for children.

Also: some plants are serious jerks.


If pi goes on forever, it contains any and all representations of child porn that could exist. The first person to calculate pi that far will be breaking the law. No, that doesn't make sense, nor does any sort of information being illegal. What does make sense is to legislate the actions that can generate that data, or the misappropriation of that data.


You took a poor example since pi is not known to be a normal number (see eg http://mathworld.wolfram.com/NormalNumber.html )

This number however is:

    0.0 1 10 11 100 101 110 111 1000 ...
This number contains all movies that have and will ever exist. However to specify where a 700mb harry potter movie is in this number, you'll need at least 700mb to represent the index. So in some sense harry potter 'exists' in this number - but in another sense its just a silly encoding method.


Hear hear. This is an easy-to-understand and concise thought experiment; use it often!


Great point !


no, it's a really contrived point.


Most law enforcement and judges don't ask what makes sense to the internet, even if you ignore users personal opinions about the matter.


I think the percentages make a lot of sense. I think there could be a fair amount of, "I think this is wrong, but nobody is really saying it's wrong, so, maybe it's not as wrong as I think it is." And that police officer basically does nothing or rough up a suspect with a colleague who's more aggressive every now and then.


I think more than 15% of people are decent and less than 15% are abusive.

I think the problem is the vast majority just goes along with the culture and a few bad apples at the top create an abuse prone culture.


Fashion is goes in cycles, so it makes sense:

Pocket -> Wrist -> Pocket (phone) -> Wrist...

Now if I can just get my 10-year old patent for wrist squares to go through....


What was the wrist device before the pocket watch? A wrist-slide-rule?



Wristrock.


I didn't see anything about the ease of copying data by stamping it. It seems like making hard copy duplicates easily would be a huge benefit of this as well.


This makes prefect sense. The worst thing you can do to punish a person in prison (which is a pretty bad punishment to begin with) is solitary confinement.


Noooooooooooooooooooooooooo...


You can use object composition: http://play.golang.org/p/jyS38luYjM

Then make a Draw() method on the single object default to what you expect. The simple inline explanation is:

    type SingleObject struct {
        Cowboy
        Shape
    }
Access is as follows to be unambiguous:

     Woody.Cowboy.Draw() 
     Woody.Shape.Draw()


The problem is that you can't differentiate SingleObject from CowboyObject and ShapeObject.

They all are the same interface and can be passed into each other's methods, leading to a logical error.


I'm thinking that clocks to time would be more like GPS to maps. You could just simply ask what position is the sun in a particular location, at a fingers touch. So it would be too much of a big deal for most people. But it would make programmers and things that deal with logical time much easier.


> But it would make programmers and things that deal with logical time much easier.

But as the article points out, programmers and others who want to work with time without the hassles of timezones already have such a system (UTC).


Only sort of. The abolishment of Daylight Savings would help a great deal in this area, though (because it makes writing time-based code so much harder).


Why only sort of? What could be easier than than a time reference that's constant across the planet, doesn't observe daylight savings, has no leap years (but rare leap seconds, iirc), and can be trivially converted to a local time if necessary? I guess never having to convert to local times because there's no such thing in the world as time zones would be easier, but at the cost of all of the practical everyday uses of local times.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: