This is a very cool think I got to do at work. We ended up doing a uStream simulcast with an international OCD advocacy group in the middle of my foundation's annual gala.
My friend Kristen Love, an outgoing advocate for OCD recovery, spoke to our group of about 400 people, and then also an online audience of 500-700 people.
I want to share more about how the technology worked and didn't work, but first, I think its very important not to overshadow the event itself. It was an amazing thing.
Here's an un-edited Ustream recording of the live portion of our program.
Its an amazing, honest look at OCD and OCD recovery. Kristen's willingness to share this story is a gift to us all. Thank you Kristen.
I like this comment on Read-Write-Web.
400 million people now use Facebook, and they don't all have CS Master's degrees from Stanford. But if you work in the IT/tech/Internet/online media industries, they do manage to pay your bills. They're the ones who open emails, click ads, make purchases, sign up for subscriptions and generally take the majority of actions that make our whole ecosystem work.
And most of them have no idea what a web browser is or how it differs from a search engine or a social network. They've chosen to be smart about other things, like building cars or making art or raising families. I'll bet some of them are terrific dancers. We have to build the Web for them, too.
This pretty much sums up how I feel about Web414's future. Web414 is for the people who are working together to make The New Web(tm). It can't be monitized or productized. It's about people who want to build cars, make art, raise families and dance in new ways using the web as a platform.
Who is Web414 for? It's for me. Its for you. Its for the community. Its for who we are who chose to be part of Web414. Web414 is the music makers, and it is the dreamers of dreams. Don't spoil it by making it into just another pointless meetup. Web414 is the magic store. Web414's like a movie, write your own ending... keep believing, keep pretending ... We've done just what we set out to do, Thanks to the lovers, the dreamers, and you.
Web414 must remain dedicated to being more than the sum of its parts. Web414 must be a place where we are free to follow our passions and are unencumbered by "making it work." Web414 works because it does. It is a group of people in a single place making great creative things happen on, for, and about the Web.
I don't normally like to repost content from other sites I work on, but I enjoyed this producing this show too much not to put it here.
It's the Welcome and Monologue from the July 9, 2009 Web414 Show.
You can keep tabs on my exploits at the Web414 show by visiting Web414.com. It's only going to get better.
Did you guys see that the Web414 show is still goin' strong? Even though I was too scattered on June 11th to really do a good job with as the host, I have put together a clip on the monologue on the Web414 Blip.tv channel.
I love the new Web414, even if I bomb now and then. Bombing is good for the soul, sometimes. Call it a Hubratic Cleansing. Is Hubratic a word? Probably not.
The best way to know when I've got new stuff up on those sites is to subscribe! What? I have to teach you bout RSS now?
I'm really looking forward to Web414 tonight-- I don't think there are any plans to webcast it, so you should definitely come by.
At first I didn't think we'd need to have a meeting so close on the heels of a virtuous and successful BarCampMilwaukee, but in retrospect, now I'm glad for the chance to get together with the gang and breakdown the BarCampMK3 experience. I just hope we're far enough removed from it so that we can realistically assess what total failures we all are. Things like Freely exchanging ideas and inspirations and building on one another's passions are great and all, right, but will they feed a hungry orphan? Will the turn a frown upside down? Will they translate sarcasm across a textual experience? No. Of course they won't. I propose that BarCamps, in and off themselves, are for wankers. And that, when it comes right down to it, at the end of the day, we're all wankers.
The thing is, we're still int he Barcamp Honeymoon phase, right? After every Barcamp that I've been involved in, there is this period for a couple of weeks afterward that everybody is really high on the BarCamp experience and wants to do stuff and get thigns done and "hold a barcamp every three months," and stuff.
Here's a far-be-it-from-inclusive list of post BarCampMilwaukee Three Projects that have been launched in the not-quite-four-days since BarcampMK3 ended:
- WriteCamp (Reboot)
- A Sex With Ashe podcast
- Justin's iCal for next year that doesn't have anything on it.
Will these things grow and evolve into THE NEXT BIG THING?
Fortunately, and so far, we've been able to stave off any kind kind of wide-spread excitement or passion for these projects. I'm proud to think that by really hanging on to our bitter disappointment and selfishness, we can probably continue to stave off doing interesting, intelligent things together in favor of a bleak post-McCain election depressive episode. We wouldn't want to make the world a better place. Shit. Can't let that happen.
I, hereby promise that I will make it my life goal to prevent meaningful communication, effectively stamping out meeting, talking, sharing ideas, and inspiring change. And it is for this reason that I am looking forward to Web414 tonight. For the good of the nation, Web414, If it is my job to be the urine stream in your open-source wikiflakes, a urine stream I shall be.
The "Put a drop in the Bucket" campaign has hit something of a snag over at Bucketworks. Too many drops, and the wrong kind.
With the weekend's storms, the Bucket's roof gave way and caused massive flooding in what is ironically referred to as "the Flowspace." (You might also know it as "the nice, finished area where Web414 usually meets.") Jenn has a short post up at Bucketworks.org, and Publisher Pete put some nice words down on screen, too.
Here's my take on it.
Bucketworks is a service and space unlike any other I've ever come across. We all laugh and throw around the term "physical wiki" when we talk about it, but really, Bucketworks is as close as you can get to the Utopian sigularlity described in Paul Di Filippo's Wikiworld. So, it makes sense then, that I would say that Bucketworks is ahead of its time. There will come a day when collaborative work, art, and playspace is just the standard setting for accomplishment. Until that day, pioneers like the gang at Web414, GLUE, Actor's Craft, Spreenkler, and all the rest will rely and depend on your donations to keep Bucketworks open.
That brings us to "Put a Drop in the Bucket." The gang at Bucketworks has been quietly asking for your financial support for a couple of weeks now. It costs Bucketworks about $350 a day to simply exist. Please support them. Although the details are still coming together as to how the flood damage will hit the Bucket's bottom line, its probably safe to say most of the repairs will be funded via insurance. (Bucketworks may be a hippiedippie physical wiki, but the folks running it aren't monkeys-- a business has disaster insurance. )
However, an organization as small as the bucket can't focus on too many crisis at a time. And recovering from the flood is going to be a priority in the short term. That's where you come in. Bucketworks certainly appreciates your willingness to pitch in and help clean up from the storm. And the best way you can do it: Drop some money in the bucket.
The storm and flooding damage may seem like a big deal-- and it is-- but the bigger deal is Bucketwork's financial future. In order to continue to exist as we know it, Bucketworks needs funding.
Full Disclosure: I proudly serve as a volunteer on the Bucketworks Board of Directors.
What I love about this photo taken by our friend John December is that it shows me using one of the most egregious security flaws in a modern software product to get Bucketworks' Ustream password out of Firefox.
If you let Firefox manage your passwords on a public computer you are exposing your passwords to anyone who comes along and knows to look.
Worse, there have been bugs that expose those passwords to the entire internet.
Use Firefox's master password feature to slap a small bandaid on this problem.
Dear Mr. Pete, et. all.
Please consider this post my sincere blessing and approval of any and all remixes of any and all of my posts to Jott, including but not limited to the profane tirade that was posted to Jott on Dec. 15, 2007.
Someone send me the MP3 and I'll host it right here.
And so there's no question about the license, I hereby designate any and all of my Jott recordings, including those I may make in the future, under a Creative Commons Sampling+ license.
My recordings on Jott are licensed under a
Creative Commons Sampling Plus 1.0 License.
This license only applies to my Jott Recordings and should not be applied to any other content appearing on Writelarge.com without my express consent. It does not supersede or change the license terms offered at Writelarge.com.
Item! Thanks to Mr. Raster, we've uploaded the file. Remix away!
It would be polite to mark this with a NSFW tag.
At the December Web414 meeting I gave a presentation on Prism (Don't call it Webrunner.) Thanks to the instructions on this fine post I did a meta-meta thing on my presentation by installing prism into a fresh virtualization of Ubuntu and using GoogleDocs to show my presentation. You can check out that presentation here. What I didn't have in my presentation was any kind of data about the difference between Prism's system footprint versus FireFox's system footprint.
So, here's a non-scientific comparison of Six Tabs in Firefox vs. Six instances of Prism all doing basically the same thing. First, I launched and logged in to six instances of prism. One each, running Google Docs, Gmail, Google Reader, Twitter, Last.FM, and Flickr.
And here's the System Resources window.
Then, I launched and opened the same six web sites in tabs in Firefox.
And here's the system resources window in that case:
It would appear that reducing your browser's impact on your system is not a significant reason to use Prism. Again, I didn't really study any kind of significant benchmarks beyond these basic screen shots, so if anyone has any scientific data that can prove me wrong, I'd love to see it.
That doesn't mean, either, than there aren't non-footprint-related reasons to use Prism. Separate processes, easy Desktop integration, reduced UI, and easy deployability are all reasons to put Prism on your machine.
These are all good reasons to encourage Prism's use, but it would appear, unscientifically, that reduced footprint ain't one of them.
Writelarge.com by Writelarge.com is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.