There are parts in the #Cricut Maker 3 that cannot be accessed without breaking plastic (red box) - like these screws (blue arrow) on the lid.

The iFixit article is not correct because it’s glued - it cannot just gently be pried off.

I am never purchasing a Cricut again. This is extremely anti-repair. #RightToRepair #enshittification

Reparatur-Shops werden gezwungen, defekte Galaxy-Geräte zu zerstören, wenn bereits Drittanbieter-Teile zur Reparatur verwendet wurden. Samsung verlangt in dem Fall die Weitergabe persönlicher Kundendaten und erhöht damit den Reparaturaufwand massiv.

notebookcheck.com/Samsung-zwin…

#samsung #righttorepair #reparatur

Samsung zwingt Reparatur-Shops zum Zerstören von Kunden-Smartphones, iFixit beendet Kooperation

Wer sein Samsung Galaxy-Gerät zu einem Reparatur-Shop bringt, könnte es in Einzelteilen zurück erhalten, denn Samsung zwingt Dienstleister unter bestimmten Voraussetzungen, Geräte zu zerlegen statt zu reparieren, und persönliche Daten des Kunden nach…

^{Hannes Brecher (Notebookcheck)}

#StopKillingGames.com aims to delegalize game publishers thanos-snapping games you've paid real money for when they feel like it. Exactly what Ubisoft recently did with The Crew.

MattKC has a great short video about it:
youtube.com/watch?v=fwcj_tIm44…

Now is the best chance for us to have governments make laws protecting games from systemic destruction!

Australians - HURRY!
2 weeks left for you to ACT!
Read details on StopKillingGames.com

#RightToRepair #RightToReplay #Gaming #Games

Game publishers want to end preservation. But we have a chance to stop them.

▶Help take action against publishers destroying your games: https://stopkillinggames.com/▶UK Petition: https://petition.parliament.uk/petitions/659071▶Austra...

^YouTube

Finally a Law for Right to repair and hopefully therefore in the future more sustainable and better repairable Products. 😃

FairPhone and ShiftPhone as Producer of Smartphones are already having this repairability in their Products long ago before that was made by Politics into a Law.
😉

#EU #RightToRepair #Law #FairPhone #ShiftPhone
@IzzyOnDroid

An EU-wide #RightToRepair has been adopted by the EU parliament with 584 votes in favour, 3 against and 14 abstentions. The directive now goes to the council and after it is officially published, member states have 24 months to implement it in national law.

And yes, smartphones are included. #ThanksEU

europarl.europa.eu/news/en/pre…

Android or iPhone — either Google or Apple delivers our messages — surely? You don't accept that?

Time I Learned: there are freedom-respecting phones.

People who do not want to depend on Google or have them control our devices are using android-compatible but not google-controlled phones, a.k.a. “degoogled phones”. We have been asking (ourselves) for several years if we can have google-free push notifications. Thanks to the developers of the UnifiedPush standard, the answer is now, “yes!”

But why?

You've probably heard of the Observer Effect. Partly influenced by hearing that someone is observing my blog from a social psychology angle relating to attitudes among the open source community, but also I was already thinking I should, I've decided to write more about why I write/build/care about the topics I choose. For a start I wrote a “Why Would I Care?” section for my latest post Google-Free Push Messaging for Google-Free Phones. Here, that section is published as an article on its own.

Why Would I Care?

Why would I care how my push notifications reach my phone? What difference does it make to me?

That's a good question. Inside a building that has a good heating, ventilation and air conditioning system, we don't notice the system, we just feel comfortable. With push notification delivery, part of the answer is the same: the system just does its job and our notifications come through. Whether the delivery channel is controlled by Google or by us or by someone else doesn't change that. The immediate, concrete result is the same. So it's not about wanting it to function differently; that's not why I care.

