this post was submitted on 05 Jul 2023
210 points (100.0% liked)

/kbin meta

2 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
 

I tried looking around for a changelog but I couldn't find one anywhere (let me know if you know where it is, I know you can look at the commits/merged PRs on Codeberg but there's a lot to dig through).

Here's some of the changes I've noticed:

  • Profile picture next to username in top right
  • Comments can now be sorted by "top"
  • Larger image preview when uploading an image
  • Magazine stats are now localized (yay!!!)
  • kbin logo instead of stormtrooper in the "Create your own instance" box
  • Vote colors are brighter on dark mode
  • New theme: Tokyo Night

This is just what I've seen after using the site for a bit after the update, let me know if there's anything I've missed!

Edit: I just noticed that you can filter posts by language now, that's huge!

you are viewing a single comment's thread
view the rest of the comments
[–] ReiWasHere@kbin.social 2 points 1 year ago (1 children)

same for me, seems the migration is not complete or a server is down..
OR some images have no longer found their way home~

[–] melroy@kbin.melroy.org 0 points 1 year ago (1 children)

My guess is Fastly cache issues.

[–] ReiWasHere@kbin.social 1 points 1 year ago (1 children)

well i don't completely know what u mean.
if i opened images in a new tab it was a error 404, the image could not be found (browser dev tools also said so), so idk if it had something to do with the cache (but cache was also one of my 1st thoughts)~

but i also could be wrong :D

[–] melroy@kbin.melroy.org 1 points 1 year ago

It's not a cache issue at your side. It was a configuration issue at kbin.social with Fastly image cache. Causing those 404's. It's now been resolved.