Switch order of html/text for StatusNet backwards compatibility
Switch order of html/text for StatusNet backwards compatibility

StatusNet chooses the first content element in an Atom feed, while
it should really choose the 'html' representation for its 'rendered'
and 'text' representation for the (text-only) 'content'.

GNU social will implement a better algorithm for retrieving Atom
feeds, but that is yet to be done. So to avoid having link-less posts
on remote nodes, we'll just do the old switch-a-roo.

Other Atom readers, such as Mozilla Firefox, has the reverse priority
(choosing the last of the content elements).

Piratas/tortuga,Piratas/tortuga,bankonme/gnu-social,charlycoste/StatusNet,sikevux/bsk-social,gnusocial/mainline,foocorp/gnu-social,eXcomm/gnu-social,bankonme/gnu-social,furtherfield/gnu-social,faulteh/gnu-social,sikevux/bsk-social,studio666/gnu-social,sikevux/bsk-social,faulteh/gnu-social,gnusocial/mainline,charnimda/lgbtpzn-social,faulteh/gnu-social,Piratas/tortuga,gnusocial/mainline,charnimda/lgbtpzn-social,furtherfield/gnu-social,studio666/gnu-social,furtherfield/gnu-social,chimo/social,bankonme/gnu-social,Piratas/tortuga,foocorp/gnu-social,eXcomm/gnu-social,gnusocial/mainline,bankonme/gnu-social,studio666/gnu-social,charnimda/lgbtpzn-social,furtherfield/gnu-social,sikevux/bsk-social,foocorp/gnu-social,charlycoste/StatusNet,faulteh/gnu-social,chimo/social,charlycoste/StatusNet,chimo/social,eXcomm/gnu-social,studio666/gnu-social,eXcomm/gnu-social