Comments for captain's blog

Comment on Notes on Web Weaver UX by Captain Lyre Calliope

Captain Lyre Calliope — Thu, 07 Feb 2013 23:16:00 +0000

“It is therefore my intent to make sure that this product class is fully
defined, specified (specificationified?) and in some form shipped by the
end of this year.”

So embarrassing.. and betrays a complete lack of grounding in reality. Who is this guy?

Comment on Web Browsers and Web Weavers by Captain Lyre Calliope

Captain Lyre Calliope — Thu, 07 Feb 2013 23:09:00 +0000

“It is therefore my intent to make sure that this product class is fully
defined, specified (specificationified?) and in some form shipped by the
end of this year.”

Wow. That’s a little embarrassing. ;)

Comment on on Webmaking Science by Webmaker TLDR: roadmaping for badges, social media and more | openmatt

Webmaker TLDR: roadmaping for badges, social media and more | openmatt — Fri, 01 Feb 2013 16:45:55 +0000

[...] Webmaking + Science. “The way in which knowledge is modeled in the human brain mirrors how the web works: like a directed graph.” [...]

Comment on Web Browsers and Web Weavers by Captain Lyre Calliope

Captain Lyre Calliope — Sun, 27 Jan 2013 22:23:00 +0000

Perhaps on the surface, but I’ve been tracking the team closely for awhile. The project evolved into https://singly.com/ and I’m pretty sure they still have their eyes on the prize.

Comment on Web Browsers and Web Weavers by Augustin Bralley

Augustin Bralley — Sun, 27 Jan 2013 20:31:00 +0000

Sadly the Locker Project has been abandoned. https://github.com/LockerProject/Locker

Comment on Why Mozilla? Manifesto and Milestones by Augustin Bralley

Augustin Bralley — Sun, 27 Jan 2013 20:11:00 +0000

“Apps still, more often than not, lead to silo-ed data.” Precisely the problem I’m trying to solve with Stardust. There needs to be a breakup in the one-to-one client-server model. Distributed apps, portable backends, discoverable schemas… returning to the concept of a user installing a program on “the user’s machine,” except now the machine is in the cloud or on a device, shares across origins, open source, enforces link contracts, etc. Mozilla does seem the most likely of institutions to progress this vision, but as yet have fallen short.

Comment on rambling on fractal automata by Augustin Bralley

Augustin Bralley — Sun, 27 Jan 2013 19:22:00 +0000

I love the spirit pulsing through this post. I’ve felt moved by the same. These are great times of technology augmented potential. How fortunate are we to be able to remake the world? ;)

Comment on on Webmaking Science by Captain Lyre Calliope

Captain Lyre Calliope — Sun, 27 Jan 2013 07:03:00 +0000

Relevant: “Making the web work for science: Kaitlin Thaney on the value of open science and why broken methods are blocking big advances.” radar.oreilly.com/2013/01/kaitlin-thaney-open-science.html

Comment on Why Mozilla? Manifesto and Milestones by Webmaker TLDR: 2013 roadmap, credit for badges and more | openmatt

Webmaker TLDR: 2013 roadmap, credit for badges and more | openmatt — Fri, 25 Jan 2013 16:39:53 +0000

[...] Why Mozilla? Lyre | Does the Mozilla manifesto need revising? How do we make the most of Mozilla’s upcoming 15th anniversary? What will the next 15 years hold? [...]

Comment on Markup APIs and the Read/Write Web by Webmaker 2013 Roadmap 0.1 |

Webmaker 2013 Roadmap 0.1 | — Wed, 23 Jan 2013 17:42:17 +0000

[...] On the tools side, we will begin to merge our web apps together. We want users to have a “Webmaker” experience, rather than separate Thimble, Popcorn, and OpenBadger modalities. These code bases and projects won’t go away – Webmaker.org will simply become a “client” of the great foundational open source projects we’ve created over the past 2 years. The recent demo of Webmaker X (see screencast below, and Doug Belshaw’s excited blog post here, as well as Lyre’s breakdown on how MarkupAPIs could be a game changer here.) [...]

Comment on Markup APIs and the Read/Write Web by Webmaker TLDR: what’s up with Webmaker this week? | openmatt

Webmaker TLDR: what’s up with Webmaker this week? | openmatt — Thu, 17 Jan 2013 17:49:19 +0000

[...] Markup APIs and the Read/Write Web. “Apps with APIs will be growing veins into the rest of the web more and more.” [...]

Comment on Markup APIs and the Read/Write Web by Captain Lyre Calliope

Captain Lyre Calliope — Thu, 17 Jan 2013 07:39:00 +0000

It now occurs to me that Markup APIs can declare UI for editing their functionality in Webmaker using Web Intents/Activities. This decouples things even further in a way that makes things hella more collaborative!

Comment on Web Components and Mozilla Webmaker by Michelle Thorne

Michelle Thorne — Wed, 16 Jan 2013 12:58:00 +0000

Thanks for this really thoughtful post! I love the very concrete experiments we could try plus the broader implications of Web Components + Webmaker. The widget directory is also brilliant, as it’d encouraging sharing and remixing.

Comment on Markup APIs and the Read/Write Web by kinlane

kinlane — Wed, 16 Jan 2013 03:27:00 +0000

Great post! Such an important evolution for not just APIs, but the entire web. So much potential.

Comment on Web Components and Mozilla Webmaker by Markup APIs and the Read/Write Web | captain's blog

Markup APIs and the Read/Write Web | captain's blog — Tue, 15 Jan 2013 22:12:26 +0000

[...] my previous post on how Web Components should inform the Mozilla Webmaker roadmap I make mention of ‘widgets, buttons, and badges.’ The context behind this grouping of [...]