Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - klosure

Pages: 1 [2] 3 4 5 6 7 8
16
Why in the hell would anyone lock those threads?

Questionning if we want to adopt Graphene is not allowed.
Bytemaster already decided that we must adopt Graphene and become Cryptonomex' bitch.
If that doesn't prove my point, I don't know what does.
Wake up people.

17
General Discussion / Re: Cryptonomex? WTF is this?
« on: June 15, 2015, 04:00:12 pm »
I was thinking this myself this morning. I have seen about 99% of the negative stuff be due to mostly people jumping to foregone conclusions. They get focused on one sprocket and don't see how the others that drive it make it work the way it needs to. There is a lot to gasp, and for a lot of people all it takes is one person to come along with over the top fear loaded words to spark cries that the whole system doesn't work out of analysis of one sprocket. So it gets wrapped up in the loaded term 'BitShares' and we all see people go on about it without really going on about it.

That's what you get when you make people face a fait accompli instead of consulting them in early stage.
The fact no comprehensive information has been released together with the announcement doesn't make things any better.
It's a bit desingenuous to complain that people focus on one sprocket when all there is to see is that sprocket.

18
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 15, 2015, 03:45:43 pm »
The devs were freelance contractors without a contract.  Under law that means they own the ip by default.  Only employee labor is considered work for hire.   Devs are not employees.
It is a very good thing that there exists a legal entity with clear rights otherwise bts code would be too risky for a business to use. 
BitShares code has been released under Unlicense, which puts the code in the public domain.
Dev don't own the property rights of the existing BitShares code.

19
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 15, 2015, 03:34:57 pm »
Valid points have been made in this thread as well as the others related to that subject, but the way some of them were formulated made me feel like they were used more to spread FUD than to start an honest and constructive discussion. I find it hard to believe that there is a benevolent motive behind some posts when they are formulated using an aggressive tone and insinuating that Bitshares is getting ripped off by Cryptonomex.

In case you haven't realized yet, I'm deliberately playing the devil's advocate here to force people out of blind faith and get them to evaluate objetively the situation under a more rational perspective and find arguments to counter my diatribe. Ultimately, what I want is people to ask themselves if they support this operation because they trust the core develpers, or if they support this operation because they understand what it's about and believe that it's the right thing to do.

So far, I have read a lot of knee-jerk "this is FUD" reactions but very little in terms of actually addressing the concerns I have raised. If the BitShares community takes the Cryptonomex deal, it must do so because it is convinced after careful and objective evaluation of all aspects of the deal that this is in BitShares' best interest, not because it believes blindly in some of the people involved in the deal. And before people can be convinced, things have to be tested and challenged.

One very important thing that people don't realize is that this time around we are not dealing with the core developers directly but with Cryptonomex, a company funded by private investors which primary objective, as any company, is to produce value for its shareholders. How much you trust Dan and Stan personally is irrelevant because Dan and Stan are not the only persons in command. As founders they certainly have a majority stake at this stage, but they already have to report to and take into account their investors opinion and make decisions that make business sense and put company growth as first priority even if it diverges from their philosphical ideals. They don't have the choice if they want to convince investors to get in for other rounds of funding. And even if they manage to keep their commitment to BitShares while they are majority stake holders, at some point they will exit, sell some of their holdings or let seasonned executives steer the company and lose control of what the company is doing. There is no way to guarantee that Cryptonomex will remain supportive to BitShares, and that's really a big concern considering that under current deal, Cryptonomex is controlling BitShares' life support system. It will take a single board decision for Cryptonomere to pull the plug on BitShares, try to steer it in a different direction or revoke whatever non-legally-binding agreement that has been made initially. If you think this is fud, you are extremely naive and have no experience of the world of business.

20
General Discussion / Re: Cryptonomex? WTF is this?
« on: June 15, 2015, 10:22:10 am »
The public domain is the legal entity that owns BitShares IP. It's a very real legal entity and you are infringing on its rights by trying to alienate its enjoyment of the intellectual properties it owns.

BitShares is an overloaded term. There is BitShares the protocol (1), BitShares the toolkit (2), and BitShares the populated blockchain (3) which is the store of value for this community.

1. BitShares the protocol: Public Domain
2. BitShares the toolkit: Public Domain?
3. BitShares the blockchain: ???

Cryptonomex is pitching a better (2) that fully implements (1) in the hopes that (3) will adopt it. Is it not the case that someone else in the future could implement a different (2) and try to sell it to (3)? It would be the community's job at that point to decide what to do, again, and the delegate's job (and by extension the witnesses) to either follow the desires of the shareholders or get fired.

edits: Typos and grammar.


Quote
https://github.com/bitshares/bitshares
The BitShares source code is in the public domain under the Unlicense. See the LICENSE for more information.

