Sure, but the Australian government's definition of an age-restricted social media platform doesn't mention advertising or algorithms at all. Technically, their definition also covers algorithm-free social media like Mastodon, which I'd argue isn't nearly as harmful.

The framing of social media as something that's inherently bad no matter how you do it is a framing that helps social media giants like YouTube, Instagram and Facebook to continue to "do it" in a way that harms people. I'm sure they love the idea that the ills of social media can be solved by banning their least profitable users while doing nothing to regulate what they do with the others. They're probably thrilled that their healthier algorithm-free competitors haven't even entered the conversation. They want to be the tobacco companies of the future, because making addictive things for adults is incredibly profitable.

All modern Chromebooks can be put into developer mode without opening the case, which gives you root access.

I think the fact that people bring up things that the Anubis mascot isn't when talking about Anubis is more telling of their own harmful (and potentially racist) biases against Japanese-styled media than it is about the idea of having anime-styled mascots for free software projects.

- Rolling release, so you don't have to do a major upgrade twice a year - which would otherwise be much more often than Windows.

- Latest kernel and graphics drivers, so it works with newly released hardware with the best performance.

- Steam, NVIDIA drivers, H.264/H.265 codecs, Gamescope, GameMode, MangoHud, etc. all in the default repos - a huge boon for new Linux users compared to having them in an external repo like RPM Fusion or having to install them manually, which can otherwise cause confusing dependency problems over the life of the installation.

- Nothing unusual about it that would be confusing or cause compatibility problems. It's just a normal mutable binary distro with a normal package manager, upstream packages, glibc and systemd.

The biggest issue is the lack of an official graphical installer, but while the install process is intimidating, it's not very difficult for people who are patient, can follow detailed instructions, and have a vague idea of what a partition and a bootloader is.

The problem is a social not a technical one. It doesn't matter how good AT Protocol is at account migration. The vast majority of AT Protocol users think of themselves as Bluesky users and don't even know what the AT Protocol is. If the official Bluesky clients move away from the AT Protocol, the majority of users are moving with Bluesky.

For all the UX concerns people have with Mastodon/ActivityPub, at least they make it obvious that different users are hosted on different instances, and no one instance has more to gain than it does to lose by defederating.

Though having said that, in the past year I've replaced ChromeOS with desktop Linux (postmarketOS) and I love it even more now. 4GB of RAM was a bit slim for running everything in micro-VMs for "security," which is what ChromeOS does. I've had no trouble with battery life or Android emulation (Waydroid) since switching.

[1]: https://github.com/hyprwm/Hyprland/blob/e999ad664da9/src/plu... [2]: https://wiki.hypr.land/Plugins/Development/Advanced/ [3]: https://github.com/hyprwm/Hyprland/blob/a5a648091760/src/plu...

Human skill was already democratized in that anyone can obtain skills, and businesses have to be good at managing those people if they want to profit from those skills - ultimately the power is in the hands of the skilled individuals. But in the hypothetical AI future, where AI has superhuman skill, and human skills are devalued, it seems like there will be a more cynical, direct conversion between the money you can spend and the quality of your output, and local/self-hosted AI will never be able to compete with the resources of big business.

> All you need to do is omit the Enterprise feature flag during compilation, and what you get is a 100% AGPL-3.0 build.

Maybe I'm misunderstanding, but my interpretation of this issue[1] is that Stalwart contains AGPLv3 licensed functions that call into the SEL licensed `has_tenant_access` function, among others, and that the affected functions are not conditionally compiled out of the AGPLv3 binaries. @afontenot says on that issue that they don't believe it's "possible to use Stalwart under the AGPL at present." Are they wrong and can that issue be closed?

I am also concerned about the webadmin. A free software program that downloads proprietary code on first start isn't free software in practice, and since there aren't two separate SEL and AGPLv3 licensed builds of the webadmin on GitHub, that must be the case.

> So while the optics of this situation may look rough from the outside, I promise it’s not some “open source in name only” kind of thing. It’s just one of those painful balance acts between building features, maintaining packages, and paying the bills.

I get it, but it's disappointing that AGPLv3 compliance is so low in the list of priorities that this licensing issue has been known about but not solved in 8 months, all while receiving grants intended for free software projects. That balancing act must have included the consideration that the free software community is regularly burnt by rug-pulls (Redis) and trust isn't easily won back once its lost.

> And hey, if you're heading back to Maddy, no hard feelings. But the door’s always open if you want to give Stalwart another shot down the road.

I might. Sorry if I've been harsh, but it's only because Stalwart is a very cool project. A FOSS all-in-one mail server written in a safe language is exactly what email needs, and since learning about it, I've been worried that it's too good to be true. Please don't let it be. I don't think it will gain the momentum to replace Postfix if it can't be packaged in Linux distros due to licensing issues.

[1]: https://github.com/stalwartlabs/stalwart/issues/783

These issues, which would be showstoppers for a real free software project, and pretty easy to fix if you were the rightsholder of the code, were promised to be fixed "in a few weeks" in September last year, and "in a few months" in January this year, however they're still not fixed, which means I can't upgrade - not that I probably want to anymore. I truly believe in free software, so I find the idea of using "open source" as an empty marketing bullet-point for at least eight months to be fairly distasteful. Might be time to switch to Maddy.

[1]: https://gitlab.archlinux.org/archlinux/packaging/packages/st... [2]: https://github.com/stalwartlabs/stalwart/issues/783 [3]: https://gitlab.archlinux.org/archlinux/packaging/packages/st...

Microsoft made their own Mesa builds for this once, but they don't appear to be updating them? https://apps.microsoft.com/detail/9nqpsl29bfff