meta: closeable issues

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#758

Oneric commented

2024-04-26 00:55:59 +00:00

Member

Already fixed

#747 fixed by #752
#727 the described issue of retaining personal info did never exist in Akkoma (was already fixed in Pleroma before forking)
#659 see comments; long since fixed in develop, just wasn’t in 3.10.4 yet
#637 fixed by #681
#606 fixed together with #269 by #762
#579 superseded by #772
#508 fixed by 0c77be9308
#477 seems to be documented now in install docs
#420 fixed by #422
#419 same as #606 above
#277 see comments; fixed by 3e0a5851e5
#241 implemented by #744
AkkomaGang/akkoma-fe#386 feature implemented by AkkomaGang/akkoma-fe#387
#820 fixed by #815
#858 fixed by 3.15.0

Cannot reproduce

#826

Maybe no longer applies

#153 according to comments in the linked PR, the HTML post format was purged so this no longer applies

Duplicate

#777 frontend issue, now moved to the fe repo (but be issue not yet closed)

Not our issue

#735 apps targeting Mastodon can't use Akkoma features
probably #704?
#654 OP dropped and incorrectly restored the database, resulting in a borked internal fetch actor. As a result federation was completely broken. Links to their posts with more info are dead; instance runs Mastodon now
#571 Lemmy used to not support signed fetches at all (and maybe still doesn’t sign by default not sure) which given AuthFetch was mentioned very likely is the issue here. In any case, additional requested info wasn’t provided in neither our nor the associated Lemmy issue and the Lemmy issue was closed a bit more than a month ago
AkkomaGang/akkoma-fe#395 Chromium bug

Not an issue

AkkomaGang/akkoma-fe#380 the source and purpose of the indicator as well as how to hide it was explained; there’s nothing to do
#835 (at best a feature request)

Missing info; no author response

#723 the author probably just forgot to upgrade admin-fe; but no response
#469 who knows what went wrong without logs and uploads work for everyone else so ¯\(ㇱ)/¯
#490 ~~(but due to recent activity i’d wait a bit longer to see if one of the two returns with the requested info)~~

Outdated (and also insufficient info)

#561 following GTS accounts works for me, maybe an old GTS bug, maybe an old Akkoma bug. Either way without new info from the author it’s impossible to do anything
#281 i successfully followed an Owncast account since and given the age this might have very well been an old Owncast bug
#215 whatever issues with migrations from Pleroma existed in 2022, with both projects changing the DB further since things will be much different now

Not sure

#485 maybe a mix of normal federation desync and #190? #190 shouldn’t affect akkoma-fe, but it’s hard to tell what additional things might or might not be happening without actual logs
#283 i don’t know which supposedly existing CLI task this is referring to

There are a bunch of open issues which are actually already resolved by some PR or invalid etc. Furthermore if an issue couldn't be reproduced and the author didn't respond to requests for more information there’s nothing which can be done and we imho might as well close the issue. I’ll list them all below: ## Already fixed - [x] #747 fixed by #752 - [x] #727 the described issue of retaining personal info did never exist in Akkoma (was already fixed in Pleroma before forking) - [x] #659 see comments; long since fixed in develop, just wasn’t in 3.10.4 yet - [x] #637 fixed by #681 - [x] #606 fixed together with #269 by #762 - [ ] #579 superseded by #772 - [ ] #508 fixed by 0c77be9308102cb2e4710fbad02035e9dc7125c3 - [ ] #477 seems to be documented now in install docs - [x] #420 fixed by #422 - [x] #419 same as #606 above - [x] #277 see comments; fixed by 3e0a5851e5 - [x] #241 implemented by #744 - [ ] https://akkoma.dev/AkkomaGang/akkoma-fe/issues/386 feature implemented by https://akkoma.dev/AkkomaGang/akkoma-fe/pulls/387 - [ ] https://akkoma.dev/AkkomaGang/akkoma/issues/820 fixed by #815 - [ ] https://akkoma.dev/AkkomaGang/akkoma/issues/858 fixed by 3.15.0 ## Cannot reproduce - [ ] https://akkoma.dev/AkkomaGang/akkoma/issues/826 ## Maybe no longer applies - [x] #153 according to comments in the linked PR, the HTML post format was purged so this no longer applies ## Duplicate - [x] #777 frontend issue, now moved to the fe repo (but be issue not yet closed) ## Not our issue - [ ] #735 apps targeting Mastodon can't use Akkoma features - [x] probably #704? - [x] #654 OP dropped and incorrectly restored the database, resulting in a borked internal fetch actor. As a result federation was completely broken. Links to their posts with more info are dead; instance runs Mastodon now - [ ] #571 Lemmy used to not support signed fetches at all (and maybe still doesn’t sign by default not sure) which given AuthFetch was mentioned very likely is the issue here. In any case, additional requested info wasn’t provided in neither our nor the associated Lemmy issue and the Lemmy issue was closed a bit more than a month ago - [x] https://akkoma.dev/AkkomaGang/akkoma-fe/issues/395 Chromium bug ## Not an issue - [x] https://akkoma.dev/AkkomaGang/akkoma-fe/issues/380 the source and purpose of the indicator as well as how to hide it was explained; there’s nothing to do - [ ] https://akkoma.dev/AkkomaGang/akkoma/issues/835 *(at best a feature request)* ## Missing info; no author response - [x] #723 the author probably just forgot to upgrade admin-fe; but no response - [x] #469 who knows what went wrong without logs and uploads work for everyone else so ¯\\(ㇱ)/¯ - [ ] #490 ~~(but due to recent activity i’d wait a bit longer to see if one of the two returns with the requested info)~~ ## Outdated (and also insufficient info) - [x] #561 following GTS accounts works for me, maybe an old GTS bug, maybe an old Akkoma bug. Either way without new info from the author it’s impossible to do anything - [x] #281 i successfully followed an Owncast account since and given the age this might have very well been an old Owncast bug - [x] #215 whatever issues with migrations from Pleroma existed in 2022, with both projects changing the DB further since things will be much different now ## Not sure - [ ] #485 maybe a mix of normal federation desync and #190? #190 shouldn’t affect akkoma-fe, but it’s hard to tell what additional things might or might not be happening without actual logs - [x] #283 i don’t know which supposedly existing CLI task this is referring to

Rows
Columns

meta: closeable issues #758