[bug] Guppe Groups broken somewhere v3.14.0..v3.15.1 #901
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 change/feedback
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#901
Loading…
Add table
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?
Your setup
From source
Extra details
Ubuntu 22.04, kernel 5.15.0-105-generic, x86_64
Version
v3.15.2
PostgreSQL version
14.17
What were you trying to do?
I'm trying to use groups hosted at a.gup.pe. One account on my server has followed https://a.gup.pe/u/bookstodon for several months. Recently, I've been trying to follow https://a.gup.pe/u/openscadclub
What did you expect to happen?
After clicking the Follow button, the button should eventually change to "Unfollow", and I should see boosts from the group account on its profile on my server.
What actually happened?
The Follow button changes to "Request sent!", but never changes to "Unfollow". Boosts from the group never appear.
Additionally, for the group that someone had followed several months ago, the last boost that my server has seen from it happened minutes before I upgraded from Akkoma v3.14.0 to v3.15.1.
Logs
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
This is a bug in whatever software a.gup.pe uses.
It identifies its key id as
https://a.gup.pe/u/bookstodon
in the signature, but then actually advertises the key ashttps://a.gup.pe/u/bookstodon#main-key
in the AP object. Such bugs also break federation with other software (e.g. in the past bookwyrm failed to federate with GtS for such a reason). Please contact the developers of a.gup.pe’s software instead.There is nothing to change on Akkoma’s end; our current behaviour is correct.
Thanks for the quick response, Oneric. I opened https://github.com/immers-space/guppe/issues/117 and will close this one.