WIP: Use raw status text instead of html encoded text #88
No reviewers
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#88
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "(deleted):status-text"
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?
do not merge
holy shit for the love of god do not merge
i wanna see just how much stuff this breaks, and if this could be deemed safe enough to use in production or if i should find a different solution for the mfm bug
characters like
<
and>
are html-encoded in statuses meaning it's impossible to use<center>
and<small>
tags, as well as> quotes
.i could fix this in marked-mfm and just make it accept
<
i probably should do that, actually
i'm just not smart enough to decide if this is a remotely good solution or not and i need feedback
these are indeed escaped by the backend
what we could do is allow it in the scrubber -> https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/priv/scrubbers/default.ex
which should pass
<center>
and<small>
as expectedwouldn't that make them render as center and small in plaintext mode, too?
(though actually that's a downside of this method as well i should just do the
<
thing)nope, plaintext doesn't get passed through the same scrubber
works though so there's that
oh cool
and what about quotes?
(also center is still broken you might notice that markdown formatting does not work inside a center tag, i fix that in a future marked-mfm version)
ah it doesn't work inbound though
ok hm
ok i found something that does work, one sec
branch small-center-mfm (BE) should somewhat work
>
won't, because... honestly i don't know a safe way to do that right now, but i'll look tomorrowyeah this can be closed then
Pull request closed