@7666 "slightly fucked"

@Phantasm @Mämmi Enjoyer :flag: @lain @nicole mikołajczyk 🔜 piwo ➡️ gpn a lot of these forever issues would also disappear if clients wrote activitystreams, but that's also a never ever thing at this point

@Phantasm @lain @nicole mikołajczyk 🔜 piwo ➡️ gpn @Mämmi Enjoyer :flag: the meme answer is that glussy was right and tagging/namespacing ought to be separated from the content, a more serious answer might ask for a note/article split where content rendering might be specified better instead of implied forever by the first big dick to get there and then nested over, but also, things like mentions and hashtags are trivial enough to be left up to the client as you suggest

@Phantasm @lain @nicole mikołajczyk 🔜 piwo ➡️ gpn @Mämmi Enjoyer :flag: yes, taking two horrible things and pretending their whole makes the mess better, the activitypub way of development

@Mämmi Enjoyer :flag: @Phantasm @lain @nicole mikołajczyk 🔜 piwo ➡️ gpn html as a payload for content

@Phantasm @lain @nicole mikołajczyk 🔜 piwo ➡️ gpn @Mämmi Enjoyer :flag: mastodon deciding on sending microformats was already bad enough, no more pls

@nprofile1q... fontconfig is such a mess, but replacing it would be a wayland tier mistake

@menherahair :redeyeorb: all anyone ever learned from the last 30 years of protocol design is that postel was fucking wrong

@$locklime this is how linux shows kernel panics now, usually there's a qr chode too like

as far as what happened, a fuck up in a brittle way to boot nvme on a server that doesn't support it, and stuff going out of sync with partial updates

@Paultron-3030 this ddr3 shitter has enough to where more is expensive again, only took a proper syu to fix it