@yonle https://github.com/Yonle/go-bwhero this seems pretty nice, i thought about using img for this, but this seems kind of equivalent
Timeline
Post
Remote status
Context
5
@lain i use this to pair it for mediaproxyoma: https://github.com/Yonle/mediaproxyoma
@yonle very nice.
btw pleroma-fe will by now automatically compress image uploads, so at least if people use that we won't get those 20mb pngs anymore...
btw pleroma-fe will by now automatically compress image uploads, so at least if people use that we won't get those 20mb pngs anymore...
@lain btw i just added API.md, documenting on how to use the API. it's short & quick.
https://github.com/Yonle/go-bwhero/blob/master/API.md
https://github.com/Yonle/go-bwhero/blob/master/API.md
@lain since the early February, fedinet.waltuh.cyou has been using mediaproxyoma+go-bwhero as the backend for the media proxy. There's simply too many things wrong with mediaproxy code that's in both akkoma and pleroma, and that includes broken video thumbnailing.
@lain as the result, i made a patch where avatar, and cover/banner is using the compressed version since it’s no use to put 540x540 image in such small <img>, and then disable preloading & make <video> to show thumbnail instead. This has reduced my bandwidth & our users since then.
Replies
6@lain in akkoma, i made attachment.akkoma.media.avatar_preview and attachment.akkoma.media.header_preview. The same can be done on pleroma too but if that’s the case, then i will make some breaking changes between both backend. Let’s see.
@lain and then, since mediaproxy didn't make preview link at all on local attachments, so i modify the backend to make it do exactly that.
@yonle i'm really trying to solve a different issue here, and that is people uploading 20mb photos from their phone. this isn't solved by generating smaller previews (which medaiproxy can already do) because the full view will still download a 20mb png to a phone screen.
Looking into hosting. Learning. Still lost. But that's ok for now. I was looking into fe, seems to have changed names?
https://codeberg.org/mkljczk/nicolex
On the note of images:
(I'm self taught, new, & may have misconceptions)
Can you use reverse proxy & intercept the url to only display the compressed images?
For full resolution could you setup an api? Have clients that respect this api call download full res?
I need to read more and learn pleroma.
I hope this wasn't just bad noise.
@rusty__shackleford @yonle yes, you can thumbnail / shrink everything, mediaproxy could do it. the issue is that there is a very specific need that currently serve correctly (i.e. i want to show my 120 megapixel png in full quality) while there's a near universal issue that we mostly ignore (i.e someone uploads their 120mp png because that's just what their xiaomi 231 hasselblad supermi takes and now everybody gets a huge download)
@rusty__shackleford @lain Nicolex is it’s own thing. different fork. I haven’t dived what’s different here but it seems like there’s some interesting patches from here.
Can you use reverse proxy & intercept the url to only display the compressed images?
you can, but then you need a backend that do the job.
For full resolution could you setup an api? Have clients that respect this api call download full res?
It will only applies in pleroma if respecting the api is the goal. You see, there’s 2 field in attachment object: url being the url of the real thing, preview_url for the thumbnail only.
but if your goal is to make it only render the compressed version on both field, then you must decide this. Either you want this to work only in pleroma fe, or both world (pleromafe and mastodon apps).