When I click view on the >>news/23797 Corona virus thread it only shows up to post 23868 but otherwise if I click expand then it displays everything up to post 23895.
That said, if I check the >>shed/13515 silly sausage thread and click view then it shows the entire thread - so I think something has broke on the news board.
I am using Firefox 64bit v75 on Windows 10.
Same thing happens on whatever version of safari iPads are on these days.
When opening a new thread it brings up the cached version instead of the new version. If you just leave it open it automatically updates itself eventually.
Same, particularly after I post in a thread then reopen the last 50 posts. I can't comment on the backend of this site but usually problems that are resolved with a page refresh are a browser (cache) issue.
Same for me on >>news/23522. On /sfw/ it shows up properly, but once I open the thread it stops at >>news/23706. It very much smells like a caching issue.
>>15329 Thanks! If it's been known for months that's a bit worrying. I just assumed purple would get a niggle in his brains if something was broke with brian. I m/A/y be projecting, of course.
I didn't want to start a new thread for something so trivial, but is there any possibility that Brian could support .webp images? They're becoming the standard across much of the internet, so it's a bit of a pain to have to convert things.
.webp is an image format, although one I've only encountered while accidentally using the mobile version of websites. Tabletlad needs to just force the desktop version to get all his legacy formats back.
It's a pretty good alternative to animated gifs, which are a bizarre inefficient dinosaur of a format.
But for stills though, yes it's utterly pointless. There's an argument that they save a bit of space when compared to an equivalent quality .jpg, but it's spare change in an age where every other website is packed full of autoplay videos.
Up until now I had assumed it was just some sort of image format DRM that stops me being easily able to save images off Google to repost on imageboards.
I'm not a computer magician but I think the only thing preventing them from working on Brian would be one line of code that contains the valid file types it will let you upload. Brian doesn't need to be able to decode the image itself, because that's done on our end in the browser, and that shouldn't be a problem for anyone who's updated their browser in the past 5-10 years.
Regarding DRM on images, one thing I've found that many websites do, either intentionally or otherwise, to stop people from being able to save images is to hide the image itself underneath a transparent layer so right clicking doesn't let you save the image. There is a workaround although it can be a bit of a pain in the backside, in Chrome, right click on the image and click "inspect", and using that function you can break the page down and find the url to the actual image.
