@anth@a.9srv.net (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has always mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)

@movq@www.uninformativ.de Yeah this is why thin @anth@a.9srv.net is that and that any v2 spec we get around to actually publishing with far better quality than the bullshit half-baked attempt I tried to 🤣; should just mandate utf-8 period. Just assume it to be true, there is no other content encoding we should ever support 😅