Archive for the ‘Open Services’ Category

Faded sidebar

Sunday, January 22nd, 2012

I’ve occasionally mucked with my blog’s theme with a general aim of removing superfluous crap that makes reading posts harder. A couple weeks ago something Parker Higgins wrote inspired me to try a little harder:

How awesome is @niemanlab’s “faded” sidebar? And zen mode? That’s a site that cares about its readers.

You can view an archived version of the Nieman Lab site should their design change. The top of the sidebar isn’t faded, but overall I think the fading there is makes it a little easier to concentrate on a post without switching to “zen” mode (removing all navigation).

For my theme, I made the sidebar always faded except when hovered over, and float to the right as far away from the main content area as possible. All “header” content is in the sidebar so that there’s nothing preceding a post’s title.

I intended to remove anything hardcoded* for my blog, anything I don’t understand or not used, and anything that doesn’t validate, but I didn’t get very far on any of those. I doubt this will be useful to anyone, but patches welcome.

*Yes it is also a little ironic I’ve never bothered to published modified source used to run this blog until now.

End of the 2011 world

Saturday, December 31st, 2011


I took the above photo near the beginning of 2011. It has spent most of the year near the top (currently #2) of my photos hosted at Flickr ranked by their interestingness metric. Every other photo in the 200 they rank (sadly I don’t think anyone not logged in as me can see this list) has some combination of being on other people’s lists of favorites, comments, or large number of views. The above photo has none of that. Prior to this post it has only been viewed 33 times by other people, according to Flickr, and I don’t think that number has changed in some time. Their (not revealed) code must find something about the image itself interesting. Is their algorithm inaccurate? In any case the image is appropriate as the world of 2011 is ending, and in 2012 I absolutely will migrate my personal media hosting to something autonomous, as since last year someone (happens to be a friend and colleague) has taken on the mantle of building media sharing for the federated social web.

My employer’s office moved from San Francisco to Mountain View in April, contributing to a number of people leaving or transitioning out, which has been a bummer. I’ve been working exclusively from home since May. Still, there have been a number of good developments, which I won’t attempt to catalog here. My favorites include agreement with the Free Software Foundation regarding use of CC0 for public domain software, small improvements in the CC legal user interface, the return and great work of a previous colleague, retirement of two substandard licenses, research, and a global summit/launch of a process toward version 4.0 of the CC licenses, which I hope over the next year prove at least a little bit visionary, long-standing, and have some consideration for how they can make the world a better place.

Speaking of which, I’ve spent more time thinking about social science-y stuff in 2011 than I have in at least several years. I’ll probably have plenty to say regarding this on a range of topics next year, but for now I’ll state one narrow “professionally-related” conclusion: free/libre/open software/culture/etc advocates (me included) have done a wholly inadequate job of characterizing why our preferences matter, both to the general public and to specialists in every social science.

Apart from silly peeves, two moderate ideas unrelated to free/libre/open stuff that I first wrote about in 2011 and I expect I’ll continue to push for years to come: increasing the minimum age and education requirement for soldiers and tearing down highway 980.

I haven’t done much programming in several years, and not full time in about a decade. This has been making me feel like my brain is rotting, and contributes to my lack of prototyping various services that I want to exist. Though I’d been fiddling (that may be generous) with Scala for a couple years, I was never really super excited about tying myself to the JVM. I know and deeply respect lots of people who doing great things with Python, and I’ve occasionally used it for scripts over the past several years because of that, but it leaves me totally non-enthused. I’ve done enough programming in languages that are uglier but more or less the same, time for something new. For a couple months I’ve been learning and doing some prototyping using the Yesod web framework (apparently I had heard of Haskell in 2005 but I didn’t look at it closely until last year). I haven’t made as much progress as I’d like, mostly due to unrelated distractions. The biggest substantive hurdle has not been Haskell (and the concepts it stands for), but a lack of Yesod examples and documentation. This seems to be a common complaint. Yesod is rapidly moving to a 1.0 release, documentation is prioritized, and I expect to be really productive with it over the coming year. Thanks to the people who make Yesod and those who have been making Haskell for two decades.

This year I appreciated three music projects that I hadn’t paid much attention to before, much to my detriment: DNA, Moondog, and especially Harry Partch. I also listened a lot again to one of my favorite bands I discovered in college, Violence and the Sacred, which amazingly has released some of its catalog under the CC BY-SA license. Check them out!

Finally, in 2011 I had the pleasure of getting to know just a little bit some people working to make my neighborhood a better place, attending a conference with my sister, seeing one of my brothers start a new job and the other a new gallery, and with my wife of continuing to grow up (in that respect, the “better half” cliche definitely applies). Now for this world to end!

Namecheap’s savvy anti-SOPA marketing

Thursday, December 29th, 2011

I’m impressed by how much gratis publicity and advertising has gotten via its anti-SOPA marketing (including the Wikipedia article I linked to; it didn’t exist 3 days ago), and completely unimpressed by the failure of approximately every other company to take advantage of the opportunity, which strikes me as easy social media gold. Communications department heads ought roll.

* pro-SOPA marketing failures made Namecheap’s action straightforward relative to companies not directly competing with Go Daddy. However, there are lots of other domain name registrars, none of which has done anything with Namecheap’s marketing savvy. Another registrar, (which I’ve used and recommended for some time, and has supported Creative Commons and other good causes), like Namecheap is donating a portion of domain transfers to the Electronic Frontier Foundation, but doesn’t seem to be making a big deal of it, and their anti-SOPA blog post is rather tepid. Compare to Namecheap’s anti-SOPA blog post, which isn’t all that much stronger in terms of substance (contains genuflection to “intellectual property”), it is much more strongly worded and simply more effectively written.

One other company has a support-EFF-against-SOPA tie-in. That company, Zopim, provides website chat services, and doesn’t seem to compete with Go Daddy at all. I’m not interested, but never would have heard of them otherwise. Any company could do that.

(I see that sometime today two other small domain registrars have added support-EFF-against-SOPA deals. Good for Suspicious Networks and Centuric.)

What inspired to me write this post is that Namecheap isn’t only taking gratis publicity. They’re also running presumably paid ads as part of their anti-SOPA marketing campaign:

While trying to get the above ad to load again (noticed out of the corner of my eye but didn’t register until sometime after — I’m oddly trying to recover from ad blindness), I noticed another Namecheap ad, which if you’re already really tuned in, illustrates nicely the imperfect options available from a software freedom perspective for domain registration and other nearly commodity services.

Check out more anti-SOPA and pro-freedom actions.

*Isn’t the name “Go Daddy” ridiculous? That, coupled with a super cheesy website and company logo led me to disregard them long before they started shooting sexy elephants at gladiator events, or whatever got people upset before they supported SOPA.

Invitation systems and the Federated Social Web

Sunday, December 25th, 2011

Notes prompted by a conversation, but not in direct response to anything therein.

I have not seen obvious for web sites used much recently, but that could be me not looking for web applications to try. I note three three overlapping purposes when they are used:

  • Promotion. The entity that has set up the invitation system hopes for viral spam; some people have a strongly negative reaction to invitation systems as a result.
  • Rationing. For example, to keep a system usable while resources added.
  • Exclusivity. For purposes regarded as wrong for non-state actors (e.g. discrimination based on birth location) to the suspicious (supposed cabals) to the practical (privacy, working group size, keep out bad actors).

My impression is that at the web site/application level, invitations are used mostly for promotion, a little for rationing, rarely for exclusivity. But invitations are ubiquitous in human interactions, and it seems to me that exclusivity is their main purpose (though I’m ignoring many communications and social purposes independent of the three mentioned; e.g., in some situations a polite communication takes the form of an invitation). One doesn’t even need to step away from “social network” web applications to see this, just into the applications — consider “connection requests” and similar actions among users.

Invitations could be a useful part of the federated social web mix, as the challenges faced by federated sites are at least a little different than those faced by silos in all three of the aforementioned areas, but especially with regard to exclusivity. Consider that bad actors can set up their own federated sites, and that federated sites often represent single users or small communities — roughly requiring the same functionality of a community or individual user of a silo, including the functionalities of the entire silo.

Also, just remembered On The Invitation, a chapter from Collaborative Futures.

Mozilla $300m/year for freedom

Thursday, December 22nd, 2011

More Mozilla ads by Henrik Moltke / CC BY

Congratulations to Mozilla on their $300m/year deal with Google, which will more than double current annual revenue. I’ve always thought people predicting doom for Mozilla if Google failed to renew were all wrong — others would be happy to pay for the default search position; probably less since Microsoft, Yahoo, and others make less than Google per ad view, but it’d still be a very substantial amount — and the link article hints that a Microsoft bid drove the price up.

There’s always a risk that Mozilla won’t spend the money well, but I’m pretty confident that they will. Firefox is excellent, and in 2011 has gotten more excellent, faster, and I think many of the other projects they’re doing are really important, and on the right track (insofar as I’m qualified to discern, which is not much), for example BrowserID. Even in small and hopelessly annoying things, like licensing, I think Mozilla is doing good. (Bias: Mozilla has donated to my employer.)

I’m no longer enthused about the possibility of huge resources for progress toward Wikimedia’s vision from advertising on Wikipedia. Since I was last on that bandwagon, it has become even less of a possibility in anything but the distant future: Wikimedia’s donation campaigns have gone very well, adequately funding its operating mission, and lack of advertising has become even more part of Wikimedia’s messaging; I’ve also become more concerned (not in particular to Wikimedia) about the institutional corruption risks previously blogged by Peter McCluskey and Timothy B. Lee. (Note these objections don’t apply to Mozilla: its significant revenue has always been advertising-based; very roughly its revenues are already 10x those of Wikimedia’s; and it is also building up an individual donor program, which I agree is often the healthiest revenue for a nonprofit.)

But I still very much think freedom needs massive, ongoing resource infusions, in the right institutional framework. I celebrate the tremendous benefits of the FLOSS community achieves without massive, concentrated, ongoing resource infusions, but I also admit that the web likely would be much worse, much less webby, and much less free without concentrated resources at Mozilla over the last several years.

Thank you Mozillians, and congratulations. I have very high expectations for your contributions over the next years to the web and society, in particular where more freedom and security are obviously needed such as mobile and software services. Such would be just a start. As computation permeates everything, and digital freedom becomes the most important political issue, the resources of many Mozillas are needed. More on that, soon.

7 FLOSS trends of the past 37.5 months

Monday, September 12th, 2011

A prospective, from memory, high level summary of trends in Free/Libre/Open Source Software, in the last 37.5* months:

Design. Many major free software projects have turned in some form to design[er]-driven UX/UI/look-and-feel/etc. Not all (any?) are acclaimed successes yet, but in a few years “open design” may go from paradoxical to hot.

Diversity. Lack thereof has become recognized as a major impediment to FLOSS potential. Existing cultures will change as participation expands and vice versa.

Distributed version control systems. Have changed the way many developers and projects work.

Governance. “Open by rule” governance that treat all participants equally and are run transparently has become recognized as a crucial part of making FLOSS FLOSSY, in addition to (and congruent with) FLOSS licensing. However, some advocate for corporate (usually) controlled projects in order to obtain corporate resources for FLOSS development. GPLv3 has seen strong uptake.

Mobile. Unlike the desktop a mostly free system (Android) is very popular, but also unlike the desktop, mobile devices with approaching 100% FLOSS[Y] software more or less don’t exist. The “appstore” phenomena is recognized as a threat to FLOSS, but it is totally unclear how that will play out.

Net services. Apart from Wikipedia, none of the dominant services people access through the web are free software. Most are largely powered by free software, and companies that run the services contribute much to back-end software, but the services users directly access are proprietary and centralized, with no interoperability among them. FLOSS and federated social web services have made strides but there is much significant technical work to do, and the network effects of the dominant proprietary services are daunting.

Open web. In 2008, Firefox 3 had just been released and Flash was ubiquitous. The “open web” is in much better shape now. It is the platform with the most innovation, is almost entirely based on open standards. As of fairly recently, the prognosis even for open web video looks good. One of the leading browsers, Firefox, is free software, and the free software WebKit renderer powers most others, while IE slowly declines.

I’ve surely missed things, some intentionally (patent threat), some out of partial ignorance (e.g., I don’t have any sense of how much has changed in the last 3 years for FLOSS as a grant, procurement, regulatory, or other “policy” requirement, but know it could be important).


*37.5 months ago Creative Commons held its previous global meeting. Another will be held next week. I’m organizing 2.33** sessions, one of which will touch on movements near Creative Commons (“Where are We?”) and another of which concerns these in depth (or as much as is possible in 80 minutes; “CC’s Role in the Global Commons Movement”).

The CC-specific parts of these sessions will be fairly detailed and for the first one, possibly more interesting to insiders (many of the participants have been involved in CC affiliate projects for most of CC’s history).

I’d also like to convey, perhaps in as little as one slide, the big trends of the last 3 years in a few related areas, without any details. These areas and their trends lead, inform, reinforce, and depend on CC’s work in varying measures, so I think the CC community should understand them at a high level at least, such that the most relevant can be more closely learned from or cooperated with.

**I’m also organizing 1/3 of a session on issues to consider for version 4.0 of the CC license suite; the part I’m organizing concerns the non-commercial clause used by some of those licenses. I promise it will be much more fun than a report on that topic.

Creative Commons hiring CTO

Monday, July 11th, 2011

See my blog post on the CC site for more context.

Also thanks to Nathan Yergler, who held the job for four years. I really miss working with Nathan. His are big shoes to fill, but also his work across operations, applications, standards, and relationships set the foundation for the next CTO to be very successful.

Semantic ref|pingback for re-use notification

Sunday, May 15th, 2011

Going back probably all the way to 2003 (I can’t easily pinpoint, as obvious mail searches turn up lots of hand-wringing about structured data in/for web pages, something which persists to this day) people have suggested using something like trackback to notify that someone has [re]used a work, as encouraged under one of the Creative Commons licenses. Such notification could be helpful, as people often would like to know someone is using their work, and might provide much better coverage than finding out by happenstance or out-of-band (e.g., email) notification and not cost as much as crawling a large portion of the web and performing various medium-specific fuzzy matching algorithms on the web’s contents.

In 2006 (maybe 2005) Victor Stone implemented a re-use notification (and a bit more) protocol he called the Sample Pool API. Several audio remix sites (including ccMixter, for which Victor developed the API; side note: read his ccMixter memoir!), but it didn’t go beyond that, probably in part because it was tailored to a particular genre of sites, and another part because it wasn’t clear how to do correctly, generally, get adoption, sort out dependencies (see hand-wringing above), and resource/prioritize.

I’ve had in mind to blog about re-use notification for years (maybe I already have, and forgot), but right now I’m spurred to by skimming Henry Story and Andrei Sambra’s Friending on the Social Web, which is largely about semantic notifications. Like them, I need to understand what the OStatus stack has to say about this. And I need to read their paper closely.

Ignorance thusly stated, I want to proclaim the value of refback. When one follows a link, one’s user agent (browser) often will send with the request for the linked page (or other resource) the referrer (the page with the link one just followed). In some cases, a list of pages linking to one’s resources that might be re-used can be rather valuable if one wants to bother manually looking at referrers for evidence of re-use. For example, Flickr provides a daily report on referrers to one’s photo pages. I look at this report for my account occasionally and have manually populated a set of my re-used photos largely by this method. This is why I recently noted that the (super exciting) MediaGoblin project needs excellent reporting.

Some re-use discovery via refback could be automated. My server (and not just my server, contrary to Friending on the Social Web; could be outsourced via javascript a la Google Analytics and Piwik) could crawl the referrer and look for structured data indicating re-use at the referrer (e.g., my page or a resource on it is subject or object of relevant assertions, e.g., dc:source) and automatically track re-uses discovered thusly.

A pingback would tell my server (or service I have delegated to) affirmatively about some re-use. This would be valuable, but requires more from the referring site than merely publishing some structured data. Hopefully re-use pingback could build upon the structured data that would be utilized by re-use refback and web agents generally.

After doing more reading, I think my plan to to file the appropriate feature requests for MediaGoblin, which seems the ideal software to finally progress these ideas. A solution also has obvious utility for oft-mooted [open] data/education/science scenarios.

IE6 is a stark reminder to developers of what a Web monoculture looks like. We need to remember it.

Tuesday, March 22nd, 2011

The title of this post quotes Evan Prodromou.

See Internet Explorer 6 criticism for the baneful details.

Firefox broke the monoculture. Today is a good day to remember, and celebrate, as Firefox 4 is released. I’ve been using alphas and betas for many months; highly recommend.

Given the quote from Prodromou, founder of identi.ca/StatusNet and first among federated social web equals, it’s also a good idea to remember that many of the services that dominate their niches on the web are themselves monocultures. It was really great yesterday to see the EFF explain and get behind the federated social web.

Be a good citizen today — here’s another helpful and current link in that regard.

Federated Social Web Status[Net]

Friday, December 31st, 2010

Evan Prodromou just published his Federated Social Web top 10 stories of 2010. It’s a great list, go read — readers who aren’t already familiar with Prodromou, StatusNet, identi.ca, OStatus, etc. probably will have missed many of the stories — and they’re extremely important for the long-term future of the web, even if there are presently far too few zeros following the currency symbol to make them near-term major news (just like early days of the web, email, and the internet).

I suggest the following additions.

Censorship of dominant non-federated social web sites (e.g., Facebook, Twitter, YouTube) occurred around the world. While totally reprehensible, and surely one of the top social web stories of 2010 by itself, one of its effects makes it a top story for the federated social web — decentralization is one of the ways of “routing around” censorship. I’d love to have mountains more evidence, but perhaps this is happening.

Perhaps Evan did not want to self-promote in his top 10, but I consider the status of his company, its services, the software they run (all called ), and the community around all three, to be extremely important data points on the status of the federated social web, and thus inherently top stories for 2010 (and they will be again in 2011, even if they completely fail, which would be a sad top story).

I hope that Evan/StatusNet post their own 2010 summary, or the community develops one on the StatusNet wiki, but very briefly: The company obtained another round of funding and from the perspective of an outsider, appears to be progressing nicely on enterprise and premium hosting products. The StatusNet cloud hosts thousands of (premium and gratis) instances, and savvy people are self-hosting, mirroring the well-established wordpress.com/WordPress pattern. The core StatusNet software made great strides (I believe seven 0.9.x releases), obtained an add-ons directory, and early support for non-microblogging features, e.g., social bookmarking and generic social networking (latter Evan did mention as a non-top-10 story; of course any such features are federated “for free”). By the way, see my post Control Yourself, Follow Evan for the beginning story, way back in 2008.

2010 also saw what I consider disappointments in the federated social web space, each of which I have high hopes will be corrected in the next year — perhaps I’ll even do something to help:

StatusNet lacks full data portability and account migration.

Nobody has yet taken up the mantle of building a federated replacement for Flickr.

Unclear federated social web spam defenses are good enough.

Nobody is doing anything interesting with reputation on the federated social web — no, make that, on the social web. This is a major befuddlement I’ve had since (2002), at least. had an excuse as the first “social network”, (1999) innovated, then nothing. Nothing!

Far too few people are aware of the challenges and opportunities of maintaining and expanding software freedom/user autonomy in the age of networked services, a general problem of which the federated social web is an important case.

Finally, a couple not-yet-stories for the federated social web.

Facebook and Twitter (especially Facebook) seem to have consolidated their dominant positions in nearly every part of the world, having surpassed regional leads of the likes of Orkut (Brazil and India), Bebo (UK), MySpace (US), Friendster (Southeast Asia), etc. and would-be competitors such as shut down (e.g., Jaiku and Plurk) or considered disappointing (e.g., Google Buzz). However, it seems there are plenty of relatively new regionally-focused services, some of which may already be huge but under the radar of English-speaking observers. An example is , Sina.com’s microblogging service, which I would not have heard of in 2010 had I not seen it in use at Sharism Forum in Shanghai. It’s possible that some of these are advantaged by censorship of global services — see above — and cooperation with local censors. Opportunity? Probably only long-term or opportunistic.

Despite their high cultural relevance and somewhat ambiguous status, I don’t know of many © disputes around tweets, or short messages generally. Part of the reason must be that Twitter and Facebook are primarily silos, and use within those silos is agreed to via their terms of service. I’m very happy that StatusNet has from the beginning take precaution against copyright interfering with the federated case — notices on StatusNet platforms are released under the permissive Creative Commons Attribution license (all uses permitted in advance, requiring only credit), which clarifies things to the extent copyright restricts, and doesn’t interfere to the extent it doesn’t. (Also note that copyright is a major challenge for the social web in general, even its silos — see YouTube, which ought be considered part of the social web.)

All the best to Evan Prodromou and other federated social web doers in 2011!

As demonstrated above, I cannot write a short blog post, which puts a crimp on my blogging. Follow me on StatusNet’s identi.ca service for lots of short updates.