2,968 karma · joined October 27, 2008
The way the default licensing on Instagram works is: you hold copyright and Instagram has a non-exclusive right to use them in some ways. It doesn't permit usage outside of that. So if you wanted to use an image on your blog or in a Wikipedia article you'd be out of luck (or maybe just get lucky and not get in any trouble).
If you're into this sort of thing you should definitely check out the LocalWiki effort: http://localwiki.org We're a non-profit, decentralized project to collect and share the world's local knowledge.
It's like this:
--> GET /api/ Accept: application/json
<-- Content-type: application/vnd.api.v1+json <stuff>
Then your consumers can know what version of the API they're interacting with and act accordingly.
This would not threaten Wikipedia's tax-exempt status.
The DavisWiki is running our old software, not LocalWiki. We'll transition it over soon. The Denton site is a good example of what LocalWiki looks like: https://dentonwiki.org
We're using OSM base data for the map tiles (rendered via cloudmade). We'll likely do our own map tile rendering soon, probably running an open tile server for any localwiki install to point at. Not sure about further OSM integration - got any ideas?
So making the most -absurdly- usable software possible was a huge priority. If you look around, there's really no easy to use open-source wiki software, so we had to do a -lot- of gruntwork. We wanted to, at the very least, remove the technically-savvy barrier.
And the standard for online collaboration hsa also risen quite a bit, but open-source wiki software hasn't kept up. Back when DavisWiki started, the very -idea- of web based collaboration was foreign. Nowdays, my mom uses Google Docs!
"I often have to manage images/css/js manually, figure out where to put them, etc"
This has (yay!) been solved in 1.3 with the inclusion of the staticfiles app. I now just put my app-specific static stuff in static/ and then run manage.py collectstatic and all is well in the world :)
Maybe they should make more public-facing updates about individual features and changes in their software, but (as is hinted to in their post) it seems like they are limited in their resources.
The Diaspora guys have the really-actually-unique challenge of developing an open-source project entirely in the open coupled with attention and radically differing expectations from thousands of people. It's kind of nuts, really. Would you want to be in their position?
Maybe they won't amount to much, but criticising them because they didn't respond to your email is not fair.