The difference it makes to me is about freedom, privacy, independence, self-agency. I am happy to have the choice to use any particular company's service, but I am not happy to be forced to use them, to have no choice, if I can't leave no matter how bad it gets. What if I don't like Google monitoring my notifications to know what I'm doing? What if I don't like to live in fear of offending them in some way and being cut off from their service and having no replacement option? What if I just don't want to condone their business model by using it, but I still want to be notified when I have messages?

Push notification delivery is one of the many invisible technical services that underpin our online communication systems. These kinds of services are implicitly considered to be part of the public infrastructure, something that we now assume is available to everyone.

When we allow ourselves to become dependent on any particular company's service, and yet do not regulate it as a public service provider, then we subject ourselves to the company's whims, priorities and values, which are different from ours. They will inevitably act against public interests.

Building publicly owned infrastructure based on open standards and freedom software is therefore essential to ensure the independent provision of services aligned with public needs and values.

I am one of the people who feels it is my place to use, promote and build non-proprietary public services, both for my own mental wellbeing and because I believe it is important for society.

It is the same reason why I support: open Ed-Tech, degoogled phones, #matrix, #fediverse, freedom software, open-source hardware, #rightToRepair.

Speaking as one of the people who prefer our devices not to be controlled by and dependent on Google:

What do we want? UnifiedPush!

When do we want it? Now!

I would love to work on any freedom tech project bringing UnifiedPush to a wider audience.

See my other posts tagged... #unifiedPush #degoogled #awesomeFOSS

Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @julian​@wrily.foad.me.uk · use the Cactus Comments box above · matrix me · Fedi follow me · email me · julian.foad.me.ukDonate: via LiberapayAll posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise

awesomeFOSS — julian

awesomeFOSS posts on julian

^julian

julian

2023-12-04 12:42:55

Google-Free Push Messaging for Google-Free Phones

UnifiedPush open-standard push messaging complements degoogled android-compatible phone OS's such as LineageOS.

People who do not want to depend on Google or have them control our devices are using android-compatible but not google-controlled phones, a.k.a. “degoogled phones”. We have been asking for several years if we can have google-free push notifications. Thanks to the developers of UnifiedPush, the answer is now, “yes!”

The open standard UnifiedPush.org has now been created. While not a large number yet, a useful handful of apps already support UnifiedPush, including several matrix and fediverse apps. For its servers and the associated client-side “distributor” component, there are multiple successful implementations deployed.

The current situation is such that anyone can use UnifiedPush on an android-compatible device by installing their choice of UnifiedPush distributor app (which must run in the background), configuring it to connect to their chosen U-P server (compatible with chosen distributor), and then installing any number of U-P-aware apps which will then use it (without needing per-app configuration to do so).

In android-compatible OS ROM projects such as LineageOS, implementing some core support for the UnifiedPush.org standard now seems to me like the right way to go. Exactly what form of support is to be decided.

Involving the OS ROM

Some ways an OS like LineageOS could usefully be involved to improve the UnifiedPush experience are:

• ensuring the U-P distributor app has a convenient way to be installed and permitted to run in the background, free from restrictions, because getting this right is critical and if the user installs the distributor manually it can be tricky to get right; (investigate: would it need to be a system app, or some kind of whitelisting (ugh), or be split into a system component and a user component, or what?)
• providing a convenient way to let the user (or the OS distribution provider) configure the distributor's U-P server address: perhaps rather than using an ad-hoc UI provided by the distributor app, it could integrate with “accounts” settings.
• potentially providing a system settings UI for monitoring the U-P connections and which apps are using them.

Thoughts on the role of microG. The purpose of microG as best I understand is to provide Google compatible APIs to apps which expect Google services. Underneath these APIs, it provides access to a mixture of actual Google services, alternative real services, and fake services. As far as I know it does not so far provide any non-Google APIs, and yet for push notifications the provision of UnifiedPush APIs might be a good fit for fulfilling its overall purpose as a compatibility layer. Or perhaps not, perhaps that is out of scope and should be in LineageOS or another add-on layer instead. I'm sure the folks involved will work out what is best.

Constraints, FCM Fallback, non-Android

