Owncast federation fix from upstream (how to handle upstream) #30
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#30
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
Pleroma has an MR open to fix owncast federation stuff:
https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3666
How you wanna handle 'upstream' do you plan to cherry-pick stuff from there? Or do you wanna follow upstream, or should akkoma go its own way? Just asking cause, i wanna know if i should open issues like this, or just wait for you to pull stuff ^^
Owncast federation fix from 'pstream (how to handle upstream)to Owncast federation fix from upstream (how to handle upstream)ah it's entirely cool to open issues like this, better for more of us to keep an eye on the base software for bugs than relying entirely on me
and yea i'll see if i can cherry-pick that, and i'll look about adding a test to it
Uh.. that was hella fast.
Thanks <3
naturally, federation issues are critical bugs in my books
plus yknow I can just merge things :aidab:
Mhh sadly, still doens't work. it seems that the MR included only a part of it -> https://git.pleroma.social/pleroma/pleroma/-/issues/2864 even with the fix mentioned by shadowfacts, i can't see any owncast posts at all on my instance.
Gonna spin up a test instance propably next weekend and try do debug it :akko_fistup: