GNU MediaGoblin Wiki - User contributions [en]

Main Page

2014-10-16T19:23:06Z

Saul: Undo revision 1596 by VenusHongmw (talk)

= Want to Join the MediaGoblin Community? =

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

We observe the [https://www.djangoproject.com/conduct/ Django code of conduct]. Be welcoming, friendly, and patient!

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

== Hang out with the MediaGoblin folk ==

MediaGoblin has a mailing list and an IRC channel where we hang out. See [http://mediagoblin.org/pages/join.html our join page] for links.

Please drop by and say “Hi!” And, if you’re looking for something to do, just ask---there’s always work to be done.

== Take Part in the Monthly Meetings ==

Each month is a [[:Meeting|Meeting]]. You can take part and help decide on the future of MediaGoblin. Or just be around and see what's happening live!

=How Can you help ?=

First and foremost, for many (but not all) types of contributions you may want to set up a local instance. To learn how to do this, see the [[HackingHowto]] page. (If you're not familiar with command line level things, there are still ways you can help below!)

== File Bugs / Triage Bugs ==

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

* [[File Bugs]] -- notes on filing new bugs/issues/feature requests
* [[Feature Ideas]] -- notes on possible features
* [[Triage Bugs]] -- notes on triaging
* [[BugTriageDay]] -- every other Thursday is bug triage day where anyone can help out triaging bugs

== Send Encouragement / Spread the Word ==

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See [http://mediagoblin.org/join/ our join page] for links.

== Write Documentation / Edit Documentation ==

* [[Documentation quick start]] - How to contribute to the documentation effort.
* [[ManualStandards]] - covers the standards for writing the user manual (forthcoming.)

== Test MediaGoblin ==

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?

* [[User Experience]] - user experience testing. Includes link to an instance you can try!
* [[UnitTests|Unit Tests]] - all about the unit tests
* [[Manual_Functional_Testing|Manual Functional Testing]] - a great way to get to know MediaGoblin.

== Translate MediaGoblin ==

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources.
Translating MediaGoblin is very easy with a web interface, so there is no programming knowledge required at all.

* [[Translations]] - How to translate stuff or update the translations

== Become a User ==

Coming soon!

We’re building MediaGoblin for us and for you but really you’re one of us and I am you and we are we and MediaGoblin is the walrus.

We're planning to launch our own public instance of MediaGoblin in the near future--probably in the September/October 2011 time frame. When we do, sign up for an account, use the service and relish in the thought that this service comes with a heaping side of Freedom and you can salt and pepper it to your liking.

== Help Others ==

Have you spent time with MediaGoblin? If so, your experience and wisdom are invaluable and you’re the best person we can think of to help other users with their questions.

Hang out on the IRC channel and help answer new peoples' questions. See [http://mediagoblin.org/join/ our join page] for links.

== Run your own MediaGoblin Instance ==

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

The primary documentation for this is at [http://docs.mediagoblin.org http://docs.mediagoblin.org] but here are some additional tips:

* [[Configure_MediaGoblin|Configuration]] - Learn about MediaGoblin configuration files and file options.
* [[Deployment]] - General deployment advice
* [[Scaling Down]] - Minimizing MediaGoblin's resource requirements
* [[Virtual Machine Hosting]] - Deploy your own publicly available MediaGoblin server using [http://aws.amazon.com/free/?utm_source=adwords&utm_medium=cpc&utm_campaign=CPC_Google_AWS_ec2&utm_content=TextV01_PP_V01_EC2&trk=CPC_Google_AWS_ec2 Amazon's free EC2 tier].

= Technical project documentation =

The technical docs, that are more finished and the ones that are better maintained near the code (so they stay up to date) are in the more technical chapters of the [http://docs.mediagoblin.org/ main documentation].
* [[Storage]] - How MediaGoblin's internal storage system works.
* [[Processing]] - What happens after you submit your image/video/etc? Processing! More about that.
* [https://gitorious.org/mediagoblin/mediagoblin/blobs/master/extlib/README External Library Policy] - covers use of external libraries
* [[User:Cwebber/braindumps]] - Chris Webber's braindumps (you can help refactoring these into real sections of the site!)
* [[Multiple media support]] - Design plan for multiple media support

== Write Code / Fix Code ==

MedaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

* [[HackingHowto|Hacking]] - notes on making and sending in code contributions
** [[BeginnersCorner|Beginner's Corner]] - resources for those who are new to Python or Git.
** ''Started from an older version of the Hacking Howto? We switched from buildout->virtualenv, so look at [[Moving from buildout to virtualenv]] for information on how to move over.''
* [[Git workflow]] - How to go about submitting patches via git.
* [[Code review tips]] - Tips on how to go about doing local code review
* [[Templating]] - How our templating structure is set up
* [[Code overview]] - Overview of the structure of the codebase

== Create a Theme ==

See [http://docs.mediagoblin.org/siteadmin/theming.html the theming docs]

== Write a plugin ==

If you start, you'll find some basic documentation [http://docs.mediagoblin.org/#part-4-developer-s-zone| in the docs site]

You've made a plugin ? List it here :

[[Available_Plugins|Available plugins]]

You've written a plugin ? You got some tips to share ? A tutorial idea ? Please do :

[[PluginsTips|Plugins Tips]]

= Misc =

== Android client ==

See [[Android Client]]

= Inner workings of the secret sanctum =

* [[IRCBot]] - covers our irc bot
* [[ReleaseProcess|Release Process]] - covers the release process
* [[Update the website]] - Learn how to update mediagoblin.org!

=FAQ=

[[GMG FAQ]]

Configure MediaGoblin

2014-01-16T22:55:04Z

Saul: /* Disable transcoding */

= The config files =

So basically there are two config files (and one meta-config file).

* '''mediagoblin.ini:''' Use this to configure MediaGoblin, the application. Want to use a different storage system? Configure it here!
* '''paste.ini:''' This just actually configures the web server that launches the MediaGoblin application, and some other things (like actually sets up the applications that serve your static files).

And then there's the meta-config file:
* '''mediagoblin/config_spec.ini:''' This sets the defaults for config file options and the type conversion for things in mediagoblin.ini. Developers who add new config options should probably register them and their types here (and set some good defaults, if applicable).

= Changing config files =

So you want to turn on (or off) all the bells and whistles, set up mediagoblin to use a storage system running out of a distributed cluster of Commodore 64s, change your email server configuration, etc. Where do you set all this stuff up?

You should do the following:
<pre>
# copy the config files
$ cp paste.ini paste_local.ini
$ cp mediagoblin.ini mediagoblin_local.ini

# edit paste_local.ini to know where mediagoblin_local.ini is
$ editor paste_local.ini
</pre>

Find the line marked "config =" under [app:mediagoblin]; change to:

<pre>
[app:mediagoblin]
use = egg:mediagoblin#app
filter-with = beaker
config = %(here)s/mediagoblin_local.ini
</pre>

If you want to use lazyserver.sh, you can run it like:

<pre>
./lazyserver.sh -c paste_local.ini
</pre>

Also, all the ./bin/gmg commands have arguments to allow you to pass in the config file. For example:

<pre>
./bin/gmg shell -cf mediagoblin_local.ini
</pre>

(It's important to note that the ./bin/gmg commands don't care about the paster file, they just care about the mediagoblin config file.)

BTW, all these ./bin/gmg subcommands have help. You can check them like:

<pre>
./bin/gmg shell --help
</pre>

for more info.

= Setting up Cloud Files public storage =

In mediagoblin.ini (or mediagoblin_local.ini), add this to the file and edit it to fit your needs.

<pre>
[storage:publicstore]
storage_class = mediagoblin.storage.cloudfiles:CloudFilesStorage
cloudfiles_user = user
cloudfiles_api_key = 1a2b3c4d5e6f7g8h9i
cloudfiles_container = mediagoblin

# Uncomment this and fill it in to set the API endpoint to anything other
# than Rackspace Cloud Files US
# cloudfiles_host = https://example.org/v1.0

# Only applicable if you run MediaGoblin on a Rackspace Cloud Server
# it routes traffic through the internal Rackspace network, this
# means that the bandwith is free.
cloudfiles_use_servicenet = false
</pre>

To make these settings work with OpenStack Object Storage (Swift) you will need to set the API endpoint (<code>cloudfiles_host</code>) to avoid it defaulting to Rackspace Cloud Files US.

= Attachments =

Attachment are arbitrary files that are associated to a media entry.

For example, it could be the GIMP .xcf file for an image, the .blend of a Blender render.

== Hazards ==

Attachments are not filtered or scanned and therefore present a security risk. They can be used to perform XSS attacks or to upload malicious content. Make sure your environment is safe before enabling it.

== Allow attachments ==

To allow attachments, add

allow_attachments = true

to your mediagoblin.ini (or mediagoblin_local.ini)

= Disable transcoding =

Transcoding means that your video is resized or converted to another format, which usually takes a lot of time and CPU power.

Currently transcoding is disabled for a video only if its mime-type, container, video and audio formats are all explicitly excluded at once in the configuration.

Add this section to your <code>mediagoblin.ini</code> to disable transcoding of WebM and Ogg/Theora videos:

<pre>
[media_type:mediagoblin.media_types.video]
[[skip_transcode]]
mime_types = video/webm, video/ogg, application/ogg, application/x-annodex
container_formats = Matroska, Ogg
video_codecs = VP8 video, Theora
audio_codecs = Vorbis,
dimensions_match = false
</pre>

Storage

2013-09-07T09:17:29Z

Saul: /* Writing code to store stuff */ - fixed link formatting

Being a media publishing platform, storage is a big deal in MediaGoblin. As such there are a few systems that are storage-related that you may encounter while doing some MediaGoblin hacking.

MediaGoblin also comes with an extensible storage interface and several implementations mapping to it: basic local file storage, OpenStack "swift" style storage... and a few more plus the ability to write your own.

= The storage systems attached to your app =

== Dynamic content: queue_store and public_store ==

Two instances of the StorageInterface come attached to your app. These are:

* '''queue_store:''' When a user submits a fresh piece of media for their gallery, before the [[Processing]] stage, that piece of media sits here in the queue_store. (It's possible that we'll rename this to "private_store" and start storing more non-publicly-stored stuff in the future...). This is a StorageInterface implementation instance. Visitors to your site probably cannot see it... it isn't designed to be seen, anyway.
* '''public_store:''' After your media goes through processing it gets moved to the public store. This is also a StorageInterface implelementation, and is for stuff that's intended to be seen by site visitors.

== The workbench ==

In addition, there's a "workbench" used during processing... it's just for temporary files during processing, and also for making local copies of stuff that might be on remote storage interfaces while transitionally moving/converting from the queue_store to the public store. See the workbench module documentation for more.

== Static assets / staticdirect ==

On top of all that, there is some static media that comes bundled with your application. This stuff is kept in:

mediagoblin/static/

These files are for mediagoblin base assets. Things like the CSS files, logos, etc. You can mount these at whatever location is appropriate to you (see the direct_remote_path option in the config file) so if your users are keeping their static assets at http://static.mgoblin.example.org/ but their actual site is at http://mgoblin.example.org/, you need to be able to get your static files in a where-it's-mounted agnostic way. There's a "staticdirector" attached to the request object. It's pretty easy to use; just look at this bit taken from the mediagoblin/templates/mediagoblin/base.html main template:

<link rel="stylesheet" type="text/css"
href="{{ request.staticdirect('/css/extlib/text.css') }}"/>

see? Not too hard. As expected, if you configured direct_remote_path to be http://static.mgoblin.example.org/ you'll get back http://static.mgoblin.example.org/css/extlib/text.css just as you'd probably expect.

= StorageInterface and implementations =

== The guts of StorageInterface and friends ==

So, the StorageInterface!

So, the public and queue stores both use StorageInterface implementations... but what does that mean? It's not too hard.

Open up: mediagoblin/storage.py

In here you'll see a couple of things. First of all, there's the StorageInterface class. What you'll see is that this is just a very simple python class. A few of the methods actually implement things, but for the most part, they don't. What really matters about this class is the ''docstrings''. Each expected method is documented as to how it should be constructed. Want to make a new StorageInterface? Simply subclass it. Want to know how to use the methods of your storage system? Read these docs, they span all implementations.

There are a couple of implementations of these classes bundled in storage.py as well. The most simple of these is BasicFileStorage, which is also the default storage system used. As expected, this stores files locally on your machine.

There's also a CloudFileStorage system. This provides a mapping to [OpenStack's swift http://swift.openstack.org/] storage system (used by RackSpace Cloud files and etc).

Between these two examples you should be able to get a pretty good idea of how to write your own storage systems, for storing data across your beowulf cluster of radioactive monkey brains, whatever.

== Writing code to store stuff ==

So what does coding for StorageInterface implementations actually look like? It's pretty simple, really. For one thing, the design is fairly inspired by [https://docs.djangoproject.com/en/dev/ref/files/storage/ Django's file storage API]... with some differences.

Basically, you access files on "file paths", which aren't exactly like unix file paths, but are close. If you wanted to store a file on a path like dir1/dir2/filename.jpg you'd actually write that file path like:

['dir1', 'dir2', 'filename.jpg']

This way we can be *sure* that each component is actually a component of the path that's expected... we do some filename cleaning on each component.

Your StorageInterface should pass in and out "file like objects". In other words, they should provide .read() and .write() at minimum, and probably also .seek() and .close().

Feature Ideas

2013-03-13T08:02:35Z

Saul: /* Media Types */ eliminate server transcoding if not needed

== Introduction ==

There are many features that one can think of for MediaGoblin. Some should be implemented really soon, because they are needed right now. Other features would be nice to have, but are currently really hard to implement. And finally there are the Feature Ideas that can be classified as "brain storming".

This wiki page is mostly for long term feature ideas. This specifically means there are no promises that anything listed here will ever happen. It means nobody is currently working on this feature.

If you have an idea for a new feature, that is not listed here or in the Bug Tracker, please talk to some developers, or add it below in the "Yet Unsorted Ideas" section. If you really think, that your idea is extremely important and needs to be acted upon soon, you could file a bug.

== The List ==
If there is a bug (closed or open), please link to it.

=== Access Control ===
* Renaming of an account
** by its user
** by an admin
* Account creation / activation, considering e-mail address
** Expire inactive accounts
** A method of account activation: ask the user to send e-mail message with a specified text from the address they entered, instead of GMG sending a message to that address (which could be somebody else’s).
*** What about faked addresses? If that’s a serious problem for this, could it still be a requirement? Or is it so serious that it would bother malicious misusers least of all people? --[[User:Aleksejrs|Aleksejrs]] 15:17, 7 December 2011 (EST)
** The above allows accepting multiple inactive accounts for the same e-mail address without bothering its owner and without making it difficult for him to register.
*** But accounts could have the same name… --[[User:Aleksejrs|Aleksejrs]] 15:14, 7 December 2011 (EST)

=== Design (UI / HTML) ===
* Point and click theme options: Colors, layout, typefaces, size, thumbnail options, etc.
** Simple settable options to "personalize" the instance without fiddling with templates.
* Responsive base theme
* User Avatar

=== Extensions ===
* A link to the page about installed (and not installed?) plugins.

=== Federation ===
* [[User:Aleksejrs/ideas/federation|Two federation ideas]]

=== Import/Export ===
* [[Feature_Ideas/Flickr_Import|flickr Import]]
* MediaWiki export
* digiKam plugin (export to mediagoblin)
* Mount GMG as a file system (e.g. FUSE)

=== Licensing ===
* Help the site admin comply with the AGPL.
* Creative Commons choice on user profile. E.g. default license choice for media uploaded by that user.
* “Other (please specify: [ ])” license as an alternative to “All rights reserved”.

=== Media Processing ===
* [[Feature_Ideas/Reprocessing|Retry media processing]]
** Related: rotating images that have no proper Orientation tags.

=== Media Types ===
* For non-still-images:
** Duration
** Bitrate
** Format structure (e.g. “Ogg/Theora+Vorbis”)
** Permit pre-encoded uploads to eliminate server-side processing (available as of 0.3.3)
** Support Ogg/Theora player (already implemented?)
** Subtitles for video and audio
* A way to find out what formats can be uploaded.
** E.g.: A simple type list near the upload field.
* For images with transparency, let the uploader specify background (e.g. color or checkerboard).

=== Metadata ===
* Ability to write metadata (comments, tags, etc.) to files.
* Copy (some) metadata from the full‐size image into the smaller versions. If possible (according to metadata formats), add a note to them that they are not exactly the original.
** [http://issues.mediagoblin.org/ticket/94 #94]: exif data handling for users (about privacy)
** <del>[http://issues.mediagoblin.org/ticket/284 #284]: Support "Orientation" EXIF tag</del> (fixed)
** EXIF info?
* Display more info about the file on its page
** Resolution of the original
** File size of the original
** Resolution of the scaled-down version
* "trans-tagging": Adding tags to other peoples media [http://issues.mediagoblin.org/ticket/251 #251]
** [[Many images usecase#Crowd tagging/captioning/commenting]]
* Geotagging support.
** Both read and write.
** Display on OpenStreetMap.
* Consider [https://en.wikipedia.org/wiki/Semantic_Web Semantic Web]
** Microformats, RDFa, Microdata
** Consider the privacy implications when choosing what to mark up.
* Add hashes etc, something like magnet links, of the files. The information can then be used for downloading, searching, linking to.
** Maybe also optional for privacy.

=== Security ===
* DONE: CSRF ([http://issues.mediagoblin.org/ticket/76 #76])
* <code>X-Content-Type-Options: nosniff</code>
*: Served pages have the content-type set. And the browser should not be allowed to guess a different type. See: [https://bugzilla.mozilla.org/show_bug.cgi?id=471020 Firefox bug #471020]
* "Content Security Policy" (CSP) might really be a good add on to have. Noone should rely solely on this, but it might make things a lot safer if other security guards fail.
*: A simple allow 'self' might already get a lot of things better.
*: [https://developer.mozilla.org/en/Security/CSP/Introducing_Content_Security_Policy Link1] [https://developer.mozilla.org/en/Security/CSP/CSP_policy_directives#options Link2]
* Possibly disallowing pages to be shown in frames.

=== Unsorted Ideas ===
Put your new ideas here:
* Search.
* Related Content
* The user has the possibility to make backup of your content that can be migrated to another instance mediagoblin
* Generate pages dynamically using files on the file system.
** Like the UI of an ordinary image viewer (e.g. geeqie) or a file manager generates thumbnails (optionally saving them), shows metadata…
** MediaWiki can generate thumbnails of arbitrary size on demand.

Feature Ideas

2012-08-29T02:21:49Z

Saul: /* Media Types */

== Introduction ==

There are many features that one can think of for MediaGoblin. Some should be implemented really soon, because they are needed right now. Other features would be nice to have, but are currently really hard to implement. And finally there are the Feature Ideas that can be classified as "brain storming".

This wiki page is mostly for long term feature ideas. This specifically means there are no promises that anything listed here will ever happen. It means nobody is currently working on this feature.

If you have an idea for a new feature, that is not listed here or in the Bug Tracker, please talk to some developers, or add it below in the "Yet Unsorted Ideas" section. If you really think, that your idea is extremely important and needs to be acted upon soon, you could file a bug.

== The List ==
If there is a bug (closed or open), please link to it.

=== Access Control ===
* Renaming of an account
** by its user
** by an admin
* Account creation / activation, considering e-mail address
** Expire inactive accounts
** A method of account activation: ask the user to send e-mail message with a specified text from the address they entered, instead of GMG sending a message to that address (which could be somebody else’s).
*** What about faked addresses? If that’s a serious problem for this, could it still be a requirement? Or is it so serious that it would bother malicious misusers least of all people? --[[User:Aleksejrs|Aleksejrs]] 15:17, 7 December 2011 (EST)
** The above allows accepting multiple inactive accounts for the same e-mail address without bothering its owner and without making it difficult for him to register.
*** But accounts could have the same name… --[[User:Aleksejrs|Aleksejrs]] 15:14, 7 December 2011 (EST)

=== Design ===
* Point and click theme options: Colors, layout, typefaces, size, thumbnail options, etc.
** Simple settable options to "personalize" the instance without fiddling with templates.
** [http://bugs.foocorp.net/issues/613 #613]: Make the base of page titles customizable.
* Responsive base theme
* User Avatar

=== Extensions ===
* A link to the page about installed (and not installed?) plugins.

=== Federation ===
* [[User:Aleksejrs/ideas/federation|Two federation ideas]]

=== Import/Export ===
* [[Feature_Ideas/Flickr_Import|flickr Import]]
* MediaWiki export
* digiKam plugin (export to mediagoblin)

=== Licensing ===
* Help the site admin comply with the AGPL.
* Creative Commons choice on user profile. E.g. default license choice for media uploaded by that user.

=== Media Processing ===
* [[Feature_Ideas/Reprocessing|Retry media processing]]
** Related: rotating images that have no proper Orientation tags.

=== Media Types ===
* For non-still-images:
** Duration
** Bitrate
** Format structure (e.g. “Ogg/Theora+Vorbis”)
** Permit pre-encoded uploads to eliminate server-side processing
** Support OGG/Theora player
* A way to find out what formats can be uploaded.
** E.g.: A simple type list near the upload field.

=== Metadata ===
* Ability to write metadata (comments, tags, etc.) to files.
* Copy (some) metadata from the full‐size image into the smaller versions. If possible (according to metadata formats), add a note to them that they are not exactly the original.
** [http://issues.mediagoblin.org/ticket/94 #94]: exif data handling for users (about privacy)
** <del>[http://issues.mediagoblin.org/ticket/284 #284]: Support "Orientation" EXIF tag</del> (fixed)
** EXIF info?
* Display more info about the file on its page
** Resolution of the original
** File size of the original
** Resolution of the scaled-down version
* "trans-tagging": Adding tags to other peoples media [http://issues.mediagoblin.org/ticket/251 #251]
** [[Many images usecase#Crowd tagging/captioning/commenting]]
* Geotagging support.
** Both read and write.
** Display on OpenStreetMap.

=== Security ===
* DONE: CSRF ([http://bugs.foocorp.net/issues/361 #361])
* <code>X-Content-Type-Options: nosniff</code>
*: Served pages have the content-type set. And the browser should not be allowed to guess a different type. See: [https://bugzilla.mozilla.org/show_bug.cgi?id=471020 Firefox bug #471020]
* "Content Security Policy" (CSP) might really be a good add on to have. Noone should rely solely on this, but it might make things a lot safer if other security guards fail.
*: A simple allow 'self' might already get a lot of things better.
*: [https://developer.mozilla.org/en/Security/CSP/Introducing_Content_Security_Policy Link1] [https://developer.mozilla.org/en/Security/CSP/CSP_policy_directives#options Link2]
* Possibly disallowing pages to be shown in frames.

=== Unsorted Ideas ===
Put your new ideas here:
* Subtitles for video (and audio?).
* Search.
* Related Content
* The user has the possibility to make backup of your content that can be migrated to another instance mediagoblin