I find the Swift tooling very lacking. There's no way to lint dead code, there no way to auto format the files exactly as Xcode would do it and tell the linter those rules so that it doesn't lint your auto formatted code. Xcode project files are impossible to edit except with Xcode and Xcode often has issues and I need to manually empty the build folder. These are just some of the issues I remember
Now that some bikes have electronic shifting, you can attack the bike itself. I wrote two blog post about how to downgrade the Shimano Di2 shifters and do a replay attack to remotely shift it. You can find them here:
I think an important factor is also how long you had the same number. I switch numbers every couple of years because I get a new contract and moving the number to the new company is such a hassle. Over time you share your number with more and more companies and people who sell it or get breached.
My parents had their number for ~30 years. I never get spam calls or texts. They get one once a week or so (this is in Germany, we get a lot fewer of these calls).
In theory you cannot even say for all programs and all inputs if the program will finish the calculation [0]. In practice you often can break it down but the number of combinations of input is what makes it impossible to test everything. Most developers try to keep individual functions as small as possible to understand them easier. You can use math to do formal verification, but that gets difficult with real programs too.
I wasn't aware of that; it wasn't clearly specified. It only mentioned a "secret" feature, but I assumed it was AI-related rather than UI-related. Additionally, Anthropic's Claude Code position on their website states that they expect their developers to work across the stack, including both front-end and back-end.
Right now it is just a hobby and there are still a number of bugs remaining. Since I don't have an income from it, I can't dedicate more time to it. Hiring me would allow me to work on fixing them full time and make the progress much faster
Hey, props to your attitude, and I wish you the best of luck.
Obviously, you've provided value to a company in a really in-demand area. It doesn't feel right to treat the contributors like this. Sadly, it seems that the companies have the power and the intent to just abuse and exploit
I don't have a solution. I am just expressing my frustration from the perceived injustice.
Correct, you cannot remove a version or the whole crate unless very specific criteria are fulfilled. You can "yank" versions. That prevents people from adding the version as a new dependency, but if you relied on it before it got yanked, your build will succeed.
I wouldn't delete old versions even if I could though. My goal is to publish a rock solid library that everyone can depend on and build awesome projects with
Hey, I'm the author of the blog post. Thank you for submitting this. If you have any questions feel free to ask and please let me know how the writing was. It's one of my first posts so I'd like to improve
You should change the license to AGPL and 'custom, contact for payment details', and provide a link to this as why you did so.
Simply put, anything not a viral license like GPL allows parasitization by companies effectively living off FLOSS devs, with absolutely nothing to gain. Human rights under GPL were meant to apply to humans, not '3 lawyers in a trench coat' (corporations).
They can make their decisions (snubbing a dev of code they deem good enough for enterprise). And you can make comparable decisions, punishing them for the sheer hubris.
It also reaffirms that my decision of AGPL for everything is the right one. They can contact for custom terms.
> It also reaffirms that my decision of AGPL for everything is the right one. They can contact for custom terms.
Since your replies below are focusing on compensation: have you actually made a nontrivial amount of money with that model?
I would expect that should be a prerequisite to reaffirm it was the correct decision, especially if you're giving unsolicited advice to strangers about how they should license their software.
Some people want others to freely use their software and choose MIT precisely because it's more free than GPL. There's nothing wrong with just making something for free and giving it away if that's what you want. Not everybody has to be chasing money in all their activities.
The author said he was proud of this outcome and nervous at how widely his hobby project will be deployed. That sounds like the ambition of many open source authors and a win. Might never have happened with GPL.
> Some people want others to freely use their software and choose MIT precisely because it's more free than GPL.
MIT license is absolutely not 'more free' than the GPL.
In fact, MIT means you give up effective ownership and control. You lose control and contributions.
And what do you get for that loss of control? Exposure. Or, in this and many other cases similar, you get diddly shit. Some company paracitizes your code, sometimes even demands SOC questionnaires and 'do this bug NOW', and other abuse.
> Not everybody has to be chasing money in all their activities.
Talk about missing the point! This was all about money. It was about a job at the company where the code is being used in a production manner. And they didn't even bother to give an interview.
And not many of us are independently wealthy, and can do things that we want with no monetary care. And, most FLOSS devs aren't that. Instead, they're being used as unpaid stepping stones so some overvalued AI hypesquad can vibecode (or slotmachine programming) faster.
> The author said he was proud of this outcome and nervous at how widely his hobby project will be deployed. That sounds like the ambition of many open source authors and a win. Might never have happened with GPL.
That's where I hope the author relicenses as LGPL and proprietary, and doesn't give Anthropic any more free professional work.
And if it never would have happened with the GPL, gasp, they would have had to pay developers to create it.
And until I'm independently wealthy, I too will license AGPL. If you're making money on my stuff, I want a cut. Simple as that.
>MIT means you give up effective ownership and control. You lose control and contributions. And what do you get for that loss of control? Exposure. Or, in this and many other cases similar, you get diddly shit.
Isn't that what true freedom is?
You can argue that more freedom is a net burden for both the individual and society (tragedy of the commons), but that doesn't negate the aspect of it being more free to begin with.
>And not many of us are independently wealthy, and can do things that we want with no monetary care.
Indeed. But not many people contribute to any kind of OS community to begin with (regardless of the license). I would like to one day, but then the industry laid me and hundreds of thousands off in the last few years and those plans were delayed.
There definitely is a certain level of privilege in being able to provide knowledge to others on the side. Even morose if you're part of an organization that pays you to do so.
Maximum freedom is when people have the freedom to do everything except take away other people's freedom. When you give people the freedom to take away other people's freedom, you don't get a free society.
So, what is your net-worth, in that you fight for freebies to corporations? What net worth should I strive towards so I can be nonchalant and passe about money?
I'm certainly not there.
Also more curious, is the AGPL doesn't affect humans doing stuff. It affects companies when they grab, modify, and host and not share contributions. Read about anti-TIVOization. That's why the AGPL. I'm guessing you know this, and why you're attacking my viewpoints as 'missing the point'.
And yes, copyright is everywhere. And the GPL has some of the sanest terms to reuse, as long as you follow the requirement. And the GPL also further grows the ecosystem, due to virality.
But Anthropic wasn't exactly submitting code either, were they? In my world, parasites get antiparasitic drugs.
> So, what is your net-worth, in that you fight for freebies to corporations? What net worth should I strive towards so I can be nonchalant and passe about money?
I've seen people with un-stressed about money with net-worths that are orders of magnitudes below those that seem to obsess about it.
Your motivations are your motivations, if you don't like the idea of someone using your work to make money without giving you a cut, you can do you, but why is it hard to understand that other people might just not care that much about it (or, gasp, even find their work being used more rewarding than the potential monetary compensation)
> Also more curious, is the AGPL doesn't affect humans doing stuff.
It does affect humans doing stuff that isn't malicious, like if you need to solve a problem by modifying the code then now you also have to make that change public which is a hassle, I'd rather not have to track or maintain such things. I'd rather not have to think about that, and I care more about such nuisances than I care about the possibility of companies stealing it.
The scenario you are describing (discovering a problem to fix, being able to fix it, but then not sharing the fix with other people) is the exact reason why GPL has been invented: to force people to share their work, so that we can all have better software, together. Maybe the software you are using wouldn't have been that good if other people weren't forced to share their improvements. Your small effort is going to help others, and their small efforts are going to help you even more. This mindset of sharing should be natural but, as you just proved, people are lazy and so the license has to force them.
> If you're making money on my stuff, I want a cut. Simple as that.
It's clear that you're motivated by personal compensation for your work, which is fine, but it means you shouldn't license it as MIT. Other people are motivated by knowing that their work is useful to others, and those people shouldn't use GPL because it hinders that aim.
I know a bunch of people have tried to argue the toss on this one with you but I'd just like to put it out there that I can't agree strongly enough! Anyone watching can see these big companies are happy to toss developers to the side and develop social harms for profit.
All of this is built on exploiting the open source movement. Delineating between closed source ventures and Free community efforts is just good sense at this point. If they're going to take they must give back.
Cool. Thanks for the link, but I wasn't actually trying to steal anyone's thunder, and ... I did read the article. Just felt that it wouldn't hurt to link to it.
Also, that discussion gets pretty mean. Didn't feel like I wanted to send people there. I just wanted to give the guy a pat on the back, and bring some humor into it. Been there. Sucks.
I don't know--As a non-celebrity tech worker, it's actually kind of comforting to see a company that doesn't just automatically roll out the red carpet and grease internal wheels, just because a candidate once wrote some very popular software. It sounds like there are still companies that make you go through the same whiteboard hazing and non-deterministic hiring process as the rest of us mere mortals, regardless of how well known you are.
Actually, I don't disagree with some of the people that had issues with him, but I do have issues with folks that refuse to look at past performance, in general (I'm biased. I have a great deal of past performance, and can prove it).
It was just a kind of nasty conversation, and I didn't feel that it was appropriate to deliberately send folks there. I'm not really into the whole "Make the Internet Darker for Everyone" schtick.
Hey, great work, and just wanted to lend my voice in support! It's kind of wild how many open source devs have a story along similar lines. (Mine is the time when Mojang used my voxel engine..)
Now that this is trending on Hacker News, surely there will be a happy ending when someone from Anthropic sees this post and hires you with sincerest apologies and everyone lives happily ever after? Can we get a positive story out of this, universe?
What's the risk? The current state is "your application has been thrown into a fire and will never be seen by human eyes". How can it get worse than that? There is no downside to complaining on HN, except for getting the reputation that you really wanted to work there, which, again, isn't that negative of a thing.
I don't know. I have no comparison but it is common for crates to be released under MIT. I took over the maintainership from the original author so the license was already there. I rewrote pretty much everything so I guess I could try changing the license now but that's not something I wanna think about.
I do the work because I see it as payback for all the great open source software I use all the time.
I really like the copyleft idea, however, I think you did nothing wrong, IMHO, because if large corps like an idea, they will rather reimplement it rather than even bothering with ways to conform to AGPL or buy an alternative licence.
Particular in the age of AI, all source available code has become pretty much public domain (value is still in maintenance, etc). License have mostly become a compliance/ideology game that alienates most people. However, changing the license on the main repo, with only a minor version bump, would be a nice asshole move to get their attention past HR (won't make a difference, but if you have nothing to lose).
Copyright is but one pillar of intellectual property law.
I’d like to see an attempt by useful freedom respecting software projects to deploy patents to combat non-free reimplementations.
A GPL license that grants you rights to the backing patent as long as the software you develop with it is also released under the GPL license.
Use the library for closed source software? Copyright violation. Reimplement the software under another license? Patent violation. Create something slightly different and call it the same thing? Trademark violation.
Not sure of the rest of the world, but at least in the US, patenting “software” is a pretty murky subject legally (at least it feels that way when trying to do some basic research on it) Something that seems common among sources discussing it is that “Software Related Inventions” (eg, a computer that does XYZ) can be patentable, but software/code itself is not literally patentable. Seemingly, because we’re talking about libraries that would be pure software, not a product for sale based on it, you wouldn’t be able patent libraries like you’re talking about.
I’d provide links to some discourse of this, but honestly I think it’s better to search “can you patent software in the US” and do a brief read of various sources, because the terminology between them can seem somewhat counterfactual to eachother.
Copyright mostly protects big corps nowadays. That's because you need lawyers to enforce copyright, and if the other side has more money the battle may not be worth it.
On the other hand, Meta was found torrenting terabytes of books and for them it's a nothingburger. The rules are really meant for commoners.
Nah, forget this attitude of yours. You created something that a behemoth like Anthropic uses and literally noone thought about compensating you. Kick the ladder out of them, and go hard on their balls.
> but it is common for crates to be released under MIT
Something that isn't brought up enough in the "rewrite everything in Rust" discussions is that the API guidelines explicitly recommend MIT/Apache to "maximize compatibility" (i.e., corporate friendliness, or developer and user exploitation): https://rust-lang.github.io/api-guidelines/necessities.html#...
Your project has been around for a while, but it's crazy to me that anyone still open sources anything under MIT (or similar) in the era of LLMs. Are they that confident in their job security? Are they already independently wealthy? Frankly, even a proper copyleft license is likely to just be ignored, or the code laundered through an LLM-assisted rewrite, by these companies. I prefer to just keep anything I can't sell all to myself rather than release it, at this point.
Hey mate, I would just like to say that I wish they at least find it in their hearts to reward you for the value you have provided to them. Knowing cut throat american corps, I'm afraid the chances are nil. Even if a good amount for you is peanuts to them.
Don't know. A company can have a huge valuation on the stock market but that does not necessarily mean that they have cash to pay wages or can afford to pay a large team. If all they have are stocks they have to find somebody that buys those stocks with cash, then find a way not to run out of those money before selling more stocks. Eventually do an exit and stop worrying or become profitable.
I have always preferred permissive over copy-left, because I've historically been unable to use packages at work, which puts food in my mouth, as a developer who spends some time contributing to projects, especially those that I use at work.
This has changed everything. AGPL and GFDL from now on.
you're right about MIT vs GPL confusion. people brainwashed themselves into thinking MIT is "more open", because it's more permissive, but it lets others profit off your code without contributing back.
GPL makes them share or pay to relicense, since you own the copyright. with MIT, they don’t need to ask. MIT just benefits big corps. GPL better protects the open-source spirit, and paradoxically, the ownership of your work.
And yes, people being able to use your code for whatever they want is absolutely more open than having restrictions on how/who gets to use it.
One other model that can also work well is to dual license as GPL + commercial, so people who want to publish their work can use the GPL license but you can potentially fund the project from license sales to closed source users using the commercial licensing option. I see this a fair bit in the audio community I work within.
>And yes, people being able to use your code for whatever they want is absolutely more open than having restrictions on how/who gets to use it.
Yes, this is why people should use free not open , and GPL is more free when you report to the entire community otherwise you are in the famous case from a story where an USAian was claiming "Amerika is the land of the free, we are free to own slaves"
If you link against GPL code, your code needs to be GPL compatible. There are some IPC based workarounds, but they are too annoying and slow in most cases.
Yeah, basically MIT is "more open" in the short term, while GPL is more open on the long term. GPL, while restricting some freedoms right now, is actually enabling the remaining freedoms to be sustainable in the future. Very similar to how law enforcement works out with regards to a sustainable society, and how market restrictions work out to create a sustainable and diverse market.
UPDATE: Two people from Anthropic recommended me internally and their HR department already rejected the application. They recommended me for jobs where you need more experience with AI, so I agree that I wasn't a good fit for those positions. Thank you for your recommendations anyways. That was very kind.
A number of other people contacted me with offers so it looks like there will be a happy end to the story :-)
Hey, I really liked the post and especially the title. Quite surreal but also very fitting at the same time. The writing was great too. Hope you keep going. I’d love to read more.
I honestly think this is some system failure, even a Claude based one. I hope someone in the Claude Desktop team sees this and reaches out to you. Cheers!
This lands. I discovered an emergent feature in GTP40 and when I tried to post about it on the developer forum, the spam filter removed my post. I asked GPT40 to rewrite it for me. I posted the update, and got banned. There's too much 'noise'. People like Einstein and Tesla would've gone unnoticed today, as I doubt they would've become "social media influencers" just to promote their ideas.
If we are at the point where a hiring manager for a position deeply related to an open source library is not at least checking if the authors would be interested, I'm not sure.
If they use any form of filtering / evaluation along the line of STAR, the positive way you chose to deal with it plus the outcome of it being a top post on HN should score you half the position already, good luck :)
You should list a pay range unless you want to be ignored. Developers aren't going to go out of their way to play your little game without a carrot on the stick.
I'm disappointed about your resigned, almost subservient tone. This company is profiting immensely off of your work, and they don't even give you the courtesy of a job interview?
~~Have you considered a copyleft licence like LGPL?~~ Answered in a sibling comment
> This company is profiting immensely off of your work
I wouldn’t say that’s exactly the case. Not to denigrate the author or anything, but this library is a relatively minor part of what Anthropic is doing. It’s a UI manipulation library, specifically one that simulates keyboard and mouse inputs. While something like that is certainly necessary for the project in question, it’s not anything that couldn’t be rewritten in-house without too much difficulty, especially since they’re only using a subset of the platforms supported by the library.
I’m sure that working on this project has provided the author with expertise in this area that Anthropic could benefit from, and so in that sense it’s still a shame that they wouldn’t give him an interview, but that’s really all that can be said about it.
> it’s not anything that couldn’t be rewritten in-house without too much difficulty
This is my experience, at every group I’ve been in. Extending the date a bit is much easier than involving legal for approving a new library.
The group I’m in now sunk a substantial amount of money into a lawsuit for a library that accidentally made its way in, so are now “No LGPL.” with some crazy loops and approvals required if there’s really no alternative (very rare). From their perspective, it’s cheaper and safer to rewrite than not be in compliance, unintentionally or not.
You have to think about other users as well. One person taking advantage of you doesn't mean you have to cut off all the people not taking advantage of you.
Expecting a reward from open source software is a recipe for disappointment. I have contributed code to projects by companies that say I'm a mentally-ill household object. I'm not going to change the license of my open source projects to get back at them, because the collateral damage against entities that aren't evil simply isn't worth it. (It's also somewhat unlikely that the people working on NTP servers at Facebook wrote those policies, so...)
reply