Well possibly, but here’s the thing: if I don’t say anything, I don’t have to worry about having to explain myself later.

This is just a software project, I really really like my job and I have other hills to die on frankly. So I just don’t need the aggravation.

The particular open-source license doesn’t matter: they’re doing all they can to not release their source code and that’s what I need to fix their stuff.

I can’t sadly. It would make it obvious which company I’m talking about, and if ever read this thread, they could retaliate against us.

My employer is openly willing to let the engineers work on whatever they want, however long it takes to make things good or better, not just good enough. The bean counters don’t run this place: we take the time to do things right.

It’s a policy that has worked for us for the past 40 years, and it’s the main reason why our customers come back to us and we’ve been consistently very successful over the decades.

Anyhow, originally one of my colleagues asked me if it would be possible to compile and debug our code in VSCode instead of the company’s IDE. I said I’d try to see if it’s possible, and then I went down the rabbit hole - with my boss’ blessing 🙂

I can’t really say because it would make it obvious which debugging tool I’m talking about and that would out me. And then the company could put 2 and 2 together and find out who my employer is and… you know, our orders might become slow or mishandled, that sort of things. My company’s entire business depends on that one supplier, so it wouldn’t be good.

Fixed. Thanks for the proofreading 🙂

You assume I’m paid 20k per month when I’m paid a lot more than that 🙂

Anyway, not to worry, we’ll recoup that money next year when we won’t have to renew our license for the 10-so development machines.

This one is kind of the same thing: it’s a bone-stock FTDI 4232H probe with a bit of logic tacked on to disable the chip without a custom init command and a custom USB PID/VID. All I need their driver for is to enable the chip. After that, I can just use the open-source FTDI driver. But the driver makes everything super-slow, so the point is kind of moot anyway.

Probably another attempt to go around the GPL actually, because they use the FTDI driver to talk to the chip (because the open-source libusb is very slow in Windows) and that too can’t be linked to the GPL debugging tool. So the probe masquerades as a custom device.

deleted by creator

deleted by creator

there are some good guys out there

I know that. But it’s just a general rule at this point: I just don’t give money. It’s rarely satisfying to give money (and yes, the person doing the donation needs to feel good doing it too) and I just don’t want to find out who deserves to get mine and who doesn’t. I understand your sentiment too, but that’s my personal rule. One has to draw the line somewhere: I’m not Mother Theresa and I reckon I contribute more than the average person to my local community. But I’m also free to donate what I want to donate, and money isn’t part of what I want to donate.

I’m a programmer. I have created, maintained and contributed to many open source projects over 40 years. That’s my donation.

I never give money: I give my time - like for example I’m a volunteer at our local association for the blind - and I give non-commercial things like my blood, used clothing, used toys or food. And to repay the other developers whose work I enjoy everyday, I donate code that I strive to make as good as possible.

The reason I never give money is because the money - part or all - invariably ends up in someone’s pocket other than the intended recipient. When it’s legal, it’s called “overhead”. Still, legal or not, and justified or not, I’m not interested in paying for that.

It’s not kindness 🙂 I only made a GPL claim. All I want is the stuff that the GPL entitles me to have. The rest is off-topic and - as you say - toxic. Nobody needs the off-topic stuff in the Github repo I’ll post the GPL code to: it’s about the code, not the people or whatever drama happened at their workplace.

Nah… It’s not a matter of embarrassing the company, it’s out of decency for the people who work(ed) there. There’s stuff like “This shit is why Stu was fired - Phil” or “Best leave this out of the repo for now as I don’t want to be included in the next round of downsizing - Tom” this would make Stu, Phil and Tom look bad and possibly hurt their careers. And it would advertise that whoever prepared this ZIP file for me didn’t bother sanitizing company confidential information out of it, possibly putting their job on the line too.

The code is GPL, and I consider the git history part of the code. The rest is inappropriate and potentially hurtful to people who didn’t do anything to deserve grief.

So basically it’s UserLAnd with accelerated graphics instead of VNC.

Conclusion of this thread:

It took a mightly long time, but the company eventually coughed up the source code. They sent me a big ZIP with an large git repo full of uncommitted changes and a bunch of comments and temp files that really shouldn’t leave the company 🙂 Clearly some engineer just zipped up the local repo on his hard disk without doing any cleanup.

So they complied with the GPL in the end. Just the bare minimum - i.e. providing the source code on request and nothing mode. I wish they put it up in their Github but they don’t want to do that apparently. I’ll clean up the embarrassing files and comments and put it up in mine.

You can fork it and basically freeze it at manifest-v2.

The problem is, all the big tech sumbitches, their buddies and all the companies who want a corporate website that Just Works [tm] will support Google’s new shit, and your privacy-respecting fork will slowly deprecate and stop working right, because you don’t have the resources to mirror new features in Google’s official browser. And of course, ordinary internet users with stick to Google’s version because they need a browser that works.

Chicken and egg… In fact, that’s exactly what’s happening to Firefox and why it’s sliding into irrelevance: Google is simply too massive and too monopolistic to resist for very long. Mozilla has had hundreds of millions to throw at trying and even they are on the verge of losing the battle completely.

With Rosehip. But good news: it would appear my ticket finally made its way to the development team and to legal. They sure are taking their own sweet time like a good giant corporation dealing with a pointless single guy, but things seem to be moving in the right direction.

If they refuse again this time, considering they now acknowledged that my ticket is processed where it should be processed, I will contact the FSF, and name and shame. But for now they’re showing good will.

I rock a Fairphone4 running CalyxOS. Apart from the hardware switches on the Purism phone, I don’t quite see what I’m missing out on privacy-wise.

The camera does not take influencer quality photos

That’s actually a selling feature.