Unlike the situation with some other google APIs, it is important to note that an OS compatibility layer such as microG cannot automatically divert the connections made by apps built using Google's FCM, to use U-P instead. The apps must be modified.

However, the inverse is possible: a UnifiedPush aware app can automatically “fall back” to using Google's FCM if U-P support is absent and FCM support is present. See details of the Embedded FCM Distributor in UnifiedPush documentation.

Non-Android devices can use UnifiedPush too, including Linux phones such as PinePhone and Purism Librem. The UnifiedPush D-Bus spec may be relevant. (On locked-down proprietary devices such as Apple's it is unlikely to be possible, nor to make much sense: FAQ.)

Packaging a UnifiedPush Distributor

A U-P distributor app could be built in to an OS or subsystem like microG but there is a significant down-side to that: it would support only one type, or at most a fixed small number of types, of U-P server. Choosing a distributor type is more of a whole OS packaging decision. In cases where the whole OS is related to a service provider of some kind (so not like LineageOS, but perhaps like Murena/Calyx/Graphene etc.), the service provider might choose to run a U-P server for their users and have their distributor automatically connect to it (with user consent/opt-in/opt-out). In the more generic/self-hosted case (like LineageOS) it makes more sense to leave it to the user to install their preferred U-P distributor.

I would love to see distributors of google-free phones, such as Murena, support google-free push notifications. I posted a brief sketch of a UnifiedPush Plan for Murena /e/-OS on their forum, without attempting to go into details of integrating the U-P distributor into the ROM.

History

A rough time line of UnifiedPush development. (From light research and having followed it through its development.)

• 2018: FOSS-Push planning
• 2019: OpenPush — defines the architectural concept
• 2020: UnifiedPush — building on OpenPush concept to a complete specification
• 2021: Gotify — a FOSS push system — was forked to add UnifiedPush support
• 2021: NextPush — NextCloud-based UnifiedPush system created
• 2022: ntfy — a FOSS push system — adds UnifiedPush support
• now: more and more apps use UnifiedPush for google-free push support

Conclusion

Whatever the specifics of how any android-compatible OS ROM project might choose to proceed with google-free push support, the solution space enabled by UnifiedPush now exists. Speaking as one of the people who prefer our devices not to be controlled by and dependent on Google:

What do we want? UnifiedPush!

When do we want it? Now!

---

See my other posts tagged... #unifiedPush #degoogled #awesomeFOSS

---

Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @[url=https://social.jsts.xyz/users/8mflxtuvnp]Julian[/url]​@wrily.foad.me.uk · use the Cactus Comments box above · matrix me · Fedi follow me · email me · julian.foad.me.ukDonate: via LiberapayAll posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise

nextpush-android

Android application

^Codeberg.org

13 SHIFTcycles♻
Weiter geht’s mit "repair". Blog: shiftphones.com/13-shiftcycles…
Für uns steht fest: Wenn Geräte nicht reparierbar sind, liegt ein Designfehler vor. Denn noch besser als Neues zu schaffen, ist Bestehendes zu erhalten. Die Reparatur eines Gerätes soll einfach und wenn möglich auch direkt von den Nutzerinnen und Nutzern übernommen werden können.

#shift #shiftphone #shifthappens #cycle #repair #righttorepair #reuse #recycle #reduce #sustainable

runder-tisch-reparatur.de/repa…

Wir haben unterschrieben!🖊️

Ressourcen schonen muss sich lohnen - unter diesem Motto sammeln 20 Organisationen und Unternehmen Stimmen für einen bundesweiten Reparaturbonus. Die Petition richtet sich an die Bundesregierung und fordert einen Zuschuss in Höhe von 50% der Reparaturkosten.

#righttorepair #repair #reparatur #shift #shifthappens

Reparaturbonus jetzt!

REPARATURBONUS JETZT! Deutschland produziert Berge von Elektroschrott. Nicht mal ein Viertel aller kaputten Elektrogeräte wird repariert! Verbraucher*innen entscheiden sich häufig für den Neukauf, da Reparaturen schlichtweg zu teuer sind.

^{Runder Tisch Reparatur}

Great news for the Right To Repair:

"EU: Smartphones Must Have User-Replaceable Batteries by 2027 | PCMag"

#RightToRepair #EU #Europe #phone #batteries #tech

pcmag.com/news/eu-smartphones-…

EU: Smartphones Must Have User-Replaceable Batteries by 2027

The European Parliament just caused a major headache for smartphone and tablet manufacturers.

^{Matthew Humphries (PCMag)}

Update. In rural America, right-to-repair laws are the leading edge of a pushback against growing corporate power.
theconversation.com/in-rural-a…

"Under the agreement, John #Deere promises to give farmers and independent repair shops access to manuals, diagnostics and parts. But there’s a catch – the agreement isn’t legally binding, and, as part of the deal, the influential #FarmBureau promised not to support any federal or state #RightToRepair legislation."

#patents

In rural America, right-to-repair laws are the leading edge of a pushback against growing corporate power

Corporations restrict what farmers can do with their own seeds, as well as their farm equipment when it breaks down.

^{The Conversation}

I'm very glad to see farmers win the right to repair their tractors. It's a win for consumers against bogus #IP objections from manufacturers.
bbc.com/news/business-64206913

#RightToRepair, #RightToTinker

US farmers win right to repair John Deere equipment

The grassroots movement has grown among consumers around the world as repair costs soar.

^{By Monica Miller (BBC News)}

Update. Turns out that John #Deere has been using open code under the #GPL w/o living up to the license. The Software Freedom Conservancy (@conservancy) is calling on it to comply — which would greatly enhance #farmers' #RightToRepair.
sfconservancy.org/blog/2023/ma…

"We…publicly call on John Deere to immediately resolve all of its outstanding GPL violations…by providing complete source code…that the GPL & other copyleft licenses require, to the farmers & others who are entitled to it."

#OpenSource

John Deere's ongoing GPL violations: What's next

I grew up on a farm. My parents worked hard to grow crops and manage the farm business. My parents also found additional jobs to make ends meet. As farmers have done for millennia, my family used tools to farm.

^{Software Freedom Conservancy}

Ok now that we have your attention, please look at Big Tech lobbyists’ impact on New York’s #RightToRepair bill.

Before ➡️ after

I can't sign this as I am not a constituent of the EU, but I hope this comes to pass and the EU forces some responsibility into the #tech corporations. Goodness knows the US isn't going to lead the way.

#OpenSource #ConsumerRights #Computers #PlannedObsolescence #FOSS #ElectronicWaste #environmentalism #RightToRepair

Imagine you could install any software on any device. The devices you own that don't receive updates anymore, or where you found out that the software is full of ads/tracking. You could replace it, maybe with a Linux distro like postmarketOS running mainline. These devices wouldn't need to be electronic waste. We signed @fsfe's #openletter to the EU to make this happen.

You can sign it, too!

fsfe.org/activities/upcyclinga…

#Ecodesign #RightToRepair #EWWR #FreeSoftware #LinuxMobile #UpcyclingAndroid

Open letter for the right to install any software on any device - FSFE

Free Software Foundation Europe is a charity that empowers users to control technology. We enable people to use, understand, adapt, and share software.

^{FSFE - Free Software Foundation Europe}

Section 1201 must go.

Fixing the #DMCA is making all the right people mad
youtu.be/hdd1wuCQ3tY

#dmca1201 #righttorepair

Fixing the DMCA is making all the right people mad

https://thehill.com/blogs/congress-blog/3512830-proposed-repair-bill-goes-too-far/https://www.congress.gov/bill/117th-congress/house-bill/6566/text?r=4&s=1#:...

^YouTube

Today the FSFE publishes an #OpenLetter, co-signed by 38 European organisations and companies to ask #European legislators for the universal right to install any software on any device, including full access to hardware: fsfe.org/news/2022/news-202204…

#Ecodesign #RightToRepair #FreeSoftware #UpcyclingAndroid