Regarding ownership of intellectual property, there are three cases out of which two are straightforward:
- All the code and ideas that are implemented in the code of the current BitShares project belong to the public domain as per the terms of the Unlicence under which it has been released. There is no way back on that, so Cryptonomex can't claim any particular rights on that code and set of ideas, and can't patent anything that makes the current BitShares protocol what it is since BitShares stands as prior art. The public keeps all rights of reuse of the existing code and owes nothing to Cryptonomex regardless of the claims they may make.
- All the code and ideas that are developped independently by Cryptonomex using its own funds and its own resources belongs to Cryptonomex and they may use and license it as they see fit.
- For all the code and ideas that hasn't been put in the public domain but has been developed prior to the incorporation of Cryptonomex or by individuals not affiliated to Cryptonomex at that time, and in particular when it could be shown that all funds meant to fund the development of BitShares hadn't been used yet, the ownership isn' clear. It may belong to its respective authors or to BitShares and therefore the public domain depending on exact circumstances. Although there really isn't much legal guidance about that case since BitShares isn't a legal entity and hasn't signed non-compete and disclosure of conflict of interests agreements, it would still be easy to show that appropriation by Cryptonomex of code which development was funded by the public for the purpose of releae in the  public domain would be unethical, so the outcome of an eventual judgement on the matter is anything but clear.

21
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 15, 2015, 09:27:54 am »
The art of trolling is to spread FUD with couple of semi-valid points. The OP was so far away from constructive critisism that it can be ignored. It's clear that he didn't want to raise any kind of reasonable discussion on valid points. Declaring that Bitshares will lose "its soul and fundamental raison d'etre" is just bullshit.

The art of cheer-leading is to buy in to everything without applying any critical thinking, dismiss valid concerns frivolously without addressing any of them, and pollute overwise constructive discussions by reactive and fanboyish posts with no actual content.

22
General Discussion / Re: Cryptonomex? WTF is this?
« on: June 15, 2015, 09:18:58 am »
Here is the deal, "BitShares" as not a legal entity and cannot "own" IP.    I personally do not recognize IP, but most people do including some of those who have contributed to BTS source code.
The public domain is the legal entity that owns BitShares IP. It's a very real legal entity and you are infringing on its rights by trying to alienate its enjoyment of the intellectual properties it owns.

Beside your stance regarding BitShares legal status is inconsistent and changes depending on the point you are trying to make. It's not a legal entity when it's about stripping it from it's intellectual property. But when you are pitching BitShares 2.0 BitShares is a well defined entity that can be the legal recipient of a software license with all the guarantees that this implies. That doesn't add up. If BitShares is not a legal entity, there is no way that you can make a software licence that will legally entitle BitShares to unlimited use of Graphene since BitShares is something that can't quite be define legally. That means that the exclusive license is a castle of cards that won't stand in court.

So let's be clear here and stop sugar coating.

BitShares not being a legal entity doesn't own the intellectual property but that doesn't mean that the core developers own it instead. As per the original license under which BitShares was released, the property rights to the work belong to the public domain. Authors retain only the moral rights.

BitShares not being a legal entity cannot be protected by any software license whatsoever, so all the reassuring guarantees of exclusive and illimited licensing are hollow promises that can be revoked on a whim by Cryptonomex and won't stand in court.

23
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 10:34:20 pm »
so, i would love to read the new license

in my opinion the intention of the license is to prefend a commercial use of Graphene. I think this is just fine! So in my understanding this license needs to make this points possible

1. no commercial use without license from Cryptonomex
2. the BitShares Blockchain got a unrestricted license for any feature in the future. Cryptonomex will get all commercial rights for stuff who is coded for the BitShares community.
3. BitShares Community can make multiple chains as long as the BitShares community is a stakeholder of 100% of the new chain.

Fully agree on the above.

Some more points that need to be addressed:
4. Software that is not a blockchain based peer-to-peer network but needs to read or manipulate the BitShares or affiliated DACs blockchain(s) or listen to transactions on the network and interface with the network at peer protocol level should be allowed to reuse BitShares code and therefore Graphene without being subject to the commercial licence. This is to allow the creation of APIs to allow third party tools, exchanges, bridges and other services to interact directly with the network or the blockchain without having to rewrite the whole object serialization and signing code already handled by Graphene.
5. Third party developers (community) who contribute code to Graphene should retain all rights of distribution, reproduction and modification on the code they contributed. Cryptonomex can specify that developers accept to grant them unrestrictive commercial license on the code by submitting it to the Graphene repo. But the point is that contributing back code shouldn't affect the rights of the contributor to use the code as he sees fit.

