The kernel update issue on Android is going to be exactly the same for PostmarketOS and for the exact same reason: proprietary firmwares and/or drivers.

That is not the case, as PostmarketOS uses community made open-source drivers, even for the GPU, and all devices that it supports uses the mainline kernel, as all of the drivers they develop are upstreamed to mainline, instead of it being a proprietary driver that is locked to a specific kernel.

The open-source drivers aren’t currently as polished as the proprietary ones, but as we’ve seen the open-source AMD driver for desktop, it can become the best option with community effort and funding.

and now you need to maintain both a GNU/systemd/Linux AND a compatibility layer with Android

The point of adopting Postmarket is that they could then rely on the open-source community to help with maintaining most of of the components, much like how Linux desktop or Linux Server works currently. Waydroid is developed by its own team, so they wouldn’t need to fork that and maintain it to have access to Android apps (though they could help contribute to it if they wanted to).

From a security and privacy standpoint, Linux was never designed to handle hostile apps designed to aquire as much data as possible. Android has a sandboxing system

Android is Linux at the core, yet it was able to be hardened, which shows that PostmarketOS could be similarly hardened if such features were adequately funded and developed by the EU. Linux already has Wayland, which is a huge step forward for security, and Flatpak packages already have Android-like permissions built in (though they would need to modify how those work by default to increase security).

I’m not entirely sure if that would be better than just adopting PostmarketOS, since forking AOSP would mean maintaining a fork of that entire ecosystem, and I’m unsure how they would deal with all the phone manufacturers dropping support for phones rather quickly, or using outdated kernels to access GPU and hardware drivers for said phones after the manufacturer drops support.

Investing in PostmarketOS instead would bring with it much less stuff to fork, along with access to the mainline linux kernel (instead of outdated Android ones) that use open-source GPU drivers that can be effectively maintained, and it can support Android compatibility with a compatibility layer, Waydroid.

A polished PostmarketOS ecosystem only seems to offer advantages compared to a forked AOSP, so if they’re choosing which to invest in, Postmarket seems like the clear winner.

Graphene is good, though it’s still pretty reliant upon Google not making life even harder for them, which it has been doing consistently.

A safer long-term option that is detached from Google’s whims entirely is PostmarketOS, which isn’t based on Android at all, but is instead a project based on Linux directly.

They apparently had a pretty big negative stigma in the audio production world as just that; a toy for un-serious amateurs, or only useful for making beats or loops, instead of as a more general DAW for other genres.

A DAW will want hardware access and wine hardware drivers don’t really exist

I’ve read in the past that some DAWs like FL Studio run quite well in Wine, but I’ve never tried it myself. I agree that it’s best just to use a native Linux DAW.

GNU Taler would be a good global solution. It’s an anonymous (for the buyer) digital cash. Do far its been adopted by some swiss banks.

There’s more info on it over at !money@slrpnk.net

90% of youtube thumbnails have a face in them, usually of an exaggerated emotion, and that goes for both male and female youtubers. Many youtubers have confirmed time and time again that the algorithm favors faces by a pretty wide margin, and thus most play that game.

I’m not a fan of it, I wish they didn’t or the algorithm was changed to not favor it, but I understand why they do it. Though I don’t think it’s particularly gendered as your image claims.

Huh, so it is.

Something strange I noticed when viewing it from there is our slrpnk comments aren’t federating to kbin.earth, despite hosting the community it was posted to. The Banjo’s and Riwo’s is, though.

I think you forgot to add the link to the video, OP.

20 years ago Linux couldn’t play 95% of Windows games seamlessly without tinkering, couldn’t easily produce music without a lot of tinkering and few DAWs, couldn’t effectively video edit (Kdenlive is good now, and Davimci Resolve now supports Linux), and it had spotty WiFi card support.

All of those are now no longer a problem, and make transitioning to it far easier for a much wider swath of people.

This video does a great job explaining the practical usefulness of the ‘Collective dreaming’ that Solarpunk provides. In short, it gives us a collective goal to aim toward, which then prompts us to figure out what the best way of achieving that goal is with the tools at hand.

In that way, I would put forward that Solarpunk provides a useful framework to address the issues we face today. At its core it encourages decentralized grassroots community building to address problems (the ‘punk’ part), which is generally more effective than spinning our collective wheels trying to reform political machinery that is fully corporate captured, and I would consider a form of prefiguration.

And the ‘Solar’ part encourages adopting practical and ecological technology to address the issue of our planet becoming uninhabitable from our current political and economic models; adopting renewable energy (which often scales down really well, helping out the decentralized part), viewing a healthy ecology as essential infrastructure to a prosperous existence, stopping consumerism with Degrowth, etc.

In practice, Solarpunk basically lets us collectively see a plausible outcome if we embraced Eco-Anarchism (basically combining what Catalonia was able to achieve in the 30’s, along with a distinct focus on restoring our planet’s ecosystems).

That it isn’t some impractical sci-fi concept needing yet to be invented tech, but instead an achievable goal even with our existing technology, is a very encouraging and motivating concept, IMO.

This is a video specific community. If you do not wish to watch videos, I would suggest blocking video communities from showing up in your feed.

If you’d rather read an article about the subject in the video, you are free to search for one and post it here in the comments for others, if you’d like.

The name of the community is listed next to a post, even from ‘All’

Videos shouldn’t be posted in video specific communities?

Ah, in that case that sounds like a bug, since Movim should fully support group audio and video calls on Firefox.

If you can, it’d be extremely helpful to report that on the movim github, where the developer can help get to the bottom of it and prevent that from happening to anyone else in the future :)

The GPL would only let them close source their own code, but to close source any code that was contributed by others, they would need to explicitly ask permission from each and every user that added to the codebase, which generally isn’t feasible.

That prevents the original creators from being able to benefit from free and rapid community development and then close sourcing it all later. To effectively close source the app, they would need to re-implement every contribution themselves.

They would only be able to do what you describe with the GPL if they also required every contributor to sign a CLA which explicitly gives up ownership of the contribution to the project owners.

The MIT license allows anyone (including the original creators) to close source the app without needing permission from anyone.

Matrix has a lot of problems, some of them inherent to its design, including spreading metadata of encrypted messages to any server that participates in a chat room (this metadata includes the time the message was sent, size, sender and recipients of messages).

I’m not a fan of it, despite it being federated.

Not personally a fan of it since it’s not federated (and has no plans to implement federation) meaning its one centralized point of failure and one centralized point for governments to subpoena. It has no plans to implement any form of encryption (Movim has solid encryption, and Fluxer plans to implement encrypted DMs in the future).

Also very concerning to me is that it uses the MIT license, which allows for the company to do a rug-pull and close-source the code in the future so they can enshittify it. Only the GPL license ensures that it remains open-source and in the community’s hands forever.

I found with Movim that you need to ensure that both you and the other person have each other added as contacts (and both parties each accepted those contact requests) for the call button to show up, just being in a chat with each other isn’t enough (and that is quite painful UX, since there’s no information that explains that that must be done).

I think it won’t show a call button if it doesn’t detect a microphone either.

In the case of our communication apps, they do have to be open-source and GPL licensed, otherwise we’re crossing our fingers that they’ll respect privacy, and kicking the can down the road until it enshittifies.

Being able to be self-hosted and federated are also essential for long-term stability and preventing centralization.

The two best discord alternatives we have available to us that meet those requirements are Movim and Fluxer. I would not consider any other options.