Age | Commit message (Collapse) | Author |
|
Pleroma 1.0.7
See merge request pleroma/pleroma!1723
|
|
|
|
|
|
|
|
|
|
|
|
|
|
follow View/Controller pattern
Note that I mentioned the change in 1.1 section because I intend to
backport this, if this is not needed I will move it back to Unreleased.
|
|
|
|
Closes: https://git.pleroma.social/pleroma/pleroma/issues/1267
|
|
mix: bump version to 1.0.6
See merge request pleroma/pleroma!1571
|
|
|
|
1.0.6 release
See merge request pleroma/pleroma!1570
|
|
|
|
|
|
|
|
tzdata 1.0.0 requires Elixir 1.8.0, but we target 1.7. Fortunately
tzdata issues bugfix releases for pre-1.8.0 version.
|
|
1.0.5 release
See merge request pleroma/pleroma!1549
|
|
|
|
|
|
|
|
memory leaks on recursive replies fetching.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
describe()
|
|
|
|
|
|
Anyone who is interested in dropping blocks can write their own MRF
policy at this point. This setting predated the MRF framework.
Disabling the side effect (unsubscription) is still a config option
per policy.
|
|
|
|
`name` key and use a depth limit when fetching it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
because the objects are no longer supposed to be embedded
|
|
in the Create activity
|