Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

@ace@lemmy.ananace.dev avatar

ace

@ace@lemmy.ananace.dev

Just another Swedish programming sysadmin person.
Coffee is always the answer.

And beware my spaghet.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

ace ,
@ace@lemmy.ananace.dev avatar

Well, one part of it is that Flatpak pulls data over the network, and sometimes data sent over a network doesn't arrive in the exact same shape as when it left the original system, which results in that same data being sent in multiple copies - until one manages to arrive correctly.

ace ,
@ace@lemmy.ananace.dev avatar

What is truly bloated is their network-install images, starting with a 14MB kernel and 65MB initrd, which then proceeds to pull a 2.5GB image which they unpack into RAM to run the install.

This is especially egregious when running thin VMs for lots of things, since you now require them to have at least 4GB of RAM simply to be able to launch the installer at all.

Compare this to regular Debian, which uses an 8MB kernel and a 40MB initrd for the entire installer.
Or some larger like AlmaLinux, which has a 13MB kernel and a 98MB initrd, and which also pulls a 900MB image for the installer. (Which does mean a 2GB RAM minimum, but is still almost a third of the size of Ubuntu)

ace ,
@ace@lemmy.ananace.dev avatar

We're mirroring the images internally, not just because their mirrors suck and would almost double the total install time when using them, but also because they only host the images for the very latest patch version - and they've multiple times made major version changes which have broken the installer between patches in 22.04 alone.

ace ,
@ace@lemmy.ananace.dev avatar

If you're going to post release notes for random selfhostable projects on GitHub, could you at least add the GitHub About text for the project - or the synopsis from the readme - into the post.

ace ,
@ace@lemmy.ananace.dev avatar

I've been hoping to find a non-PHP alternative to Nextcloud for a while, but unfortunately I've yet to find one which supports my base requirements for the file storage.

Due to some quirks with my setup, my backing storage consists of a mix of local folders, S3 buckets, SMB/SFTP mounts (with user credential login), and even an external WebDav server.
Nextcloud does manage such a thing phenomenally, while all the alternatives I've tested (including a Radicale backed by rclone mounts) tend to fall completely to pieces as soon as more than one storage backend ends up getting involved, especially when some of said backends need to be accessed with user-specific credentials.

ace ,
@ace@lemmy.ananace.dev avatar

I've been looking at the rewrite of Owncloud, but unfortunately I really do need either SMB or SFTP for one of the most critical storage mounts in my setup.
I don't particularly feel like giving Owncloud a win either, they've not been behaving in a particularly friendly manner for the community, and their track record with open core isn't particularly good, so I really don't want to end up with a decent product that then steadily mutilates itself to try and squeeze money out of me.

The Owncloud team actually had a stand at FOSDEM a couple of years back, right across from the Nextcloud team, and they really didn't give me much confidence in the project after chatting with them. I've since heard that they're apparently not going to be allowed to return again either, due to how poorly they handled it.

ace ,
@ace@lemmy.ananace.dev avatar

Well, there are people running Linux in all manner of ways, like VRChat shaders.

FEP-61cf: The OpenWebAuth Protocol (socialhub.activitypub.rocks)

This is the proposed FEP-61cf: The OpenWebAuth Protocol. OpenWebAuth is the “single sign-on” mechanism used by Hubzilla, (streams) and other related projects. It allows a browser-based user to log in to services across the Fediverse using a single identity. Once logged in, they can be recognised by other...

ace ,
@ace@lemmy.ananace.dev avatar

This looks really odd in relation to other fediverse software; Why /magic and required to be on the root of the domain? Why hard-require routing the domain part of the user ID when .well-known/webfinger exists? Why is there a X-Open-Web-Auth header which the spec only describes as "its purpose is unclear from the code"?
So many questions.

I definitely like the idea of distributed sign-in, Solid did a decent work of that many years ago after all. This particular proposal just looks rather odd.

ace ,
@ace@lemmy.ananace.dev avatar

Let me tell you about Bumblebee and their issue , though that one's even worse seeing as installing system packages are done as root.

(Their install/update commands included rm -rf /usr /lib/nvidia-current/xorg/xorg)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • incremental_games
  • meta
  • All magazines