Live data from Hacker News

Bear is now source-available

herman.bearblog.dev

171–180 of 509 posts

Re: Bear is now source-available

#171

Naive. Guy picks a license that allow anyone to do anything they want with his code. Later realizes that was not appropriate when he's trying make money. Changes to an obscure license that on the surface seems to fix the problem. Your options are: MIT / BSD, GPL, LGPL, AGPL. All others are unnecessary and create needless incompatibility.

I'd have to agree with this stance. You choose MIT when you are happy to share your source with no strings attached. Some do pick MIT with this intent, but that was not the case here. But rather a case of either miscommunication or wanting to have the pie ("look how altruistic I am") and eating it too ("look how business-minded I am").

I mean, there’s a chance it’s exactly what he said, “I didn't give it much thought at the time, but knew that I wanted the code to be available for people to learn from, and to make it easily auditable so users could validate claims I have made about the privacy and security of the platform.” … it doesn’t have to be some to be some sort of nefarious OSS altruism, it really could be, “maybe people would want to see how this works”… that ends up leading to … oh crap a bunch of people who have never contributed, and will never contribute, are hosting versions of what I created and taking money that I really would like to have to feed my family.

Re: Bear is now source-available

#172

We are also entering the age of "hey AI, take this repo, reimplement the same functionality". Now, no LLM is currently anywhere near doing that for ElasticSearch. But for a project with 4845 lines of Python code? (as per tokei) Definitely doable, with a bit of handholding and manual fixing. Would that be a derivative work? Maybe, but that would be a hard legal battle.

> We are also entering the age of "hey AI, take this repo, reimplement the same functionality".

Wouldn't you do this just against the/an API documentation? Interesting thought.

Re: Bear is now source-available

#173

Naive. Guy picks a license that allow anyone to do anything they want with his code. Later realizes that was not appropriate when he's trying make money. Changes to an obscure license that on the surface seems to fix the problem. Your options are: MIT / BSD, GPL, LGPL, AGPL. All others are unnecessary and create needless incompatibility.

Naive. Users who think a project that is Open Source will remain Open Source forever.

Authors gave the right to change license to a proprietary one. Users being surprised by this are as equally naive as developers who think you can make money writing Open Source.

Re: Bear is now source-available

#174

i need a bear alternative that can support images and video embeddings

https://prose.sh — serve your blog using ssh. It was inspired by bearblog and others in this ecosystem of minimal blog platforms.

https://pico.sh includes a suite of other services (some paid) but the business model doesn’t depend on prose in particular.

Re: Bear is now source-available

#175
post #150

Earlier quoted context omitted.

> the stance of the 'Open Source' crowd The original stance of the open source crowd was more along the lines of the GPL -> GPLv3 -> AGPL, which expressly prevents this kind of thing. The proliferation of "give everything away for free" MIT/BSD/Apache licenses seems to me to have been an intentional campaign by corporate interests to undermine free software ideals

The MIT and BSD licenses predated the GPL. People have a choice as to which ethic to follow ... it's not the result of a corporate conspiracy. (And I'm a social democrat, not a corporate simp.)

I'm not so clear the choice was made consciously. There's a big swing away from the GPL and towards MIT/BSD around the time that Apple starts adopting a bunch of open-source projects for inclusion in MacOS X, and it accelerates when various big companies announced that they would be forbidding GPLv3 adoption. Fast forward to the cloud provider era, and basically no new software is being placed under the GPL (at least in part because Amazon/Google/Facebook/etc are predicating contributions on being GPL-free)

Re: Bear is now source-available

#177

Earlier quoted context omitted.

> once we start talking about the kind of software large corporations (like AWS) will have an interest in I'm not sure why someone who is spending their limited free time building software to give away for free would want Amazon as a downstream consumer Do you enjoy spending your nights and weekends dealing with CVE reports, while a high-6-figure BigTech engineer nags you that they need it fixed?

We definitely agree on this point. Different licenses select for different things. It is an annoying problem to have, but if your goal is to be able to support yourself by working on your open source project full time (not saying this has to be or should be everyone’s goal), then having big tech engineers nagging you is probably a good problem to have.

Honestly haven't seen many open-source maintainers convert a BigTech downstream into recurring revenue. I'm sure it does happen, but its far from the norm

Re: Bear is now source-available

#178
post #150

Earlier quoted context omitted.

> the stance of the 'Open Source' crowd The original stance of the open source crowd was more along the lines of the GPL -> GPLv3 -> AGPL, which expressly prevents this kind of thing. The proliferation of "give everything away for free" MIT/BSD/Apache licenses seems to me to have been an intentional campaign by corporate interests to undermine free software ideals

The MIT and BSD licenses predated the GPL. People have a choice as to which ethic to follow ... it's not the result of a corporate conspiracy. (And I'm a social democrat, not a corporate simp.)

The creation of those licenses, maybe. Their mass popularization, and the pooh-poohing of GPL licenses that often goes with it in related discussions, is much more recent.

Re: Bear is now source-available

#179

As far as I understand it, the stance of the 'Open Source' crowd is that if Amazon can't make it one of their AWS offerings then it isn't true open source, and they'll get very upset at you if you claim it is. I'd like to see some recognition from this crowd of the "free-ride competition" problem as this author puts it. What Herman is doing is a service to us all, and we should find a term (better than 'source-availa…

> the stance of the 'Open Source' crowd The original stance of the open source crowd was more along the lines of the GPL -> GPLv3 -> AGPL, which expressly prevents this kind of thing. The proliferation of "give everything away for free" MIT/BSD/Apache licenses seems to me to have been an intentional campaign by corporate interests to undermine free software ideals

Amazon offers lots of AGPL software, and they fully respect the license in all cases. Ultimately the GPL is about protecting users' rights at the expense of developers' rights. So as long as AWS can offer a better/cheaper managed version of a software service, while still giving the users all details on how to run the same service if they chose to, then the AGPL is completely achieving its aims, even if the original company goes out of business.

Re: Bear is now source-available

#180

Earlier quoted context omitted.

That argument can be made for virtually every piece of software. We all build on top of the work of others.

The argument is that why should I be able to use software for free but do not want mine to be used the same way?

So everything should be open source and no one should be able to write software to sell it?

If you want your projects license agreement to be withheld in future projects there is a license for that. Its called copyleft

Post reply on HN