No way, really who could’ve guessed? I’m shocked, I’m telling you shocked…

oh wait, I’m not

How about using LDAP? It’s a bit complicated to learn but it’s easy to integrate it in a bunch of applications and it allows you to manage user accounts and permissions in one central place.

Maybe try LLDAP which is a modern implementation (haven’t used it myself) which is designed to be simplified and I assume more welcoming to newcomers.

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

Exactly! This is just a PR stunt, nothing more, and it looks like “journalists” bought it.

except that’s not happening. It’s giving big tech good PR while they keep doing exactly what they have been doing for the past 2+ years (i.e. pretending to care about right to repair, and the environment, and whatever other good-soundign cause they can think of, without actually doing any of it)

No they will not.

That’s a shitty article by a “journalist” that hasn’t read the bill otherwise they would know that it’s NOT right to repair, but rather it’s a bill disguised as right to repair that actually gives even more monopolistic powers to big tech.

don’t lump in everyone with musk, there are many people that actually believe in free speech

Their search results constantly impress me and honestly it’s 10 bucks for unlimited searches, it’s worth it even if it’s not a business expense, plus since you’re paying for the service they’re less likely to track you. I wish their code was FOSS, but I’ll take it, still better than google, bing, and all the others I’ve tried.

Also they actively promote the small web and you can even personalize your search results by removing websites you don’t like from the searches (for example I have a lot of big tech websites blocked)

Actually other search engines do much better with Lemmy. Kagi’s search works wonders if you select the filter for Fediverse Forums. And you can assign that filter to a bang, such as !lemmy, so that when you search “!lemmy query here” it’ll search only on the fediverse A few examples:

And this ladies and gentlemen is another reason why we should try to escape big tech’s grasp.

In general I agree with you. I find that most FOSS software is more polished than proprietary software, and it is generally more powerful.

However, I think that one problem that people somehow overlook in my opinion is that the financial side of the issue is also extremely important. I want more people to work on quality FOSS software, and I want it to become socially acceptable to work on FOSS as your main job. For that one thing is needed in my opinion: we as users of FOSS software need to give developers the financial incentives to work on what they love the whole time. In fact I want it to reach the point where immoral, non FOSS companies struggle to find developers because they’re all working on FOSS.

if you program the firmware directly your program can be stored, but it requires you to also buy the firmware writing tool and the FPGA unlocked version of the product (FPGA can be locked after writing it naturally)

what FOSS library do you maintain?

The concept of competition among tech companies has done a complete 180 on its original meaning. It’s no longer predominantly about crafting superior products; rather, it’s become a race to secure the largest amount of investor funding.

In this transformed landscape, the product itself and revenue generation often take a backseat, or at best, hold a tertiary importance. The heart of customer-centric ethos, especially crucial elements like data security, are now distressingly overlooked. What matters is getting the next investment to become the next “unicorn” and be acquired for billions of dollars. Silicon Valley Companies want the easy way out, do only a fraction of the work for an exponential amount of the benefits.

Don’t get me wrong, there are reasons to seek investment, getting a good product built is actually complex and you actually need a lot of different people working on it. The alternative is losing years of your life on a sisyphean ordeal of soul-crushing, hundred-hour work weeks (and that’s real work, not “let me check twitter” work), making you question your life choices and whether you should just throw it all away, abandon technology, become a hermit and move to a shed in the mountains.

The problem is that the EXPECTATION today is that you’re gonna build a third of a product, care about 1% of the actual business behind it and then pivoting exclusively to the pursuit of investment, letting everything else rot

To be fair, the allegations haven’t been proven and allegedly he was 13 at the time… not that it makes it any better, but context matters

I don’t know why anyone would write their IPs in octal, but fair point

Definitely, tho if you store it as a u32 that is fixed magically. Because 1.2.3.4 and 1.02.003.04 both map to the same number.

What I mean by storing it as a u32 is to convert it to a number, similar to how the IP gets sent over the wire, so for v4:

octet[3] | octet[2] << 8 | octet[1] << 16 | octet[0] << 24

or in more human terms:

(fourth octet) + (third octet * 256) + (second octet * 256^2) + (first octet * 256^3)

Please don’t. Use regex to find something that looks like an IP then build a real parser. This is madness, its’s extremely hard to read and a mistake is almost impossible to spot. Not to mention that it’s slow.

Just parse [0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3} using regex (for v4) and then have some code check that all the octets are valid (and store the IP as a u32).

If somebody actually did that it would be grounds for removing their privileges to merge into master. THIS, THIS is why the JavaScript ecosystem has gotten so bad, people with mentalities similar to his.