updated akkoma-fe here

if the three column view broke for you, go into settings, set this option to something else then change it back

ah it's not persistent for some reason, you have to do this every time

gonna report this bug

https://akkoma.dev/AkkomaGang/akkoma-fe/issues/404

@mikoto hehe issue 404 how fitting indeed

huh, it seems to fix itself when I nuke the IndexedDB storage in my browser

@mikoto@akko.wtf unrelated, I was half expecting an actual "not found" error over there

Seems like it breaks again when I mess with the columns setting.

Wonder if there's a way to make a "debug" build of akkoma-fe with all symbol names kept from the source

more testing shows that it will reappear when your browser window size changes after loading

Also noticing this error in console, though I’m unusre if this is related to this problem

Error: Failed to connect to server, try again
    loginUser users.js:709
    promise callback*3561/loginUser/< users.js:705
    loginUser users.js:630
    v vuex.esm-bundler.js:322
    dispatch vuex.esm-bundler.js:1055
    dispatch vuex.esm-bundler.js:937
    e after_store.js:355
    f runtime.js:64
    t runtime.js:299
    k runtime.js:124
    Babel 4
    e after_store.js:361
    e after_store.js:352
    f runtime.js:64
    t runtime.js:299
    k runtime.js:124
    Babel 4
    mg after_store.js:351
    e after_store.js:395
    f runtime.js:64
    t runtime.js:299
    k runtime.js:124
    Babel 6
    hg after_store.js:364
    e main.js:113
    f runtime.js:64
    t runtime.js:299
    k runtime.js:124
    Babel 6
    3561 main.js:56
    Webpack 5
after_store.js:357:16

@mikoto The real workaround is disabling “Receive posts and notifications real-time”
(why? idk yet)

@Oneric interesting

@mikoto issue was fixed

@Oneric ok, i'll update in a bit

@Oneric yup, it's working