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 - bitmeat

Pages: 1 ... 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 ... 75
256
General Discussion / Re: Invictus Innovations to Return PTS Donations
« on: November 12, 2014, 10:06:45 pm »
Why not just send them to a burn address? It would be way easier logistics wise. I suppose that won't really benefit original donators though.

257
Fine. I'll admit that I've been trying to put myself in the shoes of PTS holders and voicing what I felt would be my experience. I have a very tiny PTS holding so I'm not really affected.

I was playing devils advocate. But sure just to appease you - I'm a FUDder I should be lynched, my PTS and BTS taken away and my username banned lol Oh and all my posts should be removed. :)

258
General Discussion / Re: Is the new BTS client available?
« on: November 06, 2014, 05:36:20 pm »
My understanding is that BTSX will continue to exist and at some point one of the many hard forks will convert it to BTS, other than upgrading your client there shouldn't be any "new client". BTSX will just become BTS

259
Here's the thing, I'm actually happy with the change. I was just playing devils advocate putting myself in the shoes of someone who is entirely a PTS holder. They got robbed plain and simple. They helped fund the growth of BTSX and got detailed. Again I'm happy with the change, all I was looking for was for I3 to admit that. Instead we have Stan doing damage control. Man up admit the fault and move on. I'll admit I haven't read the newsletter in detail. But PTS holders should not need a vesting period, plain and simple.

260
Future DACs inside BTS will likely NOT honor 10% even if they wanted to it would probably be hard. Stop giving play as example.

261

It was a blatant violation of the social contract. PTS holders are no longer entitled to 10% of future DACs. Can't expect people to just let that go. I agree with the change it was necessary, but it did affect some folks, it will leave a scar regardless.

False.  PTS and AGS continue to represent the exact same demographics as always and developers have the same motivation to target them with air drops.   We continue to recommend that the community insist on that behavior from developers seeking their support.  And PTS and AGS holders also naturally benefit from all efforts to grow the value of BTS.

Lol. Come on man. Let's call a spade a spade. Will prior AGS and PTS holders take in 10% each? Or will it be 7% of 10% or in other words 0.7% of future DACs instead of 10%. Are you sure, you honored that contract?

No, I have no interest in spreading FUD. I've been a supporter of this project for quite some time. That said I am glad I have reduced my position. But am still vested.

262
It was a blatant violation of the social contract. PTS holders are no longer entitled to 10% of future DACs. Can't expect people to just let that go. I agree with the change it was necessary, but it did affect some folks, it will leave a scar regardless.

263
In all fairness his hand was forced with the merger which only allowed two weeks till end of PTS days. So independent developer had to figure out a strategy which takes time. I think they did the right thing otherwise PTS would've tanked and would've hurt confidence a lot more. Just my opinion...

264
Also not sure any mining is happening I.e. Not sure transfers in/out of exchanges would work.

265
Yes, there are talks of making a DPOS version of PTS so that independent airdrops could be done that honor the old contract. Just like PLAY. I think the Chinese community has abandoned BTS but are sticking with PTS. (Not all but some)

Whether that will go anywhere is another story.

266
QR codes as tattoos. nuff said.

267
Come on guys. There are some good points here. Yes some sounded like FUD, but I don't think there were any ill intentions.
I also do think BTS is making a step in the right direction.

Let's be constructive here - these points are actually very important going forward. What was was. No need to split hairs over what was.
Now the question is how will this be handled in the future. Let's not name call anyone who brings constructive criticism to the table a FUDder.

Is there a term for anti-FUDders? :) I find it ridiculous that any time someone asks a critical question they get the feeling as if they just stirred a hornet's nest. I think the questions alpha Bar is asking are healthy let's not alienate critical thinking.

268
I find it funny that people are using reputation, a form of trust, and decentralization, a trustless endeavor in the same thread.

We love to use the "corporation" analogy, but when it comes to performance-based compensation we abandon it completely. Not only that, but we are arguing against using our very own product to make it happen. No rational person could argue that this is unfair. If you're a developer, you get Dan or 2 other devs to sign off on your vest every month. Simple, effective, and completely obvious. Show me one company that will grant you an equity package that becomes liquid over time, but is granted in entirety upfront without any regard for your performance or status as an employee.

Outside of your issues with Dan giving grants to developers, "performance-based compensation" has not been "abandoned completely". 

I'm really starting to question your motives.  You say so many things that it almost seems you're more about the FUD than the truth.

How can this be FUD? These funds were donated for development and marketing. Is it too much to ask for transparency and accountability? If this is a one-time grant for past work then it would make sense that it was given without any precondition. If it is intended to be part of their ongoing compensation then it makes no sense to hand it out all at once. I was led to believe that all of the dev funds that are allotted for future dev and marketing work would be divided up and simply granted to the devs. We may never know what the plan is. We'll just have to watch the blockchain and take our best guess ...

Have it your way.  If choosing to view it as a year-end bonus for their roles in implementing the Crypto Product of the Year makes it acceptable in your sight, then having it done in such a way that also incentivizes continued support of the product ought to make you ecstatic.  On top of it all there are tax planning aspects and transition to the new developer funding model and the associated renegotiation of their original hiring packages that must be considered.  It is not customary to make any such compensation package negotiations public, beyond a simple transparent declaration of what is being done.

It is very customary in some open projects to have full income transparency. Gotta shift away from the "corporate" mentality.

If I remember correctly in Mozilla peers vote on who gets what % of the bonus and people know each other's compensation. (I've only heard that I haven't actually verified it, so I could be wrong, but I like the idea regardless)

269
Let me just add though - that even in this mode, if your PC is compromised you are not safe, as the produced master key could still be captured. The device won't do the signature, it will just produce the master key, which can be captured on a compromised PC.

However if the signature happens on another device (e.g. Trezor / mobile cell phone) it is far less likely that it will get hacked.

270
You guys don't understand how Yubikey works. It requires a centralized server that knows the secret and verifies it. Not that it can't be done with crypto, but you will still need to put your trust in a centralized entity. I'd much rather have an app that receives all transaction details over the net and shows it to you on your phone, where you can then decide whether to sign it or not. So even if your PC is compromised you never ever have your private keys exposed on it.

bitmeat, I don't think Yubikey needs a centralized server.   It works with KeePass and doesn't require a centralized server, you just had to install a KeePass plugin.

Here is the source to the plugin - http://keepass.info/extensions/v2/otpkeyprov/OtpKeyProv-2.3-Source.zip
Maybe someone could take a look at the source and implement it in Bitshares ... it is written in Visual C#

Thank you for the clarification! There are two modes, I was referring to the server mode. I see the static master password mode - that's fantastic. Should be easy to implement.

http://keepass.info/help/kb/yubikey.html

Pages: 1 ... 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 ... 75