🚀 Seen my posts and want more? Dive deep into the issues with Big Tech at Escape Big Tech!

💡 Need FOSS-focused software solutions? Reach out on Matrix at @dannym:balooga.xyz!

  • 5 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle

  • Pretty clear you either haven’t read the bill or grossly misunderstood it. What you describe is not proposed legislation - it’s the current reality that individuals and independent repair shops already live with.

    The 2024 variant of the bill isn’t actually publicly available online, but here’s last year’s WIP text:

    https://olis.oregonlegislature.gov/liz/2023R1/Downloads/MeasureDocument/SB542

    Absolutely, the bill you mentioned is the one I was referring to. It does state that manufacturers must provide documentation, tools, and parts to both independent repairers and owners under fair terms. However, the real issue lies in how “fair and reasonable terms” are interpreted and applied in practice.

    Here’s a quote from Google’s actual response:

    User safety should be a top priority. Improper repair can be dangerous—especially if individuals use faulty parts or are unfamiliar with safety critical components, such as lithium ion batteries.** Legislation should acknowledge the risks borne by unskilled repairers and allow original equipment manufacturers (OEM) to provide parts assemblies rather than individual components to reduce the risk of injury.**

    Doesn’t scream right to repair to me, let’s continue.

    Right to Repair regulation should focus on: Devices that are repaired by an OEM’s existing repair offerings3 Right to Repair legislation in the United States is focused on leveling the playing field between OEM repair and independent repair offerings and putting consumers first, which we fully support

    So, if they don’t repair their devices and only replace assemblies, they’re not required to do anything for RTR, how convenient!

    Right to Repair regulation should focus on: Parts that are provided by an OEM’s existing repair operations

    Hmm… So the easiest way to comply with the law is to not do anything

    Policies should encourage repairers and recycling centers to recycle or to dispose of e-waste responsibly. We believe repair can be an important mechanism to reduce the large and growing problem of e-waste

    Classic corporate green washing, this doesn’t mean recycling, it means break products, into as many parts as possible and dispose of them.

    This is what recycling means to big tech:

    Those are icloud locked iphone mainboards that have had their chips drilled through (this is "recycling). Some extremely smart people have figured out how to scrap them for parts, but that’s the ingenuity of actual repair people, not Big tech’s recycling.


  • Yes, it basically just reinforces the usual “Authorized Service Providers” spiel, i.e. it’s not a real right to repair bill.

    Special Access for ASPs: manufacturers have to share repair manuals, tools, and parts ONLY with ASPs under “fair and reasonable terms”.

    This means if you’re not part of their club and haven’t signed their agreements to become an ASP you may not be allowed to purchase parts. And to be clear, becoming an ASP can restrict you in the kinds of repairs you can provide, and the kinds of information you can tell your customers, under legal threat, and may require you to hit impossible sales quotas.


    Parts and Conditions: It gets trickier with parts. Manufacturers aren’t actually forced to give you, the little guy, access to individual parts. What they’re obligated to do is to provide full assemblies to ASPs. So, if you need just a tiny part for a fix, tough luck – they can legally turn you away or make you buy a whole assembly, which is neither practical nor cost-effective.


    Do you have a license for that?: It’s like asking, “Do you have a permit for that fishing rod?” before you even get to the lake. The bill implies that if you want to repair these devices, you better have some sort of certification or license. This could be a huge barrier for independent repair shops, especially those who don’t have the best relations with the company they repair devices of, or even DIY fixers. You want to repair something? First, prove that you’re qualified according to their standards, which can be pretty steep or even unrealistic for many. It’s another way of keeping the repair circle closed and controlled while pretending to be the moral authorities of social and environmental justice.


    “Can’t you see just how great a company we are? We’re allowing you to repair YOUR device, (assuming that we like you, that is), aren’t we such good people? After all you’re our dear cust---------”

    ERROR: CONSUMER ACCOUNT NR. 48570 TERMINATED FOR INAPPROVED WRONGSPEAK. PLEASE INSERT CREDIT CARD TO CONTINUE READING MESSAGE.


    Thank you for buying from Google, we support you, we love 😍 right to repair, we love 💚 the environment and we 💕 you, dear consumer 😘… errr… customer










  • Danny M@lemmy.escapebigtech.infotolinuxmemes@lemmy.world:wq!
    link
    fedilink
    arrow-up
    33
    arrow-down
    1
    ·
    edit-2
    10 months ago

    I prefer the extremely intuitive:

    [C-R]=system("grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9")

    or

    i:!grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9[esc]Y:@"[cr]

    It just rolls off the fingers, doesn’t it?

    Edit: damn it lemmy didn’t like my meme because it assumes that characters between angle brackets are html tags :( you ruined it lemmy

    EDIT 2: rewrote it, just assume that square brackets are buttons not characters


  • in this case the instruction set is extremely small (and includes open source verilog, so you could even fab it yourself)

    quote from the website:

    The CPU of the TKey is a modified version of PicoRV32, 32-bit RISC-V running at 18 MHz. Modifications includes a fast 32x32 multiplier implemented using the multiplier blocks in the iCE40 DSPs as well as a HW trap function.

    The supported instruction set supported by the CPU is a subset of RV32I. Specifically it includes compressed instructions, but excludes instructions for:

    • Counters
    • System
    • Synch
    • CSR access
    • Change level
    • Trap redirect
    • Interrupt
    • MMU

    The instruction set implemented by the CPU also includes multiplication instructions from the RV32IC_Zmmul (-march=rv32iczmmul) extension. Division is not supported.

    Any illegal, unsupported instruction will halt the CPU. The halted CPU is detected by the hardware, which will blink the RGB LED with red to indicate the error state. There is no way for the CPU to exit the trap state besides a power cycle of the device.

    Note that the CPU has no support for interrupts. No instructions, ports or logic.






  • Danny M@lemmy.escapebigtech.infoOPtoLemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    10 months ago

    Didn’t know about mitra, thanks for sharing!

    Regarding Linus’s quote, I completely agree with him and that’s mostly why I asked for feedback; I don’t have the time to work on this myself at the moment, and even if I did I want to hear conflicting opinions on the implementation before I did anything



  • Danny M@lemmy.escapebigtech.infoOPtoLemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    3
    ·
    10 months ago

    I really don’t want to turn this into a crypto discussion, if you think there are better alternatives I’m open to hearing about them; I’m mostly interested in rewarding people for their content and paying for instance admins and lemmy developers. You’d be surprised how much you and I probably agree on regarding crypto