Post 2243918 by VyrCossont@princess.industries
(DIR) More posts by VyrCossont@princess.industries
(DIR) Post #2243918 by VyrCossont@princess.industries
2018-12-24T03:14:08.611557Z
0 likes, 0 repeats
here is a fun #Pleroma fact: it does not have server-side mutes https://git.pleroma.social/pleroma/pleroma/issues/211
(DIR) Post #2243919 by lain@pleroma.soykaf.com
2018-12-24T12:10:37.977584Z
0 likes, 0 repeats
@VyrCossont it does, it's just that the mutes in the pleroma frontend aren't the same as in the Mastodon frontend. if you use a mastodon client or the Mastodon frontend with pleroma, it will work like someone coming from mastodon would expect.
(DIR) Post #2250035 by VyrCossont@princess.industries
2018-12-24T16:19:48.748872Z
0 likes, 0 repeats
@lain no, i got that bit, i get that Pleroma-FE mutes are distinct, but i'm using Mastodon clients like Mast, Amaroq, and Pleroma's bundled Mastodon frontend, and the mutes silently fail to persist.this comment from Eal on the issue suggested that they're not implemented:> In mastodon-api mutes are unimplemented as of now. (Just writing this down so anyone doesn't spend any more time testing it)and pleroma/web/router.ex shows that mute APIs are in fact stubbed out.
(DIR) Post #2250036 by lain@pleroma.soykaf.com
2018-12-24T16:22:59.666861Z
0 likes, 0 repeats
@VyrCossont ??? i thought we implemented them? thanks for the reminder, i'll check!
(DIR) Post #2250371 by VyrCossont@princess.industries
2018-12-24T16:34:32.642134Z
1 likes, 0 repeats
@lain https://git.pleroma.social/pleroma/pleroma/issues/211 is definitely still open, and i'm using a develop branch build from yesterday. i'm still learning Elixir and the Pleroma codebase or i'd have a go myself.there are also open bugs for Pleroma-FE related to harmonizing Mastodon server-side mutes with the existing Pleroma-FE client-side mutes, which i am all for:https://git.pleroma.social/pleroma/pleroma-fe/issues/226https://git.pleroma.social/pleroma/pleroma-fe/issues/227