Archives For StatusNet

PuSHPress 0.1.7.2

June 13, 2013 — Leave a comment

Updated to PuSHPress 0.1.7.2, networks-wide. That means we has a PuSH hub built-in, and services can use your normal feed (i.e. http://interi.org/feed/) to subscribe. This functionality had either been broken in past versions, or didn’t work on a WordPress network, but now it is working. I am using it to mirror this site into my StatusNet account.

Eventually I am planning on getting the parts of OStatus working that allows for replying directly to the site, but even more interesting is resurrecting some of the plugins that the OStatus suite was based on, and making WordPress talk to a lot of different federated systems. Of course we still don’t have an interface for reading the streams from other systems… but it isn’t a bad idea!

I think PuSHPress is working correctly, which means this should be push from my WordPress site to StatusNet.

Federation is hard

February 4, 2013 — Leave a comment

Federation is hard. Especially on the social web.

Continue Reading...

Thinking in wiki

December 30, 2012 — 2 Comments

I’ve been really into wikae lately, as is apparent by how much I written about it. A wiki is a particular set of features and workflows, and it has its own mindset.

I am thinking in wiki.

This site is becoming more of a journal, where my posts are either about flash in the pan events, or part of longer thought out articulations. The frequency of posts has gone down, because I am doing more mind-mapping in other places, like text files in git repos, and in various wikae.

It has brought a few things to light for me, about how I write, and what I am trying to create. Here are a few examples:

  • Temporality – A lot of the things (most?) I blog about are not important to me after a few months. That means I have old announcement posts and tons of broken links that have no value, but I keep them to provide temporal context. I am not convinced it is that useful.
  • Anti/Social – I think blogging is very important, but it does bother me that blogs are essentially silos. This isn’t really a critique, just that instead of loading up blogs with like buttons and allowing people to leave comments with their social network credentials, it is probably more worthwhile for the majority of bloggers to assess what collaboration looks like for them.
  • Our tools are aging – The software that runs some of the most important spaces on the web, like MediaWiki and WordPress, were developed a long time ago. It is easy to find feature requests from years ago, still being pleaded for. Again, not a critique, just an observation of what popularity does to software, and how dominance affects the culture and motives of the community that supports it.

These aren’t new, obviously. It is just me glancing at the gap between two software projects/workflows (WordPress/blogging and MediaWiki/wiki). Then I think about StatusNet, and how it looks like it could be practically abandoned for other projects. In one sense, that is a bummer, and I’ve invested a lot of time in it. On the other hand, maybe it isn’t so bad for things to get torn down and built back up, especially considering the transient nature of status updates, almost all of which are unimportant to me a few days afterward.

I’ve really pushed MediaWiki hard in the last couple of months. I’ve bumped up against a lot of walls, and some of them stopped me. But overall, I am happy with the result, which is a system to collaborate with those that want to, and a relatively decent way to create bodies of useful content. I am rushing as fast as I can to configure all the extensions I think I will need, so I can eventually just focus on creating. That will be the real test.

I think that instead of running my own StatusNet instance, I am just going to use identi.ca instead.

Diaspora didn’t have a clear problem to solve. Who else is working on something like this?

Continue Reading...

I am sure # will have something in place. I know "favorite-ing" things federates across #, so that might happen! And also, I love eir crafty eyes! ^_^

I would like to see more development on very specific parts of # I want to make it less enterprise, and encourage people to make more micro-apps. And getting export/import working would be dope. Where do we start? Is there an org out there that we can tap for crowd-funding specific improvements? I don’t code, so I don’t know how projects work that out. But I am willing to try!

The author says that # is not designed to be used the way I use it. And the 7 other people I host an SN instance for. @evan, why aren’t you making it easier for me to use StatusNet the way I use it?! Also, what is Twitter?

I don’t want to minimize what you are experiencing, but I want to mention that running my own # instance gives me a lot more tools to deal with folks like that. You shouldn’t have to leave a community because of harrassment, but if it comes to that I can help with installation.