• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • I like how easy Shiori is to install and the UI is much more responsive than Wallabag (could be a config/install issue) but it does have some annoyances too:

    • No mobile app (I think there is an abandoned third party client though)
    • Session expires frequently in the Firefox extension, requiring frequently going into extension settings
    • No koreader support for e-readers etc

    But it is actively developed and it’s the most promising alternative to Wallabag in my view.












  • Personally I use Snapcast as an endpoint, plain MPD for local files, and navidrome for remote access to my library.

    That’s where I’ve been heading too. The snapcast client has been a bit unreliable for me on my desktop though (choppy and stuttering) but it’s great in its unix-like flexibility and I’m sure it will continue to get better.

    Honestly, I hope that mobile connections in my country are one day: fast enough, cheap enough, and reliable enough that I could just use snapcast remotely and get truly seamless self-hosted streaming but that’s still a long way away I suspect.





  • I don’t see anyway around XWayland. You could run X in a separate VT but that wouldn’t be “in” Wayland and while you wouldn’t need to login, you’d still need to spawn it.

    You could try running RPCS3 in gamescope as a workaround, but it’s probably Nvidia + Wayland that’s the issue.

    EDIT: Have you tried running RPCS3 with both Wayland and XWayland? RPCS3 supports native Wayland as well so if it’s an XWayland only issue then that should fix it. Conversely if native Wayland is actually what is breaking it you could try:

    QT_QPA_PLATFORM=xcb rpcs3
    

    which would force XWayland. Presumably it’s QT_QPA_PLATFORM=wayland for wayland support, although it’s the default on my system.