Posts by VyrCossont@princess.industries
(DIR) Post #2232885 by VyrCossont@princess.industries
2018-12-24T00:45:59.515005Z
0 likes, 0 repeats
just set up my own Pleroma at https://princess.industries/ as an alt for @VyrCossont at https://cybre.space/i've set up mutual links from each bio, but Pleroma doesn't do rel="me" so Mastodon won't show the relationship as automatically verified. you can check it yourself.
(DIR) Post #2233219 by VyrCossont@princess.industries
2018-12-24T01:17:15.591595Z
0 likes, 0 repeats
i think i biffed the nginx reverse-proxy config for #Pleroma despite following the example config very closely. if i look in the JS console, Pleroma-FE is hella mad about websockets: `Error during WebSocket handshake: Unexpected response code: 200`this doesn't seem to affect the Mastodon frontend, so it could also be a Pleroma-FE bug.fortunately i mostly use Amaroq and occasionally Mast and neither of them seem to care
(DIR) Post #2235798 by VyrCossont@princess.industries
2018-12-24T03:37:34.997282Z
0 likes, 0 repeats
i think my old old instance is down again, time for a clip show
(DIR) Post #2235826 by VyrCossont@princess.industries
2018-12-24T03:40:13.532198Z
0 likes, 0 repeats
@hierarchon oh were you on queer.af before cybre.space too? i can't remember
(DIR) Post #2238144 by VyrCossont@princess.industries
2018-12-24T04:38:14.718620Z
0 likes, 0 repeats
transhumanists: yeah i'd totally switch bodies to a robot chassis/get a new one cloned whenever i couldme, a trans humanist: are you fucking kidding me? i'm keeping this one! sure it's a little beat up but i already know how it steers and where most of the controls arein the future there are gonna be a load of idiots clonking around in bodies they don't know like they're drunk driving rental cars smdh[#VyrClipShow: i have only gotten more graceful and elegant since then. i'm like a god damn swan.]
(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 #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 #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
(DIR) Post #2262932 by VyrCossont@princess.industries
2018-12-24T21:18:02.834177Z
0 likes, 0 repeats
writing a daemon for extreme sadposting that implements the Mastodon client API, but only handles one user, makes all posts private, and doesn't federategonna call it Mastodon'tMastodon't will absolutely still let you fav and boost your own toots though, i mean, that's core functionality
(DIR) Post #2262933 by VyrCossont@princess.industries
2018-12-25T01:40:04.453157Z
0 likes, 0 repeats
you all probably thought i was joking 😈
(DIR) Post #2262934 by VyrCossont@princess.industries
2018-12-25T01:59:15.226940Z
0 likes, 0 repeats
i'm only mostly joking, implementing the server side of OAuth2 is a pain in the ass, and reimplementing any API without some kind of IDL document describing it is extremely tediousi'm also not suuuper impressed with the Vapor server-side Swift framework so far, mostly due to poor docs. never trust a framework that buries any mention of error handling in the style guide.there's three other ones i need to look at:• Zewo: almost certainly dead• Perfect: might be dead, docs remind me of dealing with Typesafe/Lightbend Scala stuff like Play in a real bad way• Kitura: looks active and documented, and represented on the server-side Swift working group, but extremely IBM, which is a brand that i regard with only slightly less distaste than Oracle