You're hitting a problem I have with Ublue as well. I wanted to experiment with immutable distros last year, but Ublue provided extremely little information on how their different flavors actually differed under the hood. I ended up having to search through their forums for like an hour to find snippets of how their different when some people asked, but it was never comprehensive.
From what I recall, Bazzite had a few kernel optimizations for gaming, and received updates at a faster frequency than Bluefin, with one of the devs saying that Bazzite would be more likely to experience regressions due to it being more bleeding edge.
Looking at Bazzite's front page now, they actually seem to be doing a better job of mentioning what's unique about it than when I last tried it. But Bluefin and Aurora are still ambiguous.
If it was able to boot the Live USB to install it, I figure that means the kernel is new enough to actually run the laptop properly. I can only guess something in the installer itself was messing up somehow? Or perhaps it wasn't making an entry in the boot table? That's an odd one for sure.
Crazy to see that Las Vegas is essentially surrounded by easily stirred up naturally occuring asbestos in the dust, and Nevada actively suppresses that information.
Like holy shit that's huge. Being outside in that area is exposing yourself to a massive lung cancer risk.
Very surprising and welcome update: The Fluxer dev responded to a similar thread on reddit that they will remove the CLA before opening the repo to contributions due to how successful the funding campaign has been. Fluxer is now back on the table! :)
Though I may still open a Movim community as well, just in case.
(alt of Prodigalfrog here btw, I can't respond in this thread with my main account, as Slrpnk was down for a few days and it's still catching up with lemmy.world).
If I were to mod a Movim comm, I'd probably create one on Slrpnk or a generic instance.
Probably a good idea to have one around at some point though!
And thanks for being onboard with getting the CLA dropped ^^
The best option is to push for the Fluxer dev to remove the CLA, so we can safely support him and the project. Otherwise, we can simply adopt a different piece of software that doesn't have a CLA. Funding the Movim dev, as an example, would help accelerate the development of the few missing Discord-like features. That would let us have our cake and eat it too.
Sticking with CLA software and hoping for the best is not a good long-term plan.
It's a calculated risk to support Fluxer with a CLA. It might work out down the road if the last GPL version is forked, but it could just as easily not work out.
This effects end-users just as much as it effects contributors.
The CLA essentially provides a lever that can be pulled at any time to convert Fluxer into a closed-source proprietary app no different from Discord, which also enables it to be sold to venture capital, providing all the same incentives to enshittify the the app that Discord had, such as collaborating with Palantir-like entities for profit.
That would easily put us right back into the same boat we're in right now. We would be absolute fools to knowingly walk into that trap when we're so desperate to leave the one we're already in.
Fluxer with a CLA is kicking the can down the road.
They can’t retroactively close-source the older versions released under AGPL, but if it ever required a community fork to continue the last release of the GPL version, it would be a massive burden to maintain it, and could cause federation to break as the codebase diverges over time, which would create a rift in the community. You’d also have to hope that average users care enough about the license to jump ship to the GPL (probably now not as full-featured) version, otherwise the GPL version risks not being able to get enough funding to continue, or enough users to convince the larger communities to move over.
As a somewhat similar real world example, the pixel-art program Aseprite once used a FLOSS license, but it switched to a proprietary license at some point. The last GPL version was forked by the community, but it never got much traction, and is now massively behind the closed source version in features and userbase.
It's a pretty huge potential liability down the road. We can ignore it for the sake of convenience, but it really could bite us in the ass. Now is the best time to avoid entrenching ourselves with it.
I also want to stress that if this issue gains momentum in the community, the dev might actually be willing to take it out. If we just go along with the flow, it will not be removed.
It currently has the ability to Chat/call 1 on 1, create public facing group chats, send images/videos/files in chat, perform group audio/video calls, and screenshare applications with audio (but currently requires a chromium based browser to share the audio). I believe that's most of Discord's functionality, it even looks like Discord. Once the spaces and audio rooms are implemented, it'll be virtually a complete clone, plus it's already federated and offers excellent encryption.
It is currently missing a couple features, such as channels with rooms, but the developer is actively implementing those, after which it would be pretty much 1:1 in functionality.
EDIT: The Fluxer dev has agreed to remove the CLA!
Just a heads up to anyone interested in Fluxer: there's a huge red flag; it has a contributor CLA that could allow it to change to a non-FLOSS license in the future. I was hopeful for it previously, but that kills it for me.
EDIT: The Fluxer dev has agreed to remove the CLA!
Just a heads up to anyone interested in Fluxer: I was just informed today of a huge red flag for Fluxer; it has a contributor CLA that could allow it to change to a non-FLOSS license in the future. I was hopeful for it previously, but that kills it for me.
Not a bad idea :)
You're hitting a problem I have with Ublue as well. I wanted to experiment with immutable distros last year, but Ublue provided extremely little information on how their different flavors actually differed under the hood. I ended up having to search through their forums for like an hour to find snippets of how their different when some people asked, but it was never comprehensive.
From what I recall, Bazzite had a few kernel optimizations for gaming, and received updates at a faster frequency than Bluefin, with one of the devs saying that Bazzite would be more likely to experience regressions due to it being more bleeding edge.
Looking at Bazzite's front page now, they actually seem to be doing a better job of mentioning what's unique about it than when I last tried it. But Bluefin and Aurora are still ambiguous.
It's always been based on stable, AFAIK.
If it was able to boot the Live USB to install it, I figure that means the kernel is new enough to actually run the laptop properly. I can only guess something in the installer itself was messing up somehow? Or perhaps it wasn't making an entry in the boot table? That's an odd one for sure.
Only Bluefin LTS is based on CentOS. Standard Bluefin is based on Fedora.
LMDE is not based on Sid, it's based on Debian Stable. LMDE 7 is currently based on Debian 13 Trixie. You sure you had the right ISO?
Many parts of Cinnamon were forked from Gnome 3 and Gnome 2 (Mate).
Many other parts of Cinnamon are made from scratch, but it is not wrong the say it's also a Gnome 3 fork in many ways.
An unexpected but welcome update, the Fluxer dev agreed to remove the CLA, which puts it back in the running.
Sure thing 👍
Crazy to see that Las Vegas is essentially surrounded by easily stirred up naturally occuring asbestos in the dust, and Nevada actively suppresses that information.
Like holy shit that's huge. Being outside in that area is exposing yourself to a massive lung cancer risk.
Very surprising and welcome update: The Fluxer dev responded to a similar thread on reddit that they will remove the CLA before opening the repo to contributions due to how successful the funding campaign has been. Fluxer is now back on the table! :)
Though I may still open a Movim community as well, just in case.
(alt of Prodigalfrog here btw, I can't respond in this thread with my main account, as Slrpnk was down for a few days and it's still catching up with lemmy.world).
If I were to mod a Movim comm, I'd probably create one on Slrpnk or a generic instance.
Probably a good idea to have one around at some point though!
And thanks for being onboard with getting the CLA dropped ^^
The best option is to push for the Fluxer dev to remove the CLA, so we can safely support him and the project. Otherwise, we can simply adopt a different piece of software that doesn't have a CLA. Funding the Movim dev, as an example, would help accelerate the development of the few missing Discord-like features. That would let us have our cake and eat it too.
Sticking with CLA software and hoping for the best is not a good long-term plan.
That's not a complete get 'out of jail free' card: https://lemmy.cafe/post/31748570/15981308
It's a calculated risk to support Fluxer with a CLA. It might work out down the road if the last GPL version is forked, but it could just as easily not work out.
This effects end-users just as much as it effects contributors.
The CLA essentially provides a lever that can be pulled at any time to convert Fluxer into a closed-source proprietary app no different from Discord, which also enables it to be sold to venture capital, providing all the same incentives to enshittify the the app that Discord had, such as collaborating with Palantir-like entities for profit.
That would easily put us right back into the same boat we're in right now. We would be absolute fools to knowingly walk into that trap when we're so desperate to leave the one we're already in.
Fluxer with a CLA is kicking the can down the road.
They can’t retroactively close-source the older versions released under AGPL, but if it ever required a community fork to continue the last release of the GPL version, it would be a massive burden to maintain it, and could cause federation to break as the codebase diverges over time, which would create a rift in the community. You’d also have to hope that average users care enough about the license to jump ship to the GPL (probably now not as full-featured) version, otherwise the GPL version risks not being able to get enough funding to continue, or enough users to convince the larger communities to move over.
As a somewhat similar real world example, the pixel-art program Aseprite once used a FLOSS license, but it switched to a proprietary license at some point. The last GPL version was forked by the community, but it never got much traction, and is now massively behind the closed source version in features and userbase.
It's a pretty huge potential liability down the road. We can ignore it for the sake of convenience, but it really could bite us in the ass. Now is the best time to avoid entrenching ourselves with it.
I also want to stress that if this issue gains momentum in the community, the dev might actually be willing to take it out. If we just go along with the flow, it will not be removed.
It currently has the ability to Chat/call 1 on 1, create public facing group chats, send images/videos/files in chat, perform group audio/video calls, and screenshare applications with audio (but currently requires a chromium based browser to share the audio). I believe that's most of Discord's functionality, it even looks like Discord. Once the spaces and audio rooms are implemented, it'll be virtually a complete clone, plus it's already federated and offers excellent encryption.
It is currently missing a couple features, such as channels with rooms, but the developer is actively implementing those, after which it would be pretty much 1:1 in functionality.
EDIT: The Fluxer dev has agreed to remove the CLA!
Just a heads up to anyone interested in Fluxer: there's a huge red flag; it has a contributor CLA that could allow it to change to a non-FLOSS license in the future. I was hopeful for it previously, but that kills it for me.
EDIT: The Fluxer dev has agreed to remove the CLA!
Just a heads up to anyone interested in Fluxer: I was just informed today of a huge red flag for Fluxer; it has a contributor CLA that could allow it to change to a non-FLOSS license in the future. I was hopeful for it previously, but that kills it for me.
Also @irelephant@lemmy.dbzer0.com