Open Source

30826 readers
1335 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
976
 
 

Writeup/video on a MIT licensed physics engine used in Horizon: forbidden west

direct links:

Jolt repository: https://github.com/jrouwe/JoltPhysics

An extension for the godot engine: https://github.com/godot-jolt/godot-jolt

977
978
33
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 
 

Recently, I was looking into licensing an open-source project I'm creating. My preferred license is the BSD-3, but was given advice that I should seek a license that offers patent protection as well. I saw there is a BSD 2-Clause + Patent option, but not one for the BSD 3-Clause, not that I found through OSI or SPDX. This seems odd to me, because I'm pretty sure the BSD 3-Clause is more commonly used than the BSD 2-Clause. Because of this, I've had to dual license my project as BSD 3-Clause AND BSD 2-Clause+Patent, which is a bit unwieldy, but achieves the same desired results.

This seems like an odd oversight though, I'd be curious if there's a reason the 2-Clause was chosen for the patent protection over the 3-Clause version? I could just add in the patent protection part to the 3-Clause version, but creating arbitrary licenses like that definitely makes me feel a bit... uncomfortable.

Edit: Due to some confusion as to what I meant, I wanted to add some details.

I'm definitely aware that licenses such as the Apache 2.0 exist, I just like the BSD licenses for their simpler language (and also don't have that odd state changes clause from Apache 2.0). I'm more so just curious why the choice was made for only the BSD 2-Clause license to gain the Patent Clause, but not the BSD 3-Clause version. That's what I'm not sure about, and why I'm curious about the logic behind this choice. I'm gonna paste in the content of both licenses below, since they are both short and easy to read and understand.

BSD 2-Clause + Patent

Copyright (c)

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Subject to the terms and conditions of this license, each copyright holder and contributor hereby grants to those receiving rights under this license a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except for failure to satisfy the conditions of this license) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer this software, where such license applies only to those patent claims, already acquired or hereafter acquired, licensable by such copyright holder or contributor that are necessarily infringed by:

(a) their Contribution(s) (the licensed copyrights of copyright holders and non-copyrightable additions of contributors, in source or binary form) alone; or

(b) combination of their Contribution(s) with the work of authorship to which such Contribution(s) was added by such copyright holder or contributor, if, at the time the Contribution is added, such addition causes such combination to be necessarily infringed. The patent license shall not apply to any other combinations which include the Contribution. Except as expressly stated above, no rights or licenses from any copyright holder or contributor is granted under this license, whether expressly, by implication, estoppel or otherwise.

DISCLAIMER

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

