Add check_upstream_directory() to check that your directory is still
a directory, and if it isn't, let find_upstream_directory() find you
a new one.
use feed icon as default avatar for rss connections
Merge https://github.com/friendica/red into pending_merge
Merge remote-tracking branch 'upstream/master'
If you have a new channel (or a new hub searching for an old channel)
which uses an xchan_url other than channel or profile, chanview will
fail to find $a->poi and fail as there is no way to import the xchan.

Instead of giving up and presenting an error, we'll send you to the
requested URL anyway.  If we send you with a Zid, there's a good
chance you'll authenticate because xchans are like glitter - once you've
got one, they get everywhere, and there's a good chance you'll know
*somebody* at the hub.
.
Move achievements on, but just a tad.
Don't forget the ifs.  Now we just need to write some blurb, find some
images, add a link, and decide what to do with non-earned badges...basically
all of it.
Merge pull request #576 from beardy-unixer/master

Allow directories to stop being directories without killing anyone.
issue #578 - this won't fix old items but should work going forward. The extra time slop shouldn't be needed and will in fact result in possibly undesired redundancy.
logic inverted
pull in some posts when first connecting to feeds
fix phantom attachments in feeds
minor nits
updated compatibility notes
use feed title for channel name before checking author, make feed items shareable (they're private to the channel so they won't be shown in searches), try and handle Diaspora mentions a bit more elegantly. (Bug: we don't convert mentions to Diaspora's format on outbound at all!)
feed removal issue
provide a config option to prevent wall uploads (photos and files) from being set to the same ACL as the containing post, and instead are uploaded with public visibility (no ACL). This is to prevent folks on other networks from seeing prohibited signs for things uploaded into a private conversation. It is primarily useful when posting to collections that have mixed folks from red and other networks and an otherwise public (typical) profile. Consequently, these uploads will match your chosen default visibility for photos and storage and not that of the containing conversation item (and is only useful if the default visibility is public). This choice must be explained adequately because it represents a complex series of tradeoffs and side effects. It will reduce complaints from other networks about blocked content, but essentially forces you to use another method (dav or the photos page) if you wish to upload protected files/media.
try to proceed with a diaspora relayable even if we don't have the original author's signature.
if we don't have a stored diaspora author signature which has been passed the baton since the post's creation, fill in the field with their redmatrix signature. It's pointless, but there's so much pointless stuff in here that I doubt it matters. From what I can ascertain - nobody is going to look at it anyway.
fix diaspora_handle_from_contact()