c8add9d1dc
Merge pull request 'fix invalid proxy_hide_header in example config' (#472) from flisk/akkoma:remote-media-docs-fix into develop
d43c8080d0
Merge pull request 'updating docs: start akko first, then upgrade frontend' (#486) from flisk/akkoma:fix-updating-docs into develop
f22c6e4108
Merge pull request 'Update docs about clients' (#484) from mahito1594/akkoma:docs/update-clients-info into develop
f22c6e4108
Merge pull request 'Update docs about clients' (#484) from mahito1594/akkoma:docs/update-clients-info into develop
\n as newline for MFM
I know 😃 I was afraid I was gonna need to do very hacky stuff, but there it was 😄
A discussion in chat reminded me of https://www.w3.org/TR/activitypub/#inbox-forwarding
So basically, we don't need to announce, the reply should already have correct addressing and we need to…
Personally I 100% agree because this has annoyed me as well.
I think, technically speaking, the supported Elixir versions should be what's defined in [mix.exs](https://akkoma.dev/AkkomaGang/akko…
\n as newline for MFM
content field using HTML
you are ignoring the line break markup though, in the snippet you gave there is
<span><br></span>
Indeed, we do ignore this! Akkoma will check if the source is of mediaType `text/x.misskey…
content for posts, also when it's MFM.
I now understand why we do what we do. The problem is that the content doesn't contain the needed html. I made an issue for Foundkey now https://akkoma.dev/FoundKeyGang/FoundKey/issues/343.
…
content field using HTML