Just working on issue 302 (Delete your own account), noticing that deleting a MediaEntry and all related Comments / Files / Tags / Collections has to be done manually e.g. in user_pages/views.py:media_confirm_delete().

It would make sense to provide a "delete()" function for MediaEntry that did all this work centrally. It would simplify the view functions and put the internal implementation details into the db models where they belong. It would also enable me to easily delete all user's media from the delete_user_account function without having to manually duplicate the thing.

# We have to pass in an "urlgen" object to MediaEntry().url_for_self() to actually get the url. Being attached to the request, this means we have to carry around the request object all over the place rather than having that encapsulated nicely. Compare to django's "get_absolute_url()" which does not need such complexities. (I also think we should implement a get_absolute_url template in the Base model class, to enforce uniformity by the way).

# in contrast to werkzeug tools, this always returns relative URLs, so the URL generation in the atom feed that requires absolute urls looks for example:

werkzeug.urls.Href(self.request.host_url (
    media_entry.url_for_self(self.request.urlgen)))

when what I want is:

media_entry.url_for_self(external=True)

(or even better a more consistent media_entry.get_absolute_url()) It should be possible to enforce absolute external urls easily without having to manually parse and fudge the request in every caller.

# Nitpick: MediaEntry.url_for_next and url_for_prev are defined in models.py, while url_for_self is defined in mixin.py. This should be made consistent.

Things would be easier if the url generation did not depend on the request-specific MapAdapter (request.urlgen), which it currently does. Not sure, how this could be improved.

To sum up:

• At the very least, this bug should be about adding an external=True parameter that will return absolute, external URLs.
• The url generation should be defined in the same places (mixin or models)
• Optionally, we would implement a "get_absolute_url" in the Base model that all subclasses can override, so we can use the same consistent interface for all.This could be the same as "url_for_self" here for now.
• Ideally, we don't have to pass in the request into the url_for_self function so we don't always have to carry that around and to simplify things. However, I don't see an easy way to fix that, so this could be a step 2 of this ticket.

When we submit new media we send out the notification to the PubHubSubbub (PuSH) hub as soon as we uploaded it, which will try to fetch and distribute updated atom feeds. The problem is that with asynchronous processing, there might be no processed media yet and the feed will not yet have changed.

We therefore need a) a hook when media processing has finished b) somehow make use of the hook to actually push out notification of updated feeds to the PuSh hub.