>We are in some blocklists flagged as racists and have you ever seen me being racist? Most of the reasons are made up anyway. Probably the reason why your instance is on some blocklists is that you federate with instances like SPC/SPW, Asbestos cafe,... Racism is just a blanket word for a "valid" reason.
@voltrina@anna >"uses a blockbot" immediately defederate this instance
Embed this noticePhantasm (phnt@fluffytail.org)'s status on Friday, 05-Apr-2024 06:41:22 JST
Phantasm@anna >i can't recall a single instance of someone talking shit about Ro and actually showing a concrete example of what he did wrong. Here's one: Majority of The Bad Space's rating has absolutely no reasons given. X amount of instances block this instance is not a valid reason. And if it actually has a reason, they are either wrong, heavily opinionated or outright made up. Usually a combination of these three.
@f_o_u_r_t_y@roboneko@dushman@splitshockvirus This time I agree with dush, VLC on Loonix has many problems that have been there for months and years. Zombie processes, decoding problems, crashes while MPV just works. Granted it has basically no UI and everything is done with keyboard shortcuts, but there are many frontends for it.
@VD15@SuperDicq@iceloops It did, but 100 for a 7 year CPU is still a lot, especially now when it's performance would probably would get beaten by a low end AMD CPU.
@mint@Inginsub You are right, it would need more than just a media proxy patch and a cron job. Didn't think about that. I have some ideas, but most of them aren't ideal.
I'll add that to the never ending pile of pleromer experiments I have in mind.
@mint@Inginsub This may be a dumb idea, but you could possibly modify the nginx invalidation shell script to move the file to a specific long-term directory and patch the media proxy to also look there. Then if you do some clever atime/ctime stuff you can delete old cached files depending on their age or size with a cron job.
Of course you can do all of that without patching the media proxy and use the default folder, but if you ever wanted to disable that, there could be stale files left in the cache.
EDIT: There's not that much you can do with large file uploads. You could move the cache to a S3 bucket and that would solve the bandwidth limitations, but it will also be really expensive to manage and run. Or you can simply ignore them.
@mint@Moon@sun@sunman@captainepoch Changing the AP ID will also prevent interaction with that account. Backend doesn't recognize it as an account properly in some cases and doesn't mention the account in any posts.
There is an MR in the backend that might be able to fix mangled nicknames like this, but I did not check if it really fixes this or it's for another issue.
@Moon@pernia@sneeden@mint The featured collections yesterday returned the PleromaFE for some reason (with the application/json... in Accept header). Same thing happens on Club Cyberia. Cyberia runs quite recent versions of develop, so there might be a bug there. Did not check today because the relay worked when following from the mix task.