Other points that don't belong to the software license, but are important anyway
6. Cryptonomex must disclose to the BitShares community if they own or registered any patents on the code of Graphene and grant unrestricted license of usage of the patents to BitShares.
7. Cryptonomex should clarify how changes to Graphene framework will be tested and confirm if they intend ot use BitShares as a test bed for new features and in which circumstances they would do so. They should also commit to only integrate features on BitShares that are needed by BitShares so that BitShares doesn't become a public test net for Graphene.

A last point that has nothing to do with the upgrade:
8. Are community members who are accredited investors welcome to participate in next funding round of Cryptonomex and will this be announced on the forum?

24
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 09:35:46 pm »
https://voat.co/v/smartcoin/comments/127598
"we" can do whatever we want with the code.

Cryptonomex is giving BitShares the freedom to use everything we have produced without any kind of restriction except that it must remain a SINGLE blockchain.

License is restricted to a single blockchain. This creates the following limitations:
- If we want to add features without adding more bloat to the current blockchain so that clients interested only in one feature don't need to get all the bloat of all the features, we need multiple blockchains.
- If we want to demultiplex the current blockchain to make it easier to process, for example have decentralized exchange transactions on one blockchain and transfers on another
- If we want to acquire and merge with other DACs that already have a blockchain
- If we want to have hierarchical blockchains

License doesn't allow code reuse. This creates the following limitations:
- Third party DACs developers won't be able to fork Bitshares so Bitshares based DACs are something of the past and we lose the benefit of sharedrops. This is a huge change of the BitShares philosophy and business model that shouldn't be pushed without first being discussed. The whole point of the merger with PTS was for BTS to become the default sharedrop target and this merger yielded threads and threads of heated discussion.

25
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 09:00:10 pm »
So far I have seen half a dozen posts implying Ithat this is fud, but none has actually addressed any of the points I raised.
Graphene is open source, which was answered already in this thread.
This isn't addressing my points but nitpicking on terminology. It should be obvious from context that I meant "free software" / "non free software".
Anyway, I fixed this typo in posts, but this doesn't change the core of the argument.

Because of the license restrictions of Graphene, Bitshares cannot be forked or extended to a multiledger model, which means that it will not be able to evolve to fill other niches. The reuse restriction is a classic with proprietary licenses, but preventing Bitshares from evolving beyond a single ledger is novel and was added there for some reason. Now, if someone who cries "fud" may please explain why this restriction is necessary?

26
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 08:46:34 pm »
Good shareholders don't use their empoylees time on discussing on the forum about far-fetched worst case scenarios. Good shareholders let their employees do the job and ship the product.
Good shareholders vote on major changes of direction in the company's strategy.
Please show me where we have been consulted before this "announcement".

27
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 08:43:14 pm »
I thought everything in BitShares 2.0 would be open source ?

Surely this is just FUD. It can be licensed AND open sourced, I believe that's where it stands.

Wrong terminology, but its clear what was meant. Not sure what the correct terminology is but in media we call it creative commons.

Thanks. I meant "free software", not "open source". Typo. Fixed in the original post.

28
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 08:37:00 pm »
There are lots of bitcoin companies!  Bitcoin companies arent in competition with bitcoin.
Cryptonomex is a bitshares company.  Like Moonstone, and others to come.
Bitcoin companies don't attempt to change Bitcoin's terms of licensing to prevent it from being forked or extended in new directions.

Having bitshares companies improves the value of the bitshares ecosystem.
The problem is not the company. The problem is to try to force BitShares to use that company's non free software product and accept the major restrictions that come with it.

Stop bitching at the devs you guys!
There is a reason this thread is called "wake up call".
There are no technical reasons for forbidding Bitshares from evolving beyond a single ledger model.
The only reason is to prevent BitShares from growing too much and competing with Cryptonomex's clients.
This definitely isn't in the interest of BitShares.

So far I have seen half a dozen posts implying Ithat this is fud, but none has actually addressed any of the points I raised.

edit: replaced "closed source" by "non free software"

29
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 08:22:31 pm »
OP, please read some more threads before you write a tl;dr wall of text full of wild guesses.
I have read all the threads there are to read on the subject.
If you disagree about anything I have said, feel free to quote and reply.

30
General Discussion / Re: Wake up call: BitShares 2.0 is NOT BitShares
« on: June 14, 2015, 08:18:36 pm »
BTS cannot be "our lab rat" because we will not control its future, all hard forks will be voted on by stakeholders.   
BitShares2.0 is based on Graphene. If Graphene changes, BitShares changes unless we stop pulling changes from the Graphene repo.
It makes no sense to introduce an dependency on Graphene if we are not ready to accept subsequent changes on Graphene.
Mixed approaches with cherry picking will create a growing gap between the code base, make merges nightmerish and cost us much more in developer resources than if we had chosen the path of doing our own optimizations.

Pages: 1 [2] 3 4 5 6 7 8