(Fun Fact: A lead developer on the Rust team said they would have chosen the BSD 2-Clause+Patent license if it existed at the time of them first releasing the Rust programming language. Instead, it's why they chose to dual-license under the MIT and Apache 2.0 instead.)

BSD 3-Clause

Copyright (c) .

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

979
 
 

Hey, I've been using collabora to edit/open some spreadsheets on android but it's honestly becoming a bit of a pain for me, freezing and blanking some cells being the big ones, and so I'm looking for an alternative. I tried excel without network access and it works but I do have to clear storage everytime to bypass the "signin prompt" that shows up randomly when opening a spreadsheet which disables editing, so I would like to avoid that too if it's possible.

980
204
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 
 

Is it just me or is passing off things that aren't FOSS as FOSS a much bigger thing lately than it was previously.

Don't get me wrong. I remember Microsoft's "shared source" thing from back in the day. So I know it's not a new thing per se. But it still seems like it's suddenly a bigger problem than it was previously.

LLaMa, the large language model, is billed by Meta as "Open Source", but isn't.

I just learned today about "Grayjay," a video streaming service client app created by Louis Rossmann. Various aticles out there are billing it as "Open Source" or "FOSS". It's not. Grayjay's license doesn't allow commercial redistribution or derivative works. Its source code is available to the general public, but that's far from sufficient to qualify as "Open Source." (That article even claims "GrayJay is an open-source app, which means that users are free to alter it to meet their specific needs," but Grayjay's license grants no license to create modified versions at all.) FUTO, the parent project of Grayjay pledges on its site that "All FUTO-funded projects are expected to be open-source or develop a plan to eventually become so." I hope that means that they'll be making Grayjay properly Open Source at some point. (Maybe once it's sufficiently mature/tested?) But I worry that they're just conflating "source available" and "Open Source."

I've also seen some sentiment around that "whatever, doesn't matter if it doesn't match the OSI's definition of Open Source. Source available is just as good and OSI doesn't get a monopoly on the term 'Open Source' anyway and you're being pedantic for refusing to use the term 'Open Source' for this program that won't let you use it commercially or make modifications."

It just makes me nervous. I don't want to see these terms muddied. If that ultimately happens and these terms end up not really being meaningful/helpful, maybe the next best thing is to only speak in terms of concrete license names. We all know the GPL, MIT, BSD, Apache, Mozilla, etc kind of licenses are unambiguously FOSS licenses in the strictest sense of the term. If a piece of software is under something that doesn't have a specific name, then the best we'd be able to do is just read it and see if it matches the OSI definition or Free Software definition.

Until then, I guess I'll keep doing my best to tell folks when something's called FOSS that isn't FOSS. I'm not sure what else to do about this issue, really.

981
 
 

I need to transport multiple very large files over an unstable and untrusted network, and the file contents are outputted as a data stream. I wanted to use OpenSSL for streaming authenticated encryption, but they purposefully don't support that and are preachy about it.

Well, it turns out that XZ has checksumming built-in! It even has different algorithms (CRC32, CRC64, and SHA256). It's part of the same file, within/before the encryption, and automatically verified by the decompression tool. I'm already using XZ for compression before encryption, so this is just super convenient and useful. Also, it seems like XZ supports threaded decompression now, when it didn't before. Thanks XZ devs!

982
 
 

Hi, there is a project called SongRec which is a Shazam client for Linux, but is there an open source Shazam client app for Android?

I know that I can use the official Shazam app, but the fact that I use a closed-source app, having almost all my apps open-source, that really bothers me 🥲

983
984
 
 

The BOINC Census is back for another year! 🎉 If you use BOINC ([email protected]), we want to hear your thoughts!

BOINC is an open source tool and protocol for volunteer computing which enables people to volunteer their computational power to scientific research like cancer research and mapping the galaxy.

Take the survey with the link below 👇

Should only take 5 min and your response could help shape the future of the community 😁

https://forms.fillout.com/t/n33grsgkeRus

The BOINC Census is a project of the Science Commons Initiative, a 501(c)(3) non-profit rebuilding the bridge of trust and participation between the public and science.

Happy crunching! 🚀

985
 
 

Do you know if there is any open hardware alternative for products like Roku, Chromecast, Apple TV etc. ?

986
987
 
 

cross-posted from: https://fost.hu/post/226135

Let's say, I create a bank with the caveat that all of my banking phone apps and webapps are FOSS (or if they depend on non-free components — banks probably do to communicate with each other —, then just OSS). Am I going to be behind the competition by doing this?

If the most secure crypto algorithms are the ones that are public, can we ensure the security of a bank's apps by publicizing it?

Are they not doing this because they secretly collect a lot of data (on top of your payment history because of the centralized nature of card payments) through these apps?

EDIT: Clarifying question: Is there a technical reason they don't publicize their code or is it just purely corporate greed and nothing else?

988
40
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 
 
989
 
 

bgammon.org is a free and open source online backgammon service without ads or tracking.

The following major changes have recently been released:

  • Sound effects were added
  • Support for additional languages was added
  • Click-to-move support was added
  • Legal moves highlight feature was added
  • Spectating matches is now supported
  • Pip counts are now displayed
  • Mobile device support has been optimized

The first AI opponent, wildbg is also now available (look for "BOT_wildbg's match"). wildbg is written in Rust, and is powered by neural networks. Can you beat it?

Join the bgammon.org community via Discord, Matrix or IRC at https://bgammon.org/community

990
991
 
 

This is a fork of QKSMS which is not maintained anymore: https://github.com/moezbhatti/qksms/issues/1970

992
993
994
72
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 
 

It's an easy to use web GIS. Looks quite cool actually.

995
996
32
HyperbolaBSD (hyperbola.info)
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 
 

FSF approved distro (now Linux based soon with own FLOSS-BSD-kernel)

Do you want to participate? (esp. BSD-kernel-dev would be very welcome 😁)

997
998
 
 

cross-posted from: https://lemmy.world/post/8237599

At Framasoft, we're trying to push back GAFAMs' toxic web by multiplying digital-friendly spaces.

Find out more about our actions and how you can support us: https://framablog.org/2023/11/14/lets-regain-ground-on-the-toxic-web-framasofts-2023-report/

Our 2022-2025 roadmap "COllectivize INternet / COnvivialize INternet" is represented by Coin-Coin, who is reporting on this first year's work.

Help him to push back against the Datavöre by sharing https://soutenir.framasoft.org

999
131
Distrochooser (distrochooser.de)
submitted 11 months ago by [email protected] to c/[email protected]
 
 

There are countless Distros that do not always make it easy to choose the one that best suits each person's needs and knowledge. This page, through a small test, proposes the Distro or Distros that best fit.

1000
view more: ‹ prev next ›