I think the market is, on average, more supportive of #foss and #indieweb products and services than seed stage and angel investors are.
I just downloaded my tweet archive. Here are a few tweets I found:
The 4 in Deadmau5′ 4×4 = 12 is actually an A, and A = sqrt(12). #leetspeek 16 feb 2012
Hmm, “json” ends with the same letters (and for me, sound) as “python”. Two new words: jsonic and jsonista! 5 oct 2010
I’m in a Wave about Boulder with @HKoren. We’re using photos, and lots of threads. I’m learning more about it. Anyone want to join? @ or DM. 24 nov 2009
crayfish 4 Oct 12
Actions I might find in an ideal micropost reading tool:
skip: some things should just be removed from my stream. there are valid reasons not to unfollow someone despite not wanting to read their content. I should also be able to silence things based on content.
- sift: my massive feed should have a way for me to type what I’m interested in at the moment, and see items (posts, microposts, commits) about it.
- skim: there should be a smaller feed of stuff I want to have a chance to read, that I can quickly scroll through.
- read: some things I actually want to read. this should be smaller still.
- reply: unlike the above, these will have to be ticked off one by one.
- act: I feel I don’t act on what I read often enough. When someone I follow writes a nifty new library I should actually install it and try it out, and offer feedback.
Finally, catching up on items from my streams should feel like work more often. Using some of these networks directly is biased towards goofing off.
You’re correct, the routing mesh does not behave in quite the way described by the docs. We’re working on evolving away from the global backlog concept in order to provide better support for different concurrency models, and the docs are no longer accurate. The current behavior is not ideal, but we’re on our way to a new model which we’ll document fully once it’s done.