mirabilos

stale[bot] dixit: >Is this still relevant? If so, what is blocking it? Is there anything […] *sigh…* see also: ***@***.***/109712205752112196 bye, //mirabilos -- Yes, I hate users and I want...

Tim Schwenke dixit: >@mirabilos, I admire your persistence 😆 I hate the “stalebot” concept on principle (there recently was a good article about that on Fediverse, too). bye, //mirabilos --...

Daniel Widdis dixit: >Second, on the opposite end, if a repo is actively maintained, there >are often bug report/issues where the maintainer asks a question and it >just sits there......

Mathieu Carbou dixit: >And I am baffled to see how many people would find something useful, >but none is courageous enough to send a complete PR. Can you imagine people...

tobi dixit: >Is this fixed in 0.6.0? :) Thanks for reminding me to check. Yes, it is (I even tried with a fresh dummy ext2 on loopback), and after running...

Ah okay, so that’s also for too large attachments witrh known types? Thanks!

Wild semi-educated guess: someone set an encoding validation library to replace with U+FFFD then checks for the presence of that to cause an error. Hm, though that’s not so likely...

Nope, the database is fine: ``` gotosocial=# UPDATE statuses SET content='�', text='�' WHERE id='01GHGKE8MFA1D894DDQTV6ZHQN'; UPDATE 1 ``` Apparently, it even can serve this: https://toot.mirbsd.org/@mirabilos/statuses/01GHGKE8MFA1D894DDQTV6ZHQN

There were no instructions on with what parameters to create the database, so I just used sensible defaults: ``` Name | Owner | Encoding | Collate | Ctype | Access...

 Yep.