I use SpeechNote from flathub, which can both translate text between several languages offline, it also has good speech to text and text to speech capabilities.
Tl;dr: Use a dictionary instead. Machine translation isn't really the correct tool to translate single words.
Maybe check if one of the other instances on the web get it wrong, too. For example you could try: https://libretranslate.com/
From experience I can say libretranslate isn't as good as Google Trabslate. Especially with figures of speech or single words.
To translate single words, a dictionary works way better. And it gives you several options. So you can choose depending on context.
For translating longer text, I think AI will be the future. I think it already outperforms Google Translate. But I'm not aware if any local AI solution that'd replace Libretranslate (as of now).
It definitely can't compete with a multi-billion dollar corporation. You might have better luck with using a Google Translane frontend such as Lingva. Lingva Demo
I noticed that the quality of translation is varying a lot between the languages. Polish for example is very poor in Libretranslate, while Portuguese is quite good.
I think you might be closer than Bruce Perens to a license that more people would be willing to use. However, they explicitly name and define machine learning model training as a prohibited use of the covered work.
There's so much to read that I haven't already. I think real democratic control of a license could be good. Though, I haven't taken time to understand the governance structure of it.
However, they explicitly name and define machine learning model training as a prohibited use of the covered work.
This doesn't immediately sound bad to me.
I'm not informed on software law. As an example, my understanding from Oracle v. Google is that Google received a ruling from the Supreme Court around 2020 that stated their copyrighted use of a public API, like the public side documentation side of method calls could not be considered a violation of copyrighted works. The idea that they could use machine learning on the internal code of methods and use it to write their own version from the the start of the method call doesn't exactly seem like a good thing to allow.
Though, this is a really uninformed opinion. I haven't read any of it in detail. The public opinion is usually on Google's side. I'll leave an excerpt.
Now let us consider the example that the District Court
used to explain the precise technology here. Id., at 980–
981. A programmer wishes, as part of her program, to de-
termine which of two integers is the larger. To do so in the
Java language, she will first write java.lang. Those words
(which we have put in bold type) refer to the “package” (or
by analogy to the file cabinet). She will then write Math.
That word refers to the “class” (or by analogy to the drawer).
She will then write max. That word refers to the “method”
(or by analogy to the recipe). She will then make two pa-
rentheses ( ). And, in between the parentheses she will
put two integers, say 4 and 6, that she wishes to compare.
The whole expression—the method call—will look like this:
“java.lang.Math.max(4, 6).” The use of this expression
will, by means of the API, call up a task-implementing pro-
gram that will determine the higher number.
In writing this program, the programmer will use the
very symbols we have placed in bold in the precise order we
have placed them. But the symbols by themselves do noth-
ing. She must also use software that connects the symbols
to the equivalent of file cabinets, drawers, and files. The
API is that software. It includes both the declaring code
that links each part of the method call to the particular
task-implementing program, and the implementing code
that actually carries it out. (For an illustration of this tech-
nology, see Appendix B, infra.)
Now we can return to the copying at issue in this case.
Google did not copy the task-implementing programs, or
implementing code, from the Sun Java API. It wrote its
own task-implementing programs, such as those that would
determine which of two integers is the greater or carry out
any other desired (normally far more complex) task.
This isn't all that relevant, and there's lots of case law. It just seems slightly frustrating to me that the law might allow 1) a company to use copyright software for learning 2) take public methods, and their supporting documentation 3) and finally use them inconjunction with a prompt of the documentation to generate the internal code.
This all is a very unresearched or serious view of it. For whatever reason, I just was already thinking about it. It's all to say, I think I understand the argument for disallowing machine learning use. I haven't really decided where I align. I think it's really valuable that we can automate anything, but I also feel negative to the idea of signing everything over to the tech companies and hoping for the best.
All of my projects are on Sourcehut. So all of my projects are automatically excluded from your narrow definition of "open source projects" worth supporting. So are all projects on gitlab, or... anything but github. Your license sounds more like a mechanism for promoting a monoculture and incentivizing developers to host on github.
Say my library uses a library that uses your library. Is your license more infectius, like the GPL, or parasitic? Do all projects using your library have adopt your license, or include it?
All of my projects are on Sourcehut. So all of my projects are automatically excluded from your narrow definition of “open source projects” worth supporting. So are all projects on gitlab, or… anything but github. Your license sounds more like a mechanism for promoting a monoculture and incentivizing developers to host on github.
I don't disagree. I don't really know how to fix the problem in what has been considered without an extra organization that does some form of identity verification and then collects votes on open source from anywhere on the internet.
The only reason GitHub was selected was because it's easily recognized and the metric is understood
Say my library uses a library that uses your library. Is your license more infectius, like the GPL, or parasitic? Do all projects using your library have adopt your license, or include it?
Anything that depends on it would be including it in something else later. I was considering anything that used it that made income had to pay 5% royalty. A library that uses a library that uses a library with it would had to pay 5% on income made with the final library. Though, I don't necessarily have an opinion on requirements of the license of the final library. I also wasn't considering open source restrictions like the GPL.
This would be something that would be a deciding factor for me. I don't have a solution, either, but it would need to be addressed before I'd consider something like this.
A library that uses a library that uses a library with it would had to pay 5% on income made with the final library.
But my library is MIT, and free. Can I use a library that uses a library that uses your license? Either your license considers itself incompatible with the other licenses, meaning it's virulent like the GPL: my library must use your license, because it uses some library that uses your license; or there's a clause that says it must be included with incompatibly licensed software, in which case it's parasitic: someone could still clone my library, replace the dependency that uses your license with some other library that doesn't - remove the parasite, so to speak. In the latter case, I could still BSD-3 Clause or MIT my library, with a big ol' warning in the README about your license and the implications.
or there’s a clause that says it must be included with incompatibly licensed software, in which case it’s parasitic: someone could still clone my library, replace the dependency that uses your license with some other library that doesn’t - remove the parasite, so to speak. In the latter case, I could still BSD-3 Clause or MIT my library, with a big ol’ warning in the README about your license and the implications.
A clause for being included with incompatibly licensed software would likely be my preference given the other doesn't have more support. My first impression is that having people use it is more important. A goal of the license being to make it overwhelming to escape because it is everywhere.
This is the GPL philosophy, and it's why people call it viral (and also why many people don't like it). But there's precident in the GPL, so if that's what you're looking for, the GPL might make a good model for your wording.
I love this idea. I feel like a shakeup with licenses is needed. I wonder if you could consult a lawyer then ask some larger open source projects if they would be willing to adopt the license?
If it's identical to GPL or MIT for small licenses, but forces corporations to give back to the community, it's only fair.
I love this idea. I feel like a shakeup with licenses is needed. I wonder if you could consult a lawyer then ask some larger open source projects if they would be willing to adopt the license?
Contacting authors of repositories seems really smart. I imagine it could be possible to contact a large percentage of them. I just want to be confident that I have a good license that will be liked before I make an attempt.
edit: Though, looking for feedback from them might also be a really good idea
I think it's a great idea. Forcing commercial entities to contribute monetarily back to the opensource world? Awesome. If such a license existed, were legally applicable, and infectious like the GPL (as in code built on top of it should also be non-gratis opensource), I'd write all my code in it.
Of course you have to think of the loopholes e.g it shouldn't be possible to donate to something you own either directly or indirectly, that would defeat the purpose. I can't think of other stuff, but this is probably where a lawyer comes in.
Honestly, what you could do is:
set up a poll and share the link far and wide (here, mastodon, and if you use commercial services like reddit, insta, facebook, etc. then those too)
go to a lawyer
set up a patreon, liberapay, gofundme, or whatever with the purpose of getting this license written (I'd donate)
make a repo with the license and share progress (this is a perfect usecase for change tracking)
You could also contact the people at https://creativecommons.org/ . Maybe they could help you with finding a lawyer versed in this stuff. It's doubtful Free Software Foundation would help, but you can always take a shot.
Thanks for putting thought into this. I'm with you that commercial entities should pay for opensource if they use it. All of them.
If I continue, I would like to do something like the following
The group that this targets, software developers, I don't think we're difficult to contact. There's usually personal websites or email addresses associated with accounts. I think it could be possible to survey a large randomized sample, above 10,000 developers who have contributions to highly appreciated repositories.
There would have to be some cut off for who to select. I think I would like to focus on developers who are planning on licensing software, as in, they're already demonstrated they're writing licensed software. This is all to say, I don't want to haphazardly screen the general public opinion.
In this post, I noticed that those responding seemed to slightly skim over or misunderstand parts of it. This is partially a communication failure for me, but also seriously hinted to me that asking with text about licensing details seems like it could be a bad idea. I think like a video that first covers topics followed by a survey might be better, but I'm worried something like that will bias those that I ask.
Before all of this, before I talk to a lawyer, I want to think about all possible restrictions or options available. This is where I think comitting to a git repository would be a very good idea. Just making an attempt to determine everything that is relevant, because there are clear differences in how a license should work.
After that, I can consult to determine what is and isn't possible. And from there, I'm hopeful that it's possible to carefully survey and understand opinions on what more developers and companies would like to see in a license.
I don't want to accidentally create a license that becomes stuck and is extremely damaging. I want it to serve those that are using it in a way that makes them happy.
I'm still not 100% committed to this yet, but feel good about the responses here. I was worried the responses would be highly negative, as it's something that takes very unrestrictive software and tries to convince the authors to charge for it. I'll have to think about what I want to do some more.
I don't really care if they use it. I think overtime it could be possible to move a large chunk of software over to a royalty based license. It just has to seem like a good deal to developers, and they'll move.
If you want developers to use your license, you should work on why a commercial product like GitHub is used to judge popularity, why popularity is useful and what about small projects, and how can projects receive money (in France it would be an administrative pain in the ass because of taxes and stuff).
I see what you're saying now. I would not use this simply because profit is an unreliable measurement. A revenue based test makes more sense. Possibly adding an investment valuation test as well. Since many VCs encourage no initial revenue when they fund startups.
I think revenue seems easier to enforce too. Just revenue didn't really make sense in the context of what I was doing, as people are writing contracts that handle millions of dollars and collecting like less than half of a percent. It's just confusing. It does make sense when the business is creating iOS or Android Apps and selling digital items, etc. I think the license could be restricted to business category, it's just more to consider, and a lawyer would probably really understand it.
I'm not exactly sure what is meant by investment valuation tests. As an example, is the investment valuation supposed to be something like "the financial contribution to this repository cannot be more than 5x the estimated cost to contract the entire source code by a reputable institution?"
Oh. I thought “it” was your software project.
Yes, I want to use a custom license for my project.
I've also wanted for a while to create some type of distributed royalty license, but the level of effort I want to put into that is just dependent upon how much potential there is for it to be successful. I haven't decided on what I will do yet for my own project. I think the main issue is it's just difficult to find terms that are not hard to understand and people readily support.
I’m not exactly sure what is meant by investment valuation tests. As an example, is the investment valuation supposed to be something like “the financial contribution to this repository cannot be more than 5x the estimated cost to contract the entire source code by a reputable institution?”
I mean a test for the latest round of funding of the company establishes a value of the company and if that value is over $x, the terms apply. Fir publicly traded companies, you could just use market capitalization.
I responded here to @onlinepersona detailing how I might try to continue finding terms that are highly approved. I think what I've thought about so far isn't very carefully considered, so before I try to choose a specific license, I want to take some time to think about more options.
I really like text. I sometimes read documentation multiple times over before considering asking a question. I don't assume I am correct, and try to verify that I'm not wrong before finally asking a question. Though, other times, I'm guilty of skipping or skimming over text.
The problem I felt like I was having was that I was attempting to describe many complicated rules with as few words as possible. I felt like if I didn't try to limit words, other people would not read it. Even with all of this, it felt like many people who were responding were still not really reading it. In a survey, I might try to cover multiple contract styles, in text, it could be lots of words. The concern is that the importance of the topic will be missed to someone completing a survey.
Maybe a combination of both would be better? Like provide as much text as I want, and also a video with it. I still have to think about it.
A text post on [email protected] is going to have people skim. A link post on [email protected] to a blog or webpage with a summary of intention posted in the body of the link post would get people in a better mindset to read the detail at the linked blog post.
I think you told a story from your perspective rather than introducing your idea from the perspective of trying to get the attention of a potentially interested audience that is in a casual browsing mindset. As a result, people were trying to skip past your story and get to the meat of the idea which wasn't presented concisely.
I also don't think I entered with clear goals. Am I designing a license or trying to find a license to use?
I've seen language design blog posts here and on reddit. These are usually long, but with the intent of creating a discussion. I don't think I was even intending to create a discussion or reach an audience. I just was looking for approval of the idea. I think there's always going to be some amount of people that will skim, but stating that text is the issue is wrong, text does not stop productive conversations or creating something.
I think there's also the difference between law and software (outside of machine learning) in that there's also some level of interpretation when the subject is about a spectrum. Like when does yellow become green? I felt like I was stating lots of information that loosely goes together, and it was not concrete or solid in understanding.
I don't expect legitimate companies earning over $1m/year to just flat out violate the license. I do think they might try to dodge amounts owed with accounting, but Epic seems to find this business model viable with Unreal Engine. I'm also not going to signficantly care if it's violated, the fact that they're legally obligated to pay seems better than just giving it to them for free with a more permissive license.
I cannot speak to how their business works or if they are considered non-exploitive. However, I know their framework is super-common in the digital music world.
I'm not actually interested in charging money for myself though. The point of the license is more so to create a license that is compatible with others using it and causes downstream users of it to also have to pay. Like I'm more so imagining a best case scenario where lots of source available software is available for 5% (like use all of it together too) flat on $1m+ in income. (And free for everyone else)
Opensource
Hot