GNU MediaGoblin – A decentralized alternative to Flickr, YouTube, SoundCloud
mediagoblin.org
mediagoblin.org
PS: ..I am not part of the team.
Edit: See also the talk at Pycon US. http://pyvideo.org/video/725/40-media-goblin-the-road-to-fed...
Edit2: Everyone may run their own instances and The 'federation' idea suggests to me that independent instances will be able to enable social interactions. http://pyvideo.org/video/725/40-mediagoblin-the-road-to-fede.... See also this checklist. http://mediagoblin.org/news/mediagoblin-1.0-checklist.html
See also the video from the campaign page, which describes things better than the actual site: http://mediagoblin.org/pages/campaign.html
Unfortunately the site is in bad need of updating; there's so much going on in the codebase right now that it's been hard to prioritize. Luckily we now have an intern who is going to be taking on that work!
And yes, independent instances will be able to talk to each other soon. We have an Outreach Program for Women participant actively working on federation via the Pump API! https://github.com/e14n/pump.io/blob/master/API.md
That's not all that's going on alone, but you can get some sense of what else is happening by checking out: http://mediagoblin.org/news/summer-of-awesome.html
I agree, the frontpage of mediagoblin.org can use some improvement. We're working on that. If you want a fast summary of things, you can still watch the video from the crowdfunding campaign we ran last year with the FSF (hell, you can still donate too!). http://mediagoblin.org/pages/campaign.html
We also have an intern helping us clean up the homepage. Things should be getting clearer soon, I think. I agree that http://mediagoblin.org/ could use some improvement.
In the meanwhile, if you're wondering what it offers, right now it already supports nice photo, video, audio, document (pdf.js!), and even 3d model support. It's written in Python, so it's easy to get hacking on. We have a lot more exciting things on the way too, most noticably federation; we currently have someone working full time on adding federation via the Pump API: https://github.com/e14n/pump.io/blob/master/API.md
This will make it so that even though there's a bunch of separate MediaGoblin instances out there that you should be able to have a lot more of the same social features of other media hosting sites as if they're in the same place.
I'm happy to answer questions if anyone has any!
Anyway, once all our summer projects wrap up, I think we'll have reached 1.0-worthiness, however there's a lot of code being developed right now, and I can't promise how long it'll take for it to hit the "quality approval for merge" state.
We've had theming for a while, since 0.3.1! http://mediagoblin.org/news/mediagoblin-0.3.1-a-whole-new-lo...
Read the documentation for details on that, but you can already enable a light "airy" theme if you prefer.
PS: If you're a python developer and interested in federation, you may be interested in checking out our super-awesome-contributor Jessica Tallon's "PyPump" library, which integrates with the Pump API: https://github.com/xray7224/PyPump
I know she wants more users and feedback! Pump API integration is on the way, but in the meanwhile, there's a project that's already using it if you want to try out the API: http://pump.io/
Thanks for the excellent questions! Hope that rambly response was helpful :)
Will it support easy mirroring of media? Will the site be also metaservers (servers that provide the addresses of other servers), or proxy servers (they serve the content of other servers they know of)? What about the bandwidth issues (often bandwidth is asymmetric between upstream/downstream)? Maybe some form of load balancing by redirection to another server. But one would need URI scheme across all the sites... Oh my.
Also: one-click-install for Windows/Mac when?
Re: mirroring, I replied to that a bit here: https://news.ycombinator.com/item?id=6180159
Additionally, you can already host media files with an OpenStack Swift cloud files provider like Rackspace Cloud if you prefer.
I don't know anything about windows or macs personally, though people have gotten mediagoblin working just fine on macs... windows is harder. :) I don't have any clue when that packaging might happen though... if it happens, it'll be by someone else I guess; I just don't know anything about it.
And in any case, it's not just a "oh, we tossed an intern at this"; in this case, the person who's working on this is a community member and intern, and is doing work based on a detailed analysis based on another community member's work overviewing all our current messaging: http://lists.mediagoblin.org/pipermail/devel/2013-July/00061...
So it's not just a matter of, "oh get an intern and toss them at it"!
But hey, if you're bothered by the fact that we're a community project with not a lot of full time resources, you can donate and help us pay for more people to come on as dedicated resources! The crowdfunding campaign we ran through the FSF last year is over, but the donation link still works: http://mediagoblin.org/pages/campaign.html
Or, feel free to help us out yourself! http://mediagoblin.org/pages/join.html
Decentralized would be like GNUNet[1].
Decentralized can have various definitions; GNUNet is definitely one definition, but you might consider that the web itself is supposed to be decentralized and is designed to be able to be that way, but is moving away from that as more and more of the web is being replaced by megasites like YouTube, Flickr, Tumblr. So, MediaGoblin is one attempt to take back the web in that respect.
As for how federation will work, we may enable a plugin called "diskgobbler" or something that might dowload files, but no, by default, MediaGoblin will not mirror all files from the other sites it is federating with. :) Instead, the goal is to keep the social side of things alive: you can create galleries that have entries that span multiple sites, favoriting a piece of media can happen across instances, you can subscribe to things a-la YouTube channels. That's what we mean as in terms of what we aim for by federation.
Hope that answered a bit!
I just think that it's unfair to call it decentralized if each instance of it is out there on its own.
Perhaps once federation is working it'd be a more fair comparison, because at least then all the servers can communicate and share with each other.
Don't take this as an attack on your software. It looks nice and I'm sure it works well (I haven't had a chance to use it).
http://networkcultures.org/wpmu/unlikeus/resources/articles/...
Curiously we've gotten a number of concerns about maybe the branding will push people away by thinking that the goblins are evil or scary or will frighten children, but we've never actually had anyone tell us that it actually invoked that reaction in them, just that they're concerned about it. And a lot of people seem to really like the goblins.
We do have a light theme called "airy"; there's some debate about whether that theme should be default. The choice of a dark theme isn't to invoke something dungeon'y, it's to put spotlight on the media, making the media the "light" of the scene. But anyway, maybe at some point we will switch over to airy by default... we'll see what the future brings.
Thanks for your comment!
Glad to hear about theming. Flickr/500px/other sites chose to let users opt-in to black backgrounds, I think that is a nice approach - some media is better highlighted by a dark background, but not all. All the best to your project.
Also I beg of you to fix the color temp on that cupcake photo. People who are interested in sharing media will notice.
I realize that the FreeBSD mascot is a devil, but FreeBSD is a far less consumer-facing product than MediaGoblin aims to be. Moreover, the FreeBSD team has struggled with questions about the appropriateness of such a mascot for corporate and marketing purposes [2].
1. https://en.wikipedia.org/wiki/Goblin
2. https://en.wikipedia.org/wiki/BSD_Daemon#Use_in_operating_sy...
I actually attempted to get it going on my VPS just a few days ago but got stuck on celery, missing some config (dont have the msg left) but might attempt it in the future again.
I like the dark design at least, I never understood who came up with white and bright pages to watch on a computer monitor, its not a book.
If it isn't clear already, the warning/error message re: celery when you run `gmg *` is just a bug in current git master.
Serious questions. I love the project.
Will MediaGoblin stick with its own direction, or move over to using Django or become a Flask app? It kind of depends... at the moment, things seem to be running well, and aside for waiting for some of our libraries to catch up to Python 3, we don't seem very hampered by it, and we're also very nimble... changing core parts of MediaGoblin to fit our needs is presently very easy. It also might be interesting to see what happens if eventually we end up adopting some XUDD technologies: https://xudd.readthedocs.org/en/latest/ but admittedly that's a ways out (though MediaGoblin already can run on XUDD, as of yesterday ;)) if that will happen at all.
Sorry, kind of a rambly response! Hope it was interesting.
Also stop with the saying it's rambly please.
Seriously, what an amatuerish-looking mess. White text on black, no clear navigation path, I can't imagine any random end user actually using one of these sites.
How many people want to be the SysAdmin for all 2.0 services for their entire extended family? We need self-organizing systems, not federation.
It's possible to make installing this stuff easier.
As a designer there is only that much you can do if you don't get support, or get conflicting views from the client (= all the contributors in the project).
I'm not the creator, but perhaps you could offer 1 (or 2!) actionable critiques? For example, you mentioned the navigation path. Where did you get stuck?
You could say the same thing about MS-DOS, but if it gets the job done it will get used. The most important thing is functionality, not UI. After all, you can't polish a turd.
And maybe that's why nobody uses it anymore.
If you want to compare, compare to something current. MS DOS was not that amateurish looking for its age and its user base at the time.
(nobody as in "mostly outliers", for you pedants)
You've bitten off more than you can chew by going against Flickr/Youtube/Soundcloud. You don't really offer anything they don't, just a promise of ethics like "it's free".
Deleted comment
#2: GNU only have recommendations for GNU projects regarding licensing (posted at http://www.gnu.org/licenses/license-recommendations.html). In it, AGPL is the license of choice for software that interacts with its users over a network, but it is only a recommendation. Project leaders and project communities are the ones who decide.
#3: News articles rarely mention license in the title, except when the linked website is titled as such. Do we really need to title every software article by its license?
Deleted comment
Linus announcing his kernel was in a time when there were no open Unix-like operating systems to use. The GNU kernel was years away from release, but all the tools were there to make an operating system out of the tools, if there were just a free kernel too. (The only other kernels available were not available to the general public for free) It took years for a somewhat usable component to appear to look like a product once packaged correctly.
There exist open alternatives to galleries and video players, which is what this effectively is. That's not to say that in years this couldn't be a usable alternative to YouTube, but it's currently not being developed as a product. Instead it's apparently a high school class project. If they want people to use this, it needs some kind of vision other than yet-another-open-source-clone-we-don't-need-itis.
Rather, the projects scope is to create a federated gallery and video player, where each installed instance is connected with each other.
That has so far not been reached yet, which is why this software hasn't reached their 1.0 goal yet.
It's also curious if this was the whole point of the project, why wasn't that done first?
Improved Privacy. Only the author will have information regarding who visit, how many times, and for how long is-
Future proofing. Youtube and flickr will only exist as long those services are profitable. People who thinks they own their media, can only hope that it will stay online for as long as possible.
Improved API/features. Media hosting companies will limit features to match their business model. With federated services, there is no such limit.
Secure API. Media hosting companies will remove features if competitors are using the API in a threatening style. with federated services, there is no central company that can feel threatened.
> why wasn't that done first?
Just being federal, but with no meaningful usages, it would not be useful. I don't know if there is a technical reason why it couldn't be done at the same time.