@p @sjw can one of you guys let @r000t know that i think I figured out his issue with why he cant see poast, in the past couple months cloudflare has quietly rolled out a "super bot protection" firewall that seems to be blocking about 4.6M "probably human" requests (mastodon servers) so I have put in a request to cloudflare to explain why this was implemented without our request or permission and why it cant be turned off in the console

@graf @r000t @sjw

@r000t :

> can one of you guys let @r000t know that i think I figured out his issue with why he cant see poast, in the past couple months cloudflare has quietly rolled out a "super bot protection" firewall that seems to be blocking about 4.6M "probably human" requests (mastodon servers) so I have put in a request to cloudflare to explain why this was implemented without our request or permission and why it cant be turned off in the console

@lanodan @p @r000t @r000t @graf their CDN is pretty nice

@sjw @p @r000t @r000t @graf I probably would adopt something like ipfs or similar to do mass mirroring/caching-proxy.
CDNs to me are quite a disease.

@lanodan @p @r000t @r000t @graf that's what revolver plans to use and I mentioned to :p: that it probably wouldn't be too hard to hook ipfs into Pleroma's media_proxy

@sjw @lanodan @graf @r000t @r000t Revolver already uses it, but it's not mandatory; it works without IPFS.

I think you definitely could do media proxy with IPFS, or just serving most media.

@p @r000t @r000t @graf @lanodan instructions on how to when?

@sjw @graf @lanodan @r000t @r000t Trivially, you could just do the FUSE mount and symlink shit in the media proxy dir to the FUSE mount. You could try their FS thing but that was experimental last I checked. If you run the proxy server (I think the daemon includes it by default) you could have nginx reverse-proxy to it for that, and that'd include the headers that would let people fetch stuff from IPFS instead of the server if they have the plugin installed.

@p @sjw @r000t @lanodan ill have to read the documentation about mounting IPFS as fuse, thats really cool (but fuse + pleroma is bad, as you've watched us learn)

@graf @sjw @p @r000t
FUSE is just terribly bad.
And I'm the kind which can tolerate some of NFS troubles (not the ones caused by applications themselves being stupid though).

@lanodan @sjw @p @r000t pleroma waits for a filename from the file system so if FUSE is hung up and 4-5 people are uploading it locks pleroma up and everything fails until fuse realizes its not cool

fuse is a shitty filesystem

@graf @sjw @p @r000t
*everything* fails? It should just fail for uploads.
But well, that's the broken shit you get with the old Unix syscalls which basically do not have timeouts and are blocking, which is hell for coroutines.

FUSE is a fail for other kind of things, like fusermount tends to require you to be root, even if it's mounted as your own user (which I think shouldn't be something allowed without user-namespaces, why the hell is Plan9 more secure than modern unixes…).

@lanodan @sjw @p @r000t pleroma waits for the FS and database to give it the random filename, if that doesnt happen the database hangs and the fe hangs. you can watch it happen in real time mounting anything as CIFS

its a massive issue with pleroma and im surprised poast using something as a backup exposed it, when a user initiates an upload with upload scrambling enabled the filename should be stored in the ticket used to insert it in the database and none of this happens. this is pleroma being inadequate and its maintainers crying instead of doing something. we reported it weeks ago

@graf @sjw @p @r000t
> This is pleroma being inadequate and its maintainers crying instead of doing something. we reported it weeks ago

Pleroma backend basically only has me as a maintainer and to be honest, I have no motivation for anything but fixing stuff which gets in my way or things that are directly fun.
Which is why these days I just guide contributors, mostly with the hope of retiring from maintenance.

Reason for this being basically: No funding for most of 2021 while trying to keep things afloat, which has then been destroyed by Gleason acting like an irresponsible kid for at least a full month.
And if I remember correctly, you played your cards in this.

@lanodan @sjw @p @r000t ok so how much do you want me to pay you to stop pleroma crashing when someone other than poast uses CIFS or something tell me your price to fix it and whatever petes issue was

this is so aribtrary man it just makes you look bad so just give me a price

@graf @sjw @p @r000t None, try with the other contributors.

Price was something you could have done before, not once most of us have walked away or are preparing to.

@lanodan @sjw @p @r000t i personally hold you to a different standard but if your response is to just fuck pleroma proper off that just solidifies any thought we had that we need to ditch pleroma asap

@lanodan @sjw @p @r000t i was maybe a half dozen eggs in the pleroma basket but i will put all of them in revolver, shame it is because pleroma was really good. its not great, and it will never be now but it was OK.

@graf @sjw @p @r000t
To maybe clarify things a bit: Pleroma backend is in survival mode, it could go back entirely to life, and I truly do wish this, but I barely can push it further. I'm glad there is other contributors, some which I think could be maintainers.
But it's clearly not at the speed that it had during MFC time, which is the one that most knew where we had a huge team of full-time devs working at their own discretion.

As for revolver… I'll see once the code is released, I'm too much of a nerd to trust speech, at least it sounds interesting.

@lanodan @graf @r000t @sjw

> But it's clearly not at the speed that it had during MFC time

What happened with MFC, is that talkaboutable?

> I'll see once the code is released, I'm too much of a nerd to trust speech