d5e9f6be47
Merge branch 'develop' of https://akkoma.dev/AkkomaGang/akkoma into use_fep-c16b_formatting_mfm_functions
Sounds sensible, yes.
This seems cleanest and allows for future internal actors with follower collections
If a goal is to use "service.json" for these type of Application actors, you could…
both
relayandinternal.actoralso are marked asactor_type = Personin my database °~°
huh, that shouldn't be the case since AkkomaGang/akkoma#457
But,…
There's a bunch NULL nicknames, but relay is the only local one. internal.fetch and relay are also the only actors of type "Aplication".
In case it's usefull, here's the…
The relay is also an "Application" actor, and its nickname is NULL in my database (so in code I guess represented as this nickname: nil)
Maybe a more important question; Do you consider this a blocking issue? If not, I'd like to keep it for now, as I do consider it a strict improvement regardless, and then see what people think.
dataattributes don't actually tell the frontend what display is expected
Yes it does, that's what FEP-c16b is…
I should maybe rephrase myself. We get an object who has a content field. It also has a source field. Currently we use the source field, and that causes problems. This whole excercise here…
That one has crossed my mind too, but also has its problems (and worse imo).
From a code-complexity perspective; We now need a way for css to know what posts are mfm and not. It's doable, we…
I continue to think it’d be best for API users to perform the “data → style variables” transformation in the backend, so any frontend/app can easily support MFM rendering by just…
set the emoji height to 2em instead of a fixed pixel value
Yes! I didn't understand why I needed extra CSS for emoji while Foundey didn't ^^' Using em works perfectly, thx!
One problem I…
Seems to work fine in testing; thanks!
Nice find re
--faint. I’m not really qualified to judge thewhitespace: pre-wrapstuff, but the explanation sounds convincing and i…