@exerian <br> should work

@froggebip I do know that akkoma has a setting that adds an re: to the CW on replies to posts with a CW, but other than that, no idea

@froggebip still nothing, even after I disabled my media proxy. that’s weird

@froggebip mine still isn’t working, seems to be trying to fetch this URL https://lilypad.frogge.cafe/fileserver/01MVJ1MJZ675FRDK4TMMGQTJ8G/attachment/original/01J8J0JE4SGXXXPT8SRE8K00MZ.png and 404’ing

@nora yessss

yknow, I wish akkoma(/akkoma-fe) had the “warn when sending an image without alt text” feature, I know that some other fedi frontends do have it and it does come in handy

@ruby

@nora @ruby that actually makes sense. I’d still check if the instance software doesn’t do additional Weird Things with the text tho

@nora @ruby …wait, out of band tags are in the spec? I somehow did not know that, and now I’m wondering if we could do something with that (though it probably would require some integration effort)

@vision @froggebip same with my akkoma

@viv @bobskunk yeah, encountered that a bunch when trying to share post links with some friends

@bobskunk @viv yeaaa, I know, some types of instances handle that better than others (for example, firefish worked fine iirc)

@nora I really gotta grab that one

@viv @bobskunk it sure does work for me

@bobskunk @viv you can always try pasting the post link into the search bar fyi

@morine @girlcodedcreature @gcugreyarea ah, that’s probs a gts specific thing

@viv aaaand I don’t see any obvious place where it could be in the db. oh well, I guess I’ll live with it until I get around to looking at the source code to check where it puts those

@viv weird indeed. it’s just giving me a 500 in admin-fe and pretending the report was resolved until a refresh in akkoma-fe

@tenna update: I just made a test admin account and did it on my instance, it’ll just deactivate the account without any warnings, but you can reactivate it from another admin account (you can use the mix task to create one)