Live data from Hacker News

Bear is now source-available

herman.bearblog.dev

331–340 of 509 posts

Re: Bear is now source-available

#331
post #206
post #76

Earlier quoted context omitted.

> It feels mostly in the spirit of FOSS to me From the license at https://github.com/HermanMartinus/bearblog/blob/998e87263248... >: " You may not provide the Software as a hosted or managed service that offers users access to substantial features or functionality " Given that the exclusive purpose of the Software in question is to implement a managed service for its users' hosting needs, I'm having trouble understan…

It’s saying that you can use Bear for your own blog, but you can’t launch a service that hosts other people’s blogs using it.

The readme has this to say about hosting your own blog on it:

"Bear Blog has been built as a platform and not as an individual blog generator. It is more like Substack than Hugo. Due to this it isn't possible to individually self-host a Bear Blog."

"It isn't possible" is obviously not true but a plain reading of both that combined with the license would suggest you can't use bear at all for anything.

Re: Bear is now source-available

#332

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…

There’s no such thing as a “free ride” on software that is given away freely.

It’s a gift. Once you gift it, it is no longer yours, it belongs to the people to whom you have given it to, to do whatever they wish with.

Re: Bear is now source-available

#333

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 is that if Amazon can't make it one of their AWS offerings then it isn't true open source

Exactly! As RMS famously put it[0]:

> It is essential, for the sake of true freedom, that every user - including the humble billionaire overlord who owns a rocket factory - has the unfettered right to run the software we, the noble proletariat of unpaid maintainers, lovingly craft in our basements at 3 a.m. Our highest ethical duty is to empower Jeff Bezos to instantiate yet another Kubernetes cluster that bills government agencies by the millisecond, for freedom means all users, especially those with yachts shaped like smaller yachts. Therefore, to deny Amazon the liberty to exploit our software without a cent of reciprocation would be to shackle the very essence of the Four Freedoms, for Freedom Zero is, and always has been, the sacred right of the richest man alive to squeeze the last drops of value from our volunteer patches while whispering “thank you for your contribution” into the abyss of a PR bot.

On a more serious note:

> I argue that the natural winner-take-all dynamics of the marketplace are not beneficial to the the mission of free and open source software.

Now, if said software was intended to run on users machines to actually empower the user, we wouldn't be in this pickle, wouldn't we?

I don't see Amazon freeloading off of GNOME, KDE, LibreOffice, Blender or GIMP.

No, I would argue the root cause of the problems here is that bros want to own their users (saas to the moon) and think open source is the way to do it. I say, fork those people!

As the author of Bear put in this very article:

> 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.

>

> Unfortunately over the years there have been cases of people forking the project in the attempt to set up a competing service.

Nowhere here is the intent for users to host the blogs themselves. No, he wants uses to use his service, not his software.

Fair enough, but that shouldn't have been open source in the first place. The author is just rectifying a mistake he made previously.

If the author had actually wanted end users to use his software, he wouldn't care who runs it. Look at Hugo, they're doing alright.

> enabling these companies to ensnare unsuspecting users

Well, to me, as a user, Bear is the company that ensnares me unexpectedly, because it tells me it's running open source but the minute I want to run it myself, oh no, I'm freeloading.

Whenever I see a project that requires a Kubernetes cluster to do something people would have in the past done in 15 files of C, I know they don't care about me as an empowered user in the "free software" sense. They see me as "a user" in a drug-addict sense.

F that.

[0] he never said that, obviously

Re: Bear is now source-available

#334

This isn't bear, the compilation database building cli tool, for those similarly confused.

Almost the same emoticon logo too.

ʕ•ᴥ•ʔ Bear vs. ʕ·ᴥ·ʔ Build EAR

The compilation database tool (https://github.com/rizsotto/Bear), is extremely helpful. It got CCLS/clangd working for me over multiple in-house build systems at a vfx studio.

It also is super helpful for debugging. I have used it a lot alongside a script which converts a compile_commands.json to a sequence of commands, so I can edit them individually without fiddling with the build system, and then once fixed (such as adding a flag to one TU) try to find the way to do that in the build system.

Re: Bear is now source-available

#335
post #209

Earlier quoted context omitted.

Most people have no problem with non-open source software. The gnashing of teeth comes in when projects like Terraform become successful specifically because they're open source , and then the maintainer changes to a closed source license that would have prevented the project from being successful in the first place. Doubly so when they relicense outside contributors' work with a closed source license because those c…

Sounds like we need a "forever open source" license. A commitment that any significant derivative retain the original (or some later version) of the original license. "Free to do whatever as long as it retains this license. A commitment that this license will not change, even by the original author". No special cases, just a blanket license for all derivatives. If it exists, what are the barriers to adoption? Why don…

I’d suggest the GPL family without a CLA as an approximation of that intent.

> If it exists, what are the barriers to adoption? Why don't we all use it?

My theory is that people in general don’t care that much, or (particularly in the case of corporations) consider permissive licenses to be ”freer” than copyleft.

Re: Bear is now source-available

#336
We open source every line of code we legally can at Distrust, and it has paid off in getting us work, even on forks, many many times.

Source code is cheaper than ever, so if you fail to open source first then an open source clone will be created, and your hard work will be irrelevant. Best to have the first open source mover advantage.

This move just told users you are selfish, and breaking the pay it forward chain of goodwill extended by all the developers of the open source libraries your code relies on.

You also just told everyone to park their content on a platform that now has a bus factor of 1, with no option to export and reimport to a compatible fork hosted elsewhere.

If your ability to make a living hinges on open source code like yours not existing, then you are already on too fragile ground to be sustainable, and this looks desperate and will just make more people leave.

Re: Bear is now source-available

#337
post #294

Earlier quoted context omitted.

It reads perfectly clear. It is designed to be a platform and mit license makes it too easy for other people to create competing services and they don’t want that. Maybe it was a mistake on their part to make it initially open source or it is bad that there are people looking to steal other people’s work

It's not possible to steal code, since the original author still has it.

It depends what it is used for. It is not so simple if they are profiting off it and you start profiting as well by stealing their customers. Maybe it is ok even then, but it sounds like it would be super annoying if the “thief” is just copy pasting the code without adding any value

Re: Bear is now source-available

#338

Earlier quoted context omitted.

It reads perfectly clear. It is designed to be a platform and mit license makes it too easy for other people to create competing services and they don’t want that. Maybe it was a mistake on their part to make it initially open source or it is bad that there are people looking to steal other people’s work

If you don't want your work to be "stolen", and instead want to force the people to contribute back, use the AGPL

[deleted]

Re: Bear is now source-available

#339

Earlier quoted context omitted.

The problem with GPL was "tainting." It was never clear in what cases you could use GPL without it dragging all your code into being freely available. LGPL was supposed to help with that; AGPL made it even worse. The lawyers were terribly confused and recommended you just not use anything with "GPL" in the license. The reason why MIT/BSD licenses flourished is that they were easy to understand. As long as you didn't…

GPL also gets incredibly ambiguous when it's applied to anything that isn't software written in a language like C for a personal computer. (What does "linking" even mean with respect to a Javascript library, for instance?)

Exactly. I was building a WASM lib using Emscripten and this was the exact question I could not answer

Re: Bear is now source-available

#340
post #285

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 original stance of the open source crowd..... >The proliferation of "give everything away for free" MIT/BSD/Apache licenses... Interesting how the world have changed. The so called GPL preference, or GPL > GPLv3 > AGPL among Open source crowd is a recent thing. Arguably in the last 15 to 20 years. Both BSD and MIT dates back before GPL. And you will see far more people prefer BSD and MIT in the 90s and 00s. I ha…

> And it used to be very cool if your OSS project get used by a big company, until it is not.

Yup. Open source advocates would brag about adoption in enterprise. They would incessantly argue about how safe open source is compared to close source and would constantly complain about stupid managers not allowing open source.

Not all of them, but that stance was predominant when I was younger.

Post reply on HN