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.
None of this is seeking the favor of Invictus. We only own a small percent of AGS and PTS.Never meant that...
I find Keypr the best of those three. Undecided aginst Keyhotee... What about something like "Privee" (pronounced like the word privy - has the connotation of information you only share with those who should have it)
In any case I think if we were to switch names it should be something that people REALLY like and a clear consensus emerges. The community seems open to considering a new name (with keyhotee being the code name during development) but it would need to be something special that captures people's imagination and everyone gravitates to it, not just "BitMail." There are big costs to making a switch, it needs to be marketed and a lot of people like keyhotee; at some point you have to stick to something. So if you don't like the name, think of something that really captures people and gets a lot of support, gets people excited, get creative, think outside the box. I don't think we should make a change if there is a large split in opinion.
Not familiar with US legislation. Does anyone have a guess whether this will move the price up or downwoards?
It's not going to move the price but its a pain in the ass for taxpayers to have to try and track every trade. It's probably impossible to do it with the current technology as this would have to be built into clients themselves to work.
Bitshares wont have this problem as much because of how it's designed but if you use Cryptsy it means you have to track every single trade and the capital gains on everything.
If you use all sorts of mining pools, Cryptsy and sites which are shut down or the information is just lost, you'll have to deal with the IRS someday unless we can get a law passed to make cryptocurrency tax free.
Technology doesn't solve every problem. Sometimes you have to work the system to get a favorable bill passed and that is the reason to interface with regulators.
(
I respectfully submit the Keyhotee moniker is inadequate and may hinder widespread adoption.
...
Im glad someone has raised this issue - I was about to raise this as well.
Here is a list of communication networks that are extremely popular:
-Skype
Now here is a list of communication networks that only techies have heard of:
-Bitmessage
-Torchat
Ignoring the fact that the second list require users to share hashes of public keys, there is another pattern there - successful product names are catchy, don't include techy jargon, and can often be used as a verb. I would assert that Keyhotee is NOT catchy, and is borderline jargon. Whilst you can say "Skype/Tweet me", the phrase "send me a Keyhotee" is never going to catch on.
I dont want to have to go around my family evangelizing a product with the word "Bit" in the name either - its extremely geeky, and most people are not interested in the technology, they are interested in the social experience. For a communication system to actually get any momentum, the branding is just as important as the technology.
I imagine that people might refuse to honor AGS/PTS if they don't need anything from I3 and the comunity (no funding, no consulting with Dan, ho office space, no marketing/exposure) and just use the open source Tapos code and other Tools.
The AGS/PTS community could fork their appraoches which would be an arguement to honor PTS/AGS. But if a lot of developers take the TaPOS code and fork it the community might have a hard time re-forking all of their specific applications. Then 20% might feel too much to them...
So what do you think. Would it be a good thing for the long Term value of AGS/PTS if we downgrade the 20% to 10% or 5% or something if they just use the software tools and code?
Think of AGS being a targeted marketing email list of all the people in the industry who can prove they are willing to donate to advance the cause.
Now, as a developer you have some promotional shares to give away. Do you give them to the people on the Proven Donor Mailing List or do you hand them out at random to people who will mostly just dump them for quick cash.
We have to stop thinking of AGS as merely an obligation to be avoided by not using what the donors have built for everybody and instead remind everybodyIt's a List of Proven Donors!
People pay good money for a nice targeted mailing list for a prized demographic like AGS holders..
Who else would be better to recruit as supporters?
Having clear legislation must be a big positive for business enagement. It's not quite death by taxes but might be a PITA for individuals to understand - I expect it'll be a positive overall.
OK, so that's not the real acronym. The point is that the age of DACs is upon us.
"RideShares is a community-based open-source project built on a fully distributed architecture with no central core. From decision making to stake holdings, servers, development and adoption, the organisation is built on a completely peer-to-peer protocol and it’s power is in it’s people."
IMO yes, but the benefit is tiny compared to the benefit you get from the current team's C++ experience, the advantages are not worth it
Let me put it this way, I think c++ is one of the *worst* languages ever invented for *anything* and still have no problem using it for this project. It doesn't matter that much.QuoteC++ is a horrible language. It's made more horrible by the fact that a lot
of substandard programmers use it, to the point where it's much much
easier to generate total and utter crap with it. Quite frankly, even if
the choice of C were to do *nothing* but keep the C++ programmers out,
that in itself would be a huge reason to use C.
...
C++ leads to really really bad design choices. You invariably start using
the "nice" library features of the language like STL and Boost and other
total and utter crap, that may "help" you program, but causes:
- infinite amounts of pain when they don't work (and anybody who tells me
that STL and especially Boost are stable and portable is just so full
of BS that it's not even funny)
- inefficient abstracted programming models where two years down the road
you notice that some abstraction wasn't very efficient, but now all
your code depends on all the nice object models around it, and you
cannot fix it without rewriting your app.
Linus Torvalds
