anyone else? rolling back to previous flatpak solves it.

$ flatpak remote-info --log flathub org.jellyfin.JellyfinDesktop

Jellyfin Desktop - Jellyfin desktop client

        ID: org.jellyfin.JellyfinDesktop
       Ref: app/org.jellyfin.JellyfinDesktop/x86_64/stable
      Arch: x86_64
    Branch: stable
   Version: 2.0.0
   License: GPL-2.0
Collection: org.flathub.Stable

Download Size: 139.7 MB Installed Size: 323.2 MB Runtime: org.kde.Platform/x86_64/6.11 Sdk: org.kde.Sdk/x86_64/6.11

    Commit: a6d784a0c6db00f3d260e08c026a30072c2ec2ad7e902e8805033809296ddcb0
    Parent: 101468e6a77cf4cc4343f3069933025a86ebaf765eb662644dc6536003831c1d
   Subject: Merge pull request #18 from Justinzobel/runtime611 (03154a53a1a8)
      Date: 2026-10-30 22:50:12 +0000
   History: 

    Commit: 101468e6a77cf4cc4343f3069933025a86ebaf765eb662644dc6536003831c1d
   Subject: Add org.jellyfin.JellyfinDesktop (23eebe530cc6)
      Date: 2025-12-27 13:09:06 +0000

    Commit: a00879190e5e977f1185537e67426773db3944bddffc01ff9c0aaa9e7ab7e741
   Subject: Add org.jellyfin.JellyfinDesktop (23eebe530cc6)
      Date: 2025-12-27 13:09:06 +0000

the Oct 30 one doesn't play them, the 27 one does. also whole lotta fucked up UI glitches, doesn't respect the tv and desktop launch flags, some major changes afoot.

 

didn't see it mentioned here, so a brief YSK.

stefano marinelli is working on #littleFedi, a self-hosted, single-binary activitypub/fediverse peer that hosts a mastodon-like instance with, in my mind, three killer features.

one, the thing can run on your premises completely, no need for paying for a VPS, domain name, nothing, bypasses NAT/CGNAT, encrypted comms to other instances by way of lighthouses that do the initial intros.

dos, the thing runs on something as light as a Pi zero 2W, with a miniscule memory footprint and immense CPU optimizations due to running on the weakest hardware there is (also running off SD storage).

finally, a blog-like view of your long-format tweets/toots/posts, naturally with replies appearing as comments.

original post introing the thing: https://littleone.littlefedi.social/@stefano/4252ae6f-b949-42f8-a021-fd2b698f8b37

no code available atm (coming soon) same goes for binaries. the first instance is at https://littleone.littlefedi.social/ if you want an invite code to check things out (the settings page's got a lot of cool stuff), hit up stefano.

I am beyond stoked, this clears the two biggest hurdles for selfhosting your shit - the VPS/domain expense and hassle, and the hardware requirements for running it.

edit: missed that the website is up, explaining everything way better: https://littlefedi.org/

 

in its first iteration, it strips all AI shit, doesn't just disable it; the hero went through the source tree and patched it by hand!

it differs from LibreWolf and friends as there's an intention to hard-fork the thing (LW should be based on basebrowser) and let the abomination that is the mozilla shell-game-corp of today behind, thus returning to the original idea behind creating mozilla, best described by the dude who gave us the thing:

In my humble but correct opinion, Mozilla should be doing two things and two things only:

  1. Building THE reference implementation web browser, and
  2. Being a jugular-snapping attack dog on standards committees.
  3. There is no 3.

mastodon thread: https://mastodon.social/@sarahjamielewis/116994970688711387

the patch repo: https://codeberg.org/basebrowserproject/organization

firefox repo: https://github.com/mozilla-firefox/firefox

build instructions: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html

the only thing missing's how to apply the patch. it's as simple as going to the firefox source folder and applying the patch file with:

patch -p1 < the.patch

and then proceed with ./mach build.

this was my first time building firefox from source and it wasn't half as bad; about 30ish minutes on an i7-870 in the background without any excessive load that woulda made the system unusable.

 

In case you were one of the lucky ones able to snag a free account in the olden days, the terms have changed. Instead of 4 CPU and 24 RAM that you were free to whack up amongst 1-4 VPS, now you got 2 CPU and 12 GB RAM, so either one dual-core VPS or two single-core. If you keep using the old setup beyond a certain date (can't be bothered to look up when that is) you'll get billed; at reasonable rates, I'm sure.

If I'm reading this correctly, the block volume storage allotment hasn't changed, but their whole setup is hella confusing, so might be off on that.

Was really a matter of days when they was gonna axe the thing, they fired half a planet's worth of workers, I'm amazed they left even this much.

edit: I'm behind the times, this was reported more than a month ago: https://linuxiac.com/oracle-quietly-cuts-free-tier-ampere-a1-resources-in-half/

 

was away from django development for close to a decade, decided to jump in for a smallish project. don't wanna use my preferred IDE from way back when (pycharm) and am trying to use vscodium.

with the standard python and django extensions, the autocompletion/suggestion is... uh, lacking. what else do I need? a search in the marketplace nets tons of suggestions, don't know which are superfluous, overlapping, deprecated...

 

hated on the thing since I first spotted it and dismissed it, never to think about it again - doing everything wrong and then adding the shittiest of solutions, who's gonna fall for that, right? but that thing is gaining and this post and recent threads just make me irrationally angry.

oh, the thing is also vibecoded. if you had any reservations about letting this idiocy loose on your data, there's a relief, huh? head bozo detects ever-so-subtle AGI whilst slop-fondling and easily "verifies" 30K LoC that was shat out. stomach-churning shit.

not to mention, said bozo is doubling down on his fash idiocies. I wish I was making half of this up.