@p almost done my live log parser complete with status code filtering, requests over a buffer limit highlighted in a different color, ip anonymity toggle (in this case it's the nitter log), the ability to search the entire log, pausing live to investigate, themes, ua agent filtering/sorting, live (shitty hemispheric map made with :: (going to redo this). might be ready to send a copy if you want to try it out since I know you like your mon2.sh. sorry it's written in python
Timeline
Post
Remote status
Context
8
@ailatan @p sorting in burst mode properly supports user agents now as well as IPs. just going to try to draw an ascii map or just strip it out altogether and ship it I think. I'm satisfied unless anybody else who has to view logs on the daily for long periods of time has anything else to chime in with
>inb4 Goyfeed
again this is the log for the nitter so the one for poast will be a lot more interesting (but its a lot larger and takes forever to buffer since it loads the backlog while tailing the current incoming)
edit: oh yeah poast's log is gonna take a while
>inb4 Goyfeed
again this is the log for the nitter so the one for poast will be a lot more interesting (but its a lot larger and takes forever to buffer since it loads the backlog while tailing the current incoming)
edit: oh yeah poast's log is gonna take a while
at the UX end of things, i would be fine with limits like one post per minute and one reload per 15sec. storage-wise, i feel that images need enough detail to be understood. imho, high res is for autistes.
btw, are we seeing "web optimised" images different from the upload? because i would be fine with seeing thumbs in the thread and original quality via the dl button. (ie, images >120kb get an embedded thumb for the inline view).
i haven't done my homework so, if these are real rookie takes, just say so.
@tobias @ailatan @p the backend software has the ability to generate thumbnails and provide the full scale image when it is opened but back in 2021 people complained and it caused a lot of constraints on the hardware we had at the time so we disabled it. its something we can look at again, but the amount of emojis that get loaded when you load poast and open the emoji picker are far larger in terms of overall size than what you'd get just casually browsing the timeline lol
@graf @tobias @p Navigating the emoji picker is indeed quite painful, because the less frequently used pictures take forever to load. Also, some of the file sizes are quite absurd for such small images.
For example https://poa.st/emoji/stolen/AngryGlitch.png is 253 kilobytes. The attachment is an AVIF conversion at only 39 kilobytes: ffmpeg -i AngryGlitch.png -crf 50 AngryGlitch.avif
For example https://poa.st/emoji/stolen/AngryGlitch.png is 253 kilobytes. The attachment is an AVIF conversion at only 39 kilobytes: ffmpeg -i AngryGlitch.png -crf 50 AngryGlitch.avif
@graf @ailatan @tobias @p >100mb emoji
>mouse over to see what it is
>it's gay niggers from outer space
>mouse over to see what it is
>it's gay niggers from outer space
Replies
1