AkkomaGang/akkoma
AkkomaGang
/
akkoma
12
63
Fork 83
Code Issues 169 Pull Requests 14 Packages Projects 2 Releases 13 Wiki Activity

meta: closeable issues #758

New Issue
Open
opened 2024-04-26 00:55:59 +00:00 by Oneric · 0 comments
Oneric commented 2024-04-26 00:55:59 +00:00
Member
Copy Link

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

  • #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
  • #508 fixed by 0c77be9308
  • #477 seems to be documented now in install docs
  • #420 fixed by #422
  • #277 see comments; fixed by 3e0a5851e5
  • #241 implemented by #744

Maybe no longer applies

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

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

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

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 - [ ] #637 fixed by #681 - [ ] #508 fixed by 0c77be9308102cb2e4710fbad02035e9dc7125c3 - [ ] #477 seems to be documented now in install docs - [ ] #420 fixed by #422 - [x] #277 see comments; fixed by 3e0a5851e5 - [x] #241 implemented by #744 ## Maybe no longer applies - [x] #153 according to comments in the linked PR, the HTML post format was purged so this no longer applies ## 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 ## 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 ## Missing info; no author response - [ ] #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) - [ ] #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 - [ ] #283 i don’t know which supposedly existing CLI task this is referring to
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
develop
backoff-http
stable
translations
bad-uploader-config-warning
docker
user-expiry-backfill
config-db-keys
ensure-scrubbers-loaded
otp26
code-shaking-does-not-go-brr
elixir1.15
circleci
backup-fixes
mod-task
policy
mrf-coolness
frontend-switcher-9000
contentMap
language-on-posts
rabbit
credo-on-pr
unify-http
normalise-markup-by-default
buildx
v3.13.1
v3.13.0
snac-3.12.1.2
v3.12.2
snac-3.12.1.1
v3.12.1
v3.12.0
v3.11.0
v2.6.2
v2.6.1
v2.6.0
v2.5.5
v3.10.4
v3.10.3
v3.10.2
v3.10.1
v3.10.0
v2.5.4
v2.5.3
v3.9.3
v3.9.2
v3.9.1
V3.9.0
2023.05
v3.8.0
v3.7.1
v3.7.0
v3.6.0
v3.5.0
v2.4.5
v3.4.0
v3.3.1
v2.4.4
v3.3.0
v3.2.3
v3.2.2
v3.2.1
stable-202209
v3.2.0
v3.1.0
stable-2022.07
v3.0.0
v0.0.1
v2.5.2-6
v2.5.2-5
v2.5.2-4
v2.5.2-3
v2.5.2-2
v2.5.2-1
v2.5.2
v2.5.1
v2.5.0-8
v2.5.0-7
v2.5.0-6
v2.5.0-5
v2.5.0-4
v2.5.0-3
v2.5.0-2
v2.5.0-1
v2.5.0
v2.4.3
pre-rebase
v2.4.2
v2.4.1
v2.4.0
soapbox-v1.1.1
soapbox-v1.1.0
soapbox-v1.0.0
v2.3.0
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.7
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.1.9
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.91
v1.0.90
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
v0.9.0
Labels
Clear labels   
approved, awaiting change

   
bug

Something is not working

  
configuration

This requires config changes

  
documentation

This is about human-readable docs

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
extremely low priority

   
feature request

Something new?

  
Fix it yourself

Support has been attempted

  
help wanted

Need some help

  
invalid

Something is wrong

  
mastodon_api

   
needs docs

   
needs tests

   
not a bug

   
planned

   
pleroma_api

   
privacy

   
question

More information is needed

  
static_fe

   
triage

   
wontfix

This won't be fixed

No Label
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
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
No description provided.
Delete Branch "%!s(<nil>)"

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?