found a bug in pleroma miniapps deploying after I take a shower
Timeline
Post
Remote status
Context
12
@sun@shitposter.world lmk when you merge my pr so i can drop my workaround from my misskey fork
@anemone ok I'm reading it after I take a shower.
@anemone it won't break existing installation right?
@sun@shitposter.world yeah it will unfortunately because your current registration system conflicts with OAuth2 DCR. I'm not intending to push you to do it right away I just want to know when it happens so I can remove the shim I have in place
@anemone oh woops already merged. I guess we just force everyone to log in again?
@anemone tell me what I need to do to support this right away
@sun@shitposter.world it wont invalidate existing sessions
@anemone ok so it is actually ok, it will just make people log in again? there's already a bug on pleroma thats forcing that anyway
@anemone incidentally if there's a way to generalize how we get identity and post statuses so it supports both mastodon and misskey so its not a terrible burden for miniapp developers, I am okay with supporting just these two
@sun@shitposter.world yeah I'm still looking at that aspect. probably some fairly simple stuff I can do. my PR was just focused on making the app registration path work with Oauth2's dynamic client registration and discovery specs
@anemone no problem just saying.
I am looking at maybe getting some money from someone to work on this, and it may be possible for me to maintain patches for mastodon and misskey if those projects won't upstream
I am looking at maybe getting some money from someone to work on this, and it may be possible for me to maintain patches for mastodon and misskey if those projects won't upstream
@sun@shitposter.world I already maintain patches for misskey that I doubt they'd upstream so I'd be up to help w/ that
Replies
0
No replies yet.