This has not been my experience, at least on a 4G device. My internet/data still work fine on a 5 year old device.

As an owner of a 4a, I can tell you with confidence that my device has not received an update in any form for many, many months now. It is effectively unsupported, and certainly is insecure in comparison to a Pixel 6 or newer.

The GrapheneOS developers themselves have stated in their forum that they will no longer provide extended support beyond the Pixel 5a, and that the extended support it has is already effectively insecure:

You should already be treating it as if it’s not receiving updates anymore, since that’s largely the case already.

Providing extended support doesn’t fit with the way we do things at all and is ending after the Pixel 5a. It’s a temporary compromise for harm reduction through existing users at least getting some of the patches despite not moving to a secure device. When this topic comes up in this way, it hints to us that we may be doing more harm than good through people continuing to use an insecure devices. We’ll certainly stop doing it with the 5 and 7 year support devices.

A day ago, a GrapheneOS dev said of the Pixel 4a:

It’s unsafe to continue using the Pixel 4a. It lacks basic security updates. Pixel 4a was launched August 2020 so it’s at the 5 year point. It was a budget device, not a flagship. It was launched with 3 years of support, unlike 8th/9th gen Pixels with 7 years of support from launch or the prior 6th/7th gen Pixels with 5 years of support from launch.

So for the Pixel 4, it effectively received about an extra year and half of tenuous support. The Pixel 5 will receive a few more months of tenuous extended support, then there will be no extended support for any future devices, meaning users will have to upgrade at the end of Google’s official support cycle for each device.

From the link:

GrapheneOS aims to provide harm reduction releases for devices which only have a minimum of 3 years support. Extended support updates at minimum will be done until the next Android version.

Emphasis mine. That quote does not imply they will provide an additional 3 years of support, only that they will offer the harm reduction updates from the end of official OEM support until the next version of Android is released.

I have personal experience with this, as my quite old Pixel 4a received harm-reduction updates from GrapheneOS for an additional few months into 2024 until the next version of Android was released, but that did not result in years of support. It is now completely unsupported, and has a warning on every bootup that says as much.

Further along they then say:

It is likely that we will make a decision around harm reduction releases for other devices with longer lifetimes in Q4 2024.

This implies they may actually stop doing post-support harm reduction updates for the newer devices that have longer support lifetimes from Google.

There’s nothing in that link to indicate 15 years. OEM support means Google’s support, not graphene’s. GrapheneOS does usually offer a few harm reduction releases beyond the official support timeline, but that’s a few months of extra time, not years.

GrapheneOS supports a phone model for as long as Google officially does. You can see the support lifetime of each model here: https://endoflife.date/pixel

If you want to keep an updated phone constantly, you’d have to upgrade every 7 years.

I try to donate to projects I use the most.

• Mint/Debian
• Krita
• KDE
• Archive.org

If I had time to redo it, I do think that revised order would be more ideal.

I would be pretty surprised if the current order will render it completely ineffectual at informing people of those concepts, and any who do flip it over and read the poorly named step 3 will find that it recommends building community for a general strike to be successful.

Clicking on the find a branch button brings you to a zoomed out map showing chapters around the globe, but I get what you mean where the preview is zoomed in on the US by default :p

That’s when the UAW’s (a large union) contract ends, so the plan is for all unions to plan the ends of their contracts for the same date.

It is admittedly a long time to wait, but due to how little of the US workforce is unionized, I assume it’s to give time to build up more unions and gain momentum?

You can break that view of themselves through community efforts - like gardens, allotments, etc

That’s precisely what the second page mentions, as well as information on how to find a local Food Not Bombs chapter. These topics are also discussed often on Slrpnk.net, which I encourage readers to take a look at and join, in the hopes of exposing them to more in-depth discussion of those topics and people who they can talk to about it.

The people who are already open to unions are already in them.

Again, in my personal experience in my area, I have met an astonishing amount of people who genuinely have no concept of what a union or general strike are, so for them, the lack of knowledge is most certainly a big barrier.

Ah, I realize now that, at least on voyager, cross posts don’t seem to show the post body contents.

If you click through, you’ll be able to see the second page (that is supposed to be on the reverse side) that briefly covers community building as well.

I have the general strike as step two since it made sense to explain what is immediately after mentioning it, and how it goes hand in hand with unionizing.

At least in my area both unions and a general strike are completely unknown concepts to most people I mention it to, so I wanted it to be clear what they are, though I wrote it while fairly sleep deprived, so I’m sure it could’ve been done better.

Ultimately this flyer is intended to just get people started down a good right path. I could only fit so much without it likely becoming overwhelming and not read, and still fitting on a double sided page.

One way to explain this is “double system theory”, namely the idea that a successful transition between two systems (any kind of system, not just social or political systems) happens only if the dismantling of the old happens in sync with the growth of the new and this growth can fulfill the needs of its participants better than the old.

That sounds fairly similar to Dual Power/Counter Power

I really, really like the logo you have for it. It’s snazzy AF :)

Hm, I thought he mentioned it in his 6.4 juicy video, but I can’t find it either. Apologies, I must have confused it with something else.

I did manage to find this rounded corners proposal, and unfortunately it doesn’t look like it’ll be in kwin anytime soon.

I think native rounded corners were introduced in one of the latest versions, Nicco Loves Linux did a video on it, I believe.

Older desktops can have a somewhat hefty idle power draw due to the overall system consumption contributing more than expected, such as the southbridge. According to this old review of the i7-2600k, the system idles at 74w, which at $0.12 per KWh, would cost you roughly $77 per year. Though you might want to confirm that with a Kill-a-watt meter if you can (libraries sometimes lend them out), since I’m pretty sure that total system power chart includes a discrete GPU, so the real number for a GPU-less system is probably around 40 or 50w at idle.

If that is accurate, you could potentially replace your i7-2600 with a used Dell Wyse 5070 thin client from ebay for about $40 (in the US), and that idles at 5w, which would only cost you $5 a year at the same rate.

Older thin clients and laptops tend to have much better idle power draws compared to desktops. For other people reading this, if you’re using a desktop for a low-power use case, it’s probably worth finding out what its idle power consumption is and doing the calculation to determine if it’d be worth replacing it with a more efficient used thin-client or office mini-pc.

If you’d be interested in a tracker-like DAW, Renoise has a native Linux version.

For more traditional DAWS, Bitwig and Reaper are the two best Linux native options. Reaper is quite cheap, and also offers a trial version that just nags you like winrar.

I think you’re right, and they may be exaggerating a bit. From what I can tell, this would be almost act like a 4th setting between power-save and on-demand mode, so you still get most of the benefits of power-save mode, but without the need to switch back to on-demand when you do something intense.

also @MangoPenguin@lemmy.blahaj.zone.

I suspect a VM would introduce latency (big no no for music production), and I can’t imagine getting ASIO working would be easy (though I’ve never tried it).

According to WineHQ, Ableton’s compatibility with wine isn’t stellar. FL Studio works quite well in it, but switching DAWs can be a pretty major undertaking.

For Linux native DAWs, Reaper and Bitwig are the two best options. Reaper is the most affordable at 60 bucks, with an infinite free trial.