[misskey compat] add config option to change the misskey ticker color #17
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#17
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?
currently all posts from (pler|akk)oma instances show up on misskey with a grey banner under the instance name:
you can patch pleroma-fe to add the following line to
index.html
to make misskey display any RGB valuemaybe this should be configurable via akkoma and admin-fe? probably somewhere under
:instance
i was going to say "wait, that's insanely stupid why would it parse HTML to get instance information!?" then remembered it's misskey
this should... really be done via nodeinfo
i'll see if i can dig into misskey's source to figure out if it can be, if not i'll bug syuilo about it because it's p bad to rely on the frontend for federated information
looked into it, we already support this via
config :pleroma, :manifest
it's just grey by default
https://docs.akkoma.dev/main/backend/configuration/cheatsheet/#manifest
this seems to relate to PWA settings, so misskey just happens to take a thing from them and use it for their banner rendering, then? i see
also
yeah this makes sense in the context of a PWA but when it's used in a different way it's kinda weird
yeah, syuilo doing syuilo things
we should probably raise it with them as questionable
i'll have to try and format a sentence in japanese help me
raised as https://github.com/misskey-dev/misskey/issues/8897
reopening this issue just to keep track of it
looking unlikely that this'll happen their side
i'll just mess with
server-generated-meta
:(