thickertoofan

joined 1 day ago
[–] thickertoofan@lemm.ee 2 points 2 hours ago (2 children)

that's not the issue here, i'm talking about the technical bug, I do understand that i am not yet qualified for image uploads.

 

I see this error when I'm trying to upload an icon image for a community I've recently created:

{"data":{"error":"pictrs_response_error","message":"Your account is too new to upload images"},"state":"success"}

I suppose, if the state of upload was success, and assuming the API output is correct, that the image either got uploaded or got denied after upload.
It seems like we can do an improvement if there is a bug, that we should do perm check before image upload happens, this way, we can save bandwidth (i mean its negligible but i dont know if it happens in other places like image posts etc.).
And we can prevent useless upload/bandwidth usage (which i dont think happens in this case) and if this doesnt happen, then the API has a bug of giving a false status message? Just discussing here before raising an enhancement issue on the github repo. The bug is either of the two cases, I'm not sure.

[–] thickertoofan@lemm.ee 5 points 4 hours ago

welp, TL;DR from comments says its fear mongering at best, physical access required right?

[–] thickertoofan@lemm.ee 1 points 4 hours ago

you can do cpu inference too! if you have enough ram to load GGUF formats :)

[–] thickertoofan@lemm.ee 4 points 5 hours ago

as a cs major, you kicked me in the stomach with this one

[–] thickertoofan@lemm.ee 1 points 5 hours ago

working and progressing, learning, staying healthy

[–] thickertoofan@lemm.ee 9 points 7 hours ago

yay, my once which was my fav platform becoming a shitshow. i won't miss it