<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for windley</title><link>http://disqus.com/by/windley/</link><description></description><atom:link href="http://disqus.com/windley/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 28 Jul 2017 17:24:33 -0000</lastBuildDate><item><title>Re: Identity, Sovrin, and the Internet of Things</title><link>http://www.windley.com/archives/2017/07/identity_sovrin_and_the_internet_of_things.shtml#comment-3440851592</link><description>&lt;p&gt;Creating non-hierarchical certificate/trust structures doesn't preclude hierarchies of devices where that's desirable. Although I prefer random grouping ability as spelled out in this post on Communities of Things (called "societies" in the post): &lt;a href="http://www.windley.com/archives/2015/07/social_things_trustworthy_spaces_and_the_internet_of_things.shtml" rel="nofollow noopener" target="_blank" title="http://www.windley.com/archives/2015/07/social_things_trustworthy_spaces_and_the_internet_of_things.shtml"&gt;http://www.windley.com/arch...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Fri, 28 Jul 2017 17:24:33 -0000</pubDate></item><item><title>Re: Identity, Sovrin, and the Internet of Things</title><link>http://www.windley.com/archives/2017/07/identity_sovrin_and_the_internet_of_things.shtml#comment-3440712749</link><description>&lt;p&gt;Wouldn't its response be an identifier? Not sure what you're driving at.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Fri, 28 Jul 2017 15:56:30 -0000</pubDate></item><item><title>Re: Sovrin Use Cases: Authentication</title><link>http://www.windley.com/archives/2016/11/sovrin_use_cases_authentication.shtml#comment-3413765247</link><description>&lt;p&gt;Yes, ironic indeed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 12 Jul 2017 18:08:57 -0000</pubDate></item><item><title>Re: Phil Windley's Technometria | Capture Mode and Emacs</title><link>http://www.windley.com/archives/2010/12/capture_mode_and_emacs.shtml#comment-3366923155</link><description>&lt;p&gt;Its been a long time since I've done this. But you need to have the Quicksilver Terminal plugin installed. Then from Quicksilver, you can enter the text and select "Run in Terminal" from Quicksilver. Setting up a trigger for that is pretty straightforward after that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Sat, 17 Jun 2017 13:18:45 -0000</pubDate></item><item><title>Re: Using Picos for BYU's Priority Registration</title><link>http://www.windley.com/archives/2017/01/using_picos_for_byus_priority_registration.shtml#comment-3233534397</link><description>&lt;p&gt;A couple of things. First, the numbers I report for the legacy system are for peak load, not maximum throughput.&lt;/p&gt;&lt;p&gt;Second, contrary to what you seem to believe, the system isn't run by a bunch of incompetent hacks. We have looked at it and it is contention at the persistence layer that's can't be easily solved. But like any other system, it could be fixed, but no one has deemed that the fix is worth the cost. Obviously, if this were the core system for a bank, those economies would be different and it would be changed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Fri, 31 Mar 2017 12:50:51 -0000</pubDate></item><item><title>Re: The New Pico Engine Is Ready for Use</title><link>http://www.windley.com/archives/2017/03/the_new_pico_engine_is_ready_for_use.shtml#comment-3233517454</link><description>&lt;p&gt;Your comment on the other page makes me think you're perhaps misunderstanding what this is. It's not an event bus, it's an actor-model programming system with built-in persistence.&lt;/p&gt;&lt;p&gt;At its current performance level there are obviously use cases for which it might not be applicable, but there are lots of use cases, even outside the classroom, where it has utility. For example, for most IoT applications of picos that I've explored these numbers wouldn't even be close to a problem. What's your use case?&lt;/p&gt;&lt;p&gt;There is still a lot of low hanging fruit for optimizing the engine. For example, the new pico engine isn't yet using a real persistence store and I expect that to help a lot.&lt;/p&gt;&lt;p&gt;Also, to be fair, the registration demo was a proof of concept, not a performance test. No one took any pains to find bottlenecks. Could be something as simple as how the HTTP calls were made and a bottleneck there. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Fri, 31 Mar 2017 12:45:42 -0000</pubDate></item><item><title>Re: The New Pico Engine Is Ready for Use</title><link>http://www.windley.com/archives/2017/03/the_new_pico_engine_is_ready_for_use.shtml#comment-3231658566</link><description>&lt;p&gt;You can be impressed or not, I don't care. Given everything it was trying to do, it was a useful milestone for us.&lt;/p&gt;&lt;p&gt;Comparing it to a Node app is apples and oranges given what the pico engine is intended to do. Furthermore, these figures are with no optimization other than removing logging and there's considerable room for improving the persistence layer to increase performance.&lt;/p&gt;&lt;p&gt;So, whether you were impressed or not, I was happy to hit the milestone.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Thu, 30 Mar 2017 11:57:34 -0000</pubDate></item><item><title>Re: Using Picos for BYU's Priority Registration</title><link>http://www.windley.com/archives/2017/01/using_picos_for_byus_priority_registration.shtml#comment-3231648328</link><description>&lt;p&gt;The legacy system is over 20 years old with all that implies. The performance issue on registration basically comes down to disk contention, which might sound easy to solve, but is not as simple as it sounds for lots of reasons.&lt;/p&gt;&lt;p&gt;The pico system has not been optimized in any way, so yeah, considering what it's doing here, I was happy with the performance. The problem with the current implementation basically comes down to persistence layer contention as well, although for different reasons. This architecture allows that problem to be solved through the straightforward application of some basic scaling concepts.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Thu, 30 Mar 2017 11:51:03 -0000</pubDate></item><item><title>Re: The CloudOS: Connecting Hue Lights and Insteon Controllers</title><link>http://www.windley.com/archives/2013/01/the_cloudos_connecting_hue_lights_and_insteon_controllers.shtml#comment-3213366563</link><description>&lt;p&gt;I agree this is an important point. We've been reworking the pico engine to run on Raspberry Pi's and similar processors in order to push as much processing to the edge as possible.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Mon, 20 Mar 2017 11:02:58 -0000</pubDate></item><item><title>Re: Every Computer is Distributed</title><link>http://www.windley.com/archives/2017/01/every_computer_is_distributed.shtml#comment-3122436935</link><description>&lt;p&gt;Apparently, there's a thread on Reddit about the problems I've experienced: &lt;a href="https://www.reddit.com/r/apple/comments/5p3srp/apple_shutters_reviews_of_lg_ultrafine_5k_display/" rel="nofollow noopener" target="_blank" title="https://www.reddit.com/r/apple/comments/5p3srp/apple_shutters_reviews_of_lg_ultrafine_5k_display/"&gt;https://www.reddit.com/r/ap...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;My fix (rebooting everything, including the monitor) only brings temporary relief.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Thu, 26 Jan 2017 22:22:16 -0000</pubDate></item><item><title>Re: Every Computer is Distributed</title><link>http://www.windley.com/archives/2017/01/every_computer_is_distributed.shtml#comment-3122435755</link><description>&lt;p&gt;Yeah, an electricians are rarely trained to be computer techs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Thu, 26 Jan 2017 22:21:06 -0000</pubDate></item><item><title>Re: Book Review: Seeing Like a State</title><link>https://solitum.net/book-review-seeing-like-a-state/#comment-3122189053</link><description>&lt;p&gt;I read this book several years ago and similarly enjoyed it. I was reading primarily from the perspective of how identity systems impact and nurture a centralized, administrative regime. A more identity-oriented treatment of these issues can be found in Documenting Individual Identity by Caplan and Torpey (eds). I trad Anti-Fragile some time after reading this, and had not connected them the way you did. Thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Thu, 26 Jan 2017 18:48:22 -0000</pubDate></item><item><title>Re: On Sovereignty</title><link>http://www.windley.com/archives/2016/10/on_sovereignty.shtml#comment-2976712761</link><description>&lt;p&gt;Thanks Darrel! It hit me that way too when I finally got the dual nature of sovereignty and that its duality makes it even more powerful.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Sun, 30 Oct 2016 18:53:41 -0000</pubDate></item><item><title>Re: Self-Sovereign Identity and the Legitimacy of Permissioned Ledgers</title><link>http://www.windley.com/archives/2016/09/self-sovereign_identity_and_the_legitimacy_of_permissioned_ledgers.shtml#comment-2934713451</link><description>&lt;p&gt;While I can't predict how they'll react, our hope is that they will react just as you've outlined. That by giving people control, we lessen the regulatory burden on businesses and other organizations.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:22:38 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934710581</link><description>&lt;p&gt;In part by solving the "cheap pseudonym problem". The actual computation of the reputation is outside the scope of Sovrin. Sovrin merely records claims and proofs. Other systems will use them to generate reputation scores.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:20:46 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934708242</link><description>&lt;p&gt;It's not clear if stewards make money fro Sovrin or because or it. Stewards are likely going to be stewards because of the benefits it provides, not because there's a business model that pays them (as stewards). We're working on an economy of claims that includes premium claims that cost something to use with the proceeds being split among many parties.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:19:11 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934704439</link><description>&lt;p&gt;The details are yet to be defined, the Trust Framework working group is currently dealing with those questions.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:16:42 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934703107</link><description>&lt;p&gt;Yes, there is a need for semantic interchange. Lots of work to do in making that all work.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:15:52 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934700987</link><description>&lt;p&gt;I believe so but that probably depends on what part of the IAM infrastructure we're talking about. Sovrin doesn't do away with the need for organizations to have internal accounts and keep their own data. So to the extent existing IAM systems do that, they will co-exist and make use of each other.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:14:28 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934698206</link><description>&lt;p&gt;It can't since all that data is in the bank's systems. Sovrin prevents correlation between domains, it can't control what happens within a single domain.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:12:41 -0000</pubDate></item><item><title>Re: How Sovrin Works</title><link>http://www.windley.com/archives/2016/10/how_sovrin_works.shtml#comment-2934694352</link><description>&lt;p&gt;Out of scope. For now they simply memorialize an agreement. Sovrin, in general, makes relies appeals processes and legal arrangements that exist outside the ledger.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 05 Oct 2016 11:10:13 -0000</pubDate></item><item><title>Re: An Internet for Identity</title><link>http://www.windley.com/archives/2016/08/an_internet_for_identity.shtml#comment-2879966966</link><description>&lt;p&gt;OpenID failed because it was impossible to know what identities you could trust. There was no trust framework. An SIS needs to solve the trust problem to be viable. If it does that, there are plenty of businesses who will use it and sponsor users on the network.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Tue, 06 Sep 2016 21:41:11 -0000</pubDate></item><item><title>Re: Why Companies Need Self-Sovereign Identity</title><link>http://www.windley.com//archives/2016/05/why_companies_need_self-sovereign_identity.shtml#comment-2682260948</link><description>&lt;p&gt;Yes. See Properties of Permissioned and Permissionless Blockchains (&lt;a href="http://www.windley.com/archives/2016/04/properties_of_permissioned_and_permissionless_blockchains.shtml)" rel="nofollow noopener" target="_blank" title="http://www.windley.com/archives/2016/04/properties_of_permissioned_and_permissionless_blockchains.shtml)"&gt;http://www.windley.com/arch...&lt;/a&gt;. Short answer: persmissioned blockchains. Quoting: "Permissioned blockchains have a governance process that selects validators and thus don't have to survive Sybil attacks since the validators are known--there are no pseudonymous validators."&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Wed, 18 May 2016 11:30:02 -0000</pubDate></item><item><title>Re: Properties of Permissioned and Permissionless Blockchains</title><link>http://www.windley.com/archives/2016/04/properties_of_permissioned_and_permissionless_blockchains.shtml#comment-2635261627</link><description>&lt;p&gt;Thanks Daniel. I'll take a look.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Thu, 21 Apr 2016 09:19:12 -0000</pubDate></item><item><title>Re: Properties of Permissioned and Permissionless Blockchains</title><link>http://www.windley.com/archives/2016/04/properties_of_permissioned_and_permissionless_blockchains.shtml#comment-2628964543</link><description>&lt;p&gt;One additional feature of permissioned blockchains is they're faster (transactions per second) because they don't need to spend time on proof of work. Note that I didn't say they're less resource intensive. Most centralized transaction clearing systems (ledgers) are pretty expensive to run (think SWIFT, Visa, etc.). I don't know of evidence that proof-of-work schemes are necessarily resource hogs compared to other systems we have to clearing transactions in a ledger.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Windley</dc:creator><pubDate>Sun, 17 Apr 2016 18:32:21 -0000</pubDate></item></channel></rss>