Nginx is currently not caching data because proxy_buffering needs to be
enabled for caching to work at all, and we are receiving a Cache-Control
header from Pleroma that states "max-age=0, private, must-revalidate"

Even disregarding the Cache-Control header that should actually be set
to "public, max-age=1209600" as defined in the reverse_proxy code, we
don't want to obey this header at all as it overrides our Nginx caching
rules.

Add Twitter Card parser

See merge request pleroma/pleroma!643

Twapi follower pagination

See merge request pleroma/pleroma!648

common api: fix newlines in markdown code blocks

See merge request pleroma/pleroma!651

ok @lanodan

Pinned Statuses

Closes #440

See merge request pleroma/pleroma!636

Mass follow

See merge request pleroma/pleroma!642

Add activity visibility index.

See merge request pleroma/pleroma!646

Alpha sort the restricted nicknames

See merge request pleroma/pleroma!650

Rich media: Remove :commit since a tuple is already returned

See merge request pleroma/pleroma!649

Scarlett/pleroma summary html api

See merge request pleroma/pleroma!647

```
# Only return statuses that have been pinned
GET /api/statuses/user_timeline.json?pinned=true

# Pin
POST /api/statuses/pin/:id

# Unpin
POST /api/statuses/unpin/:id
```

# Conflicts:
#	docs/config.md

user: fix local vs remote determination in remote_or_auth_active?/1

See merge request pleroma/pleroma!640

any actual callee will be dealing with a User struct to begin with, so
just check the child struct inside User.superuser?/1 with pattern matching.

auth_active?/1 can check remote users and return true directly.

user: use pattern matching to determine if user is local or remote instead of the previous hairy logic

Add a setting for users to autofollow on sign up.

See merge request pleroma/pleroma!639