https://twit.tv/shows/triangulation/episodes/264
Plus an article in the Chronicle of Higher Ed
http://www.chronicle.com/article/How-Gopher-Nearly-Won-the/237682
Tagged: #gopher
1 min read
https://twit.tv/shows/triangulation/episodes/264
Plus an article in the Chronicle of Higher Ed
http://www.chronicle.com/article/How-Gopher-Nearly-Won-the/237682
Tagged: #gopher
1 min read

Didn't realize I was doing "ledgers" way back at the University of Minnesota. As you can see we weren't that excited writing line-of-business apps. Also funny how Privacy Enhanced Mail never took off. Pity that.
Here's the executive summary for Forms Nirvana from an old design doc:
This document describes an open-architecture forms routing and approval system suitable for routing requests through a multi-person authorization chain. Once a request has been authorized, the completed request can be automagically submitted to another system (for example, the financial system for posting to the general ledger). While WWW is initially envisioned as the vehicle for user interaction with the system, the request routing logic is separated from user presentation so that other technologies (such as E-mail with digital signatures) can be used as well. Provisions are also made for entities other than human signers to be part of the authorization chain, so consistency checks can be automatically applied to the form's content.
Tagged: #throwbackthursday
Original: http://www.1500wordmtu.com/2016/behold-formsnirvana-the-internal-only-logo-from-1996-at-umn
1 min read
#umn" />Didn't realize I was doing "ledgers" way back at the University of Minnesota. As you can see we weren't that excited writing line-of-business apps. Also funny how Privacy Enhanced Mail never took off. Pity that.
Here's the executive summary for Forms Nirvana from an old design doc:
This document describes an open-architecture forms routing and approval system suitable for routing requests through a multi-person authorization chain. Once a request has been authorized, the completed request can be automagically submitted to another system (for example, the financial system for posting to the general ledger). While WWW is initially envisioned as the vehicle for user interaction with the system, the request routing logic is separated from user presentation so that other technologies (such as E-mail with digital signatures) can be used as well. Provisions are also made for entities other than human signers to be part of the authorization chain, so consistency checks can be automatically applied to the form's content.
You can read more about Forms Nirvana in this Minnpost article.
Tagged: #throwbackthursday
3 min read
I'm still pretty happy my indieweb publishing experiment.
Content is flowing in all the right ways. Posts end up as Posts. Photos are uploaded native with backlinks. POSSE via brid.gy just works. You can see that Brid.gy polls Google+, and then saves what it finds back to the original post by sending Webmentions. The result is a full archive of activity around this content.
![]()
![]()
Oh and cross posting to SoundCloud worked perfectly. And so do embeds..
After a fix from the Known Team WebHooks are working. I get a POST whenever content changes. To test this out I send the URL to the Internet Archive Save Page. Voila! Instant archiving of my content. [Next up, backups in IPFS]
I was able to set up the Known open source software on my own server. Next step is to pull a backup from the hosted version I'm using so I can experiment further and contribute back to the project.
Mobile Posting via Chrome on Android is working well. You can access the Camera and a rudimentary file picker. HTML editing is workable, but not great. I installed the Url Forward app so I can also have native sharing intents.
Of course there are some issues encountered...
Spelling errors mean you Publish Once, Edit Everywhere. Or if you messed up the URL, Publish Once, Delete Everywhere
I tried using a native web mention to reply to another post, but it didn’t appear on the target site. There wasn't any visible UX feedback.
I found that there’s no UI support for backdating posts. Okay, I’ll try Micropub to post. Nope, very rough implementations, but Quill seems nice. Eventually I wrote a stub post in Wordpress, exported, imported and edited. Phew!
But.. it appears that brid.gy doesn’t syndicate to old posts like this. Even when I went back and pointed links at each other. I’ll have to followup on that.
Also, I lost the first version of this post due to a CSRF error since I left it sitting too long in the browser. Oops.
TinyMCE still is a pain and loves using and CMD-9 is bound to <address>.. I might have to use Markdown instead.
I miss @ mentioning people, and wish there was a UI for that.
Native Google+ support in brid.gy needs an API.
But still overall quite happy with the way this is going. I hope you're enjoying the journey with me.
Tagged: #indieweb #withknown
1 min read
W3C Blockchains and the Web Workshop Report
Lots and lots of content to digest from this workshop in June. I'm really excited to see IPLD, which brings actual URNs to life.