Recent content by Sam Barnes

  1. Sam Barnes

    Proposal to remove the Guide position

    I agree with OP. The position should be removed or put on the track towards removal. If not fully dissolved, at least reduced to a volunteer capacity. As multiple guides have said before, the job was never the money, anyway. It's an avenue for gaining and exerting influence (social, democratic...
  2. Sam Barnes

    On-Chain voting working group - status, October 2019

    That's also just some random guy's blog post to beginner crypto speculators vs. a statement made by a sizable company with (presumably) legit legal research capabilities. Just saying its probably better to look into the future implications of this decision further before assuming "voting with...
  3. Sam Barnes

    On-Chain voting working group - status, October 2019

    Is token holder voting something that would prevent a future coinbase listing? Although I'm doubtful that would happen any time soon its something to consider: the possibility of a US based exchange adding it in the future. Don't think decisions that potentially block off all future US exchanges...
  4. Sam Barnes

    Factom Live API considerations

    Thats not what I was implying lol of course k8s and container orchestration are great. The home-grown daemon is the point of failure when its the onramp to all other services you run. Just unnecessary overhead that our team doesn't want to be stuck devoting man hours to maintain and debug. We...
  5. Sam Barnes

    Factom Live API considerations

    Agreed on the need for another call, if others are up for it. I'll convey that back to the relevant parties on the team. As for the daemon on docker/k8s, just because you can doesn't mean you should ;) it's a songle point of failure that can easily be eliminated with something more cloud native
  6. Sam Barnes

    Factom Live API considerations

    I wasn't suggesting factomd implement its own PubSub system. You guys mentioned that is going to just be a firehose of data. Rather than spewing that stream of data at a particular IP address/URL where a home-grown daemon lives, point it at a proper queue that has no maintenance overhead. The...
  7. Sam Barnes

    Factom Live API considerations

    As another stakeholder in the success of this feature, the Harmony team at Factom would like to express our concerns with some of the ideas being floated and also suggestions as to the direction we would like it to head. Many people have already commented about how the listening to network...
  8. Sam Barnes

    Seperate FIP and FIS or recombine

    Because they improve Factom as a whole. I just think we should avoid developer dilution wherever we can. We already have a core committee that never meets, and attention is spread thin . If Bitcoin and Ethereum (by far the two largest and most successful blockchain developer ecosystems) both...
  9. Sam Barnes

    Seperate FIP and FIS or recombine

    FIPS (Root Page) |-- Core Protocol (Sub Page) |-- Application Interoperability (Another Page) |-- Governance (Another Page) |-- Any other improvement category... Meh, if you can't trust the audience to click the right link out of those choices to find what their looking for, I don't think you...
  10. Sam Barnes

    Seperate FIP and FIS or recombine

    I'm not involved with FAT in any way, but it seems like its a project with its own self-contained governance system that suits its needs well enough already. I don't think we should impose the FIP system on FAT if that community of devs doesn't think its necessary. At the end of the day, a...
  11. Sam Barnes

    Seperate FIP and FIS or recombine

    Thinking about it more, i think it would make sense to include Governance proposals in FIPs as well. Make that a separate bucket with the Guides as the editors. Could follow the same system and rules we have now, but be more formally tracked as "Factom Improvements"
  12. Sam Barnes

    Seperate FIP and FIS or recombine

    Thanks for bringing this up, Niels. I am in agreement with Who's points here. I think overall there will be less confusion with a single system, and we can focus the limited developer attention in one spot. I don't think it makes things any more cluttered --- Bitcoin and Ethereum both use a...
  13. Sam Barnes

    Explanation of Messages (IMsg)

    For anyone looking for byte level descriptions of the messages, I'm working to draft that here: https://hackmd.io/@9jEhmQ9vTMGWUph4GvlVlA/H1e8rS3lr hopefully we can merge this with all of Who's work and start putting together an official spec for the protocol EDIT: In case that site goes away...
  14. Sam Barnes

    Standing Parties

    The same can be said about cryptocurrency in general — you lose your key, you lose your money. The safety of funds ultimately relies on users being able to safely handle their private keys and know which private keys should be stored more securely. I'd be much more careful with the keys for a...
  15. Sam Barnes

    Standing Parties

    Sam from Factom Inc here. Over the past few weeks I've been helping to design and lead the implementation of the Digital Identity system on Factom. To see the definition of what constitutes an Identity under this scheme, see the specification and initial Go library / factom-walletd...
Top