Hi, I believe this is something that was recently fixed in piefed, but we haven't deployed this patch yet. I'm currently planning to deploy an update in the coming days, might take until the next weekend.
it seems like voyager might be the only one displaying it correctly?
assuming that voyager is indeed displaying it correctly, that would indicate that mlem isn't handling the error correctly, as it seems to unconditionally try to access the url of the upload and failing to do so.
the web interface is probably also just not exposing the error message correctly.
quota exceeded is a very useful error message, that means it's likely an issue specific to the amount of media uploaded by your user. i'll have to check how upload quota is determined, but this is is not something we have customized. i suspect that this was intentionally changed with one of the version updates, probably not accounting well enough for people commenting as much as you do. it should not be related to the recent vulnerabilities.
it looks like this is caused by a default blocklist in piefed, an "anti-fascist domains blocklist of QAnon, conspiracy, fake news, far-right and discriminatory websites"
mostly indexes and in some cases changing queries.
there are lots of queries in piefed that are not using indexes and some that are just unoptimized sql statements. for example, there are a lot of like '%foo%' queries but there are no GIN indexes to support those queries.
unfortunately it's a hassle to manage custom indexes as they can't be part of the code migrations without fucking other things up, so for the time being i'm just keeping track of them by having a dedicated prefix for the index names and updating them in our DB manually. once/if they're upstreamed i'm removing our custom ones again, but it's not possible for us to track them in code.
some of the code changes for sql statements were upstreamed, but rimu didn't want to incorporate all of them without evidence of performance impact. it took me a bit to make sense of the more complex statements, but i don't have time or motivation to demonstrate performance impact for them, so i'll just keep the remainder in our fork. e.g. 1bf4d8409b vs c41d47850e.
Hi, I believe this is something that was recently fixed in piefed, but we haven't deployed this patch yet. I'm currently planning to deploy an update in the coming days, might take until the next weekend.
not sure, maybe try !piefed_help@piefed.social?
we're also a few versions behind currently that might contain bugfixes, but i haven't looked through all the changes yet.
this isn't piefed.social support and piefed.social doesn't host lemmy
which types of reports? post and comment reports should federate, user reports don't exist on lemmy yet.
all time - seems like a design flaw. i'll look at raising an issue on the piefed issue tracker in the coming days.
i've raised the limit for now.
would be great if you could report it
it seems like voyager might be the only one displaying it correctly?
assuming that voyager is indeed displaying it correctly, that would indicate that mlem isn't handling the error correctly, as it seems to unconditionally try to access the url of the upload and failing to do so.
the web interface is probably also just not exposing the error message correctly.
you should be able to see your upload volume here: https://piefed.world/user/files
the default limit in piefed is 50MB, which is rather easily reached. can you please confirm if you're indeed hitting that limit?
quota exceeded is a very useful error message, that means it's likely an issue specific to the amount of media uploaded by your user. i'll have to check how upload quota is determined, but this is is not something we have customized. i suspect that this was intentionally changed with one of the version updates, probably not accounting well enough for people commenting as much as you do. it should not be related to the recent vulnerabilities.
it works fine for me, which theme are you using?
e.g. https://piefed.world/c/birding@lemmy.world?sort=new&layout=list&content_type=posts&flair= looks like this for me with the more compact view:
did you maybe enable the most compact mode in settings?
oh, i thought this was limited to admins due to the info loaded there, but i guess this info is also loaded for people when viewing their own profiles
it looks like this is caused by a default blocklist in piefed, an "anti-fascist domains blocklist of QAnon, conspiracy, fake news, far-right and discriminatory websites"
can you provide some more context? are you getting an error message or something?
Hey, sorry for the delay, I've been traveling. I just made your PFW account owner of the community.
does being the sole mod in a community make you owner?
i guess piefed doesn't take the top mod structure lemmy uses into account at all?
mostly indexes and in some cases changing queries.
there are lots of queries in piefed that are not using indexes and some that are just unoptimized sql statements. for example, there are a lot of
like '%foo%'queries but there are no GIN indexes to support those queries.unfortunately it's a hassle to manage custom indexes as they can't be part of the code migrations without fucking other things up, so for the time being i'm just keeping track of them by having a dedicated prefix for the index names and updating them in our DB manually. once/if they're upstreamed i'm removing our custom ones again, but it's not possible for us to track them in code.
some of the code changes for sql statements were upstreamed, but rimu didn't want to incorporate all of them without evidence of performance impact. it took me a bit to make sense of the more complex statements, but i don't have time or motivation to demonstrate performance impact for them, so i'll just keep the remainder in our fork. e.g. 1bf4d8409b vs c41d47850e.
should be working now
it's working again: https://piefed.world/c/local_test/p/875614/test-steam-3
this is likely related to a bug that will be fixed in the next piefed release (currently in a development branch)
hey, do you happen and have an example at hand where this worked before?
edit: found some in your post history, looking into it