This is a terrible idea. So of course it already exists https://c2pa.org/
It's already being exploited https://www.da.vidbuchanan.co.uk/...
We need a solution but that's not it.
@sh.itjust.works
This is a terrible idea. So of course it already exists https://c2pa.org/
It's already being exploited https://www.da.vidbuchanan.co.uk/...
We need a solution but that's not it.
Open source Not […] allow […] commercial applications
For some definitions of open source, this is contradictory (FOSS). Some non FOSS licenses do limit commercial use while making the source available, this could be a possibility for you.
But, I’d instead recommend that you check if a copyleft license such as the GPL provide enough protections for your use case.
Maybe look into PipeWire, Reaper in jack mode works fine connected to PipeWire for me, without any of the problems you mentioned.
It is quite possible that your desktop audio already uses PipeWire depending on your distribution, you would need to look at latency settings if you want live playback.
At some point, uppercase letters were written without accent in French. I'm unsure where this comes from, but I heard this was due to the limitations of printing presses, and then typewriters kept the convention.
In any case, the style is quite out of fashion today, but I know people who still write (handwriting and typing) without using accented uppercase letters.
I think google hides an additional mark in their own edits so the tool can perform an actual check in this case.
They would not detect any AI edit from other providers.
There are tools to remove these hidden "signatures" E.g. https://github.com/wiltodelta/remove-ai-watermarks
I'm not commenting on the ethics.
There might be an actual issue in your case, but this feels to me like https://www.linuxatemyram.com/
I’m expecting mapping will write a lot of map data to files in your world folder which might explain the apparent high ram usage. Try looking at disk usage while the issue occur maybe ?
Not how I understand it, but I'm not a lawyer. The user that uses the script to generate the code can copyright the output and oop can copyright their script (and the output they themself generate). If it worked like you said, it would be trivial to write a script that generates all possible code by enumerating possible programs, then because the script will eventually generate your code, it's already copyrighted. This appear absurd to me.
Relevant: https://www.vice.com/...
If the script copies chunks of code under the copyright of the original script writer, I typically see for those parts that the original owner keeps copyright of those chunks and usually license it in some way to the user. But the code from the user input part is still copyrightable by the user. And that's that last part that is most interesting for the copyright of AI works. I'm curious how the law will settle on that.
I'm open to counterarguments.
electrons actually loop around in a closed DC circuit in the speed of light
On average, electrons "move forward" much much slower than that:
https://en.wikipedia.org/wiki/Drift_velocity
But even the whole "electrical signal" is slower than the speed of light:
I'm not a researcher in this field, so I don't have anything substantial to suggest. My opinion is that it is unsolvable.
No matter what you try, sufficiently powerful entities will be able to modify the sensor to sign images of anything they want to pass as real (or just use a very high quality projector)
It might be better that we are all always weary of an image being AI at this point.
A rooted phone could not, but anyone with a bottle of acid and a microscope could. Or as I've said, a nice optics setup and a high quality projector.
My point being that trusting the camera chip does not help much. But, of course, it would block the easiest software attacks like we have seen so far.
First, thanks for working on Pharo, what an amazing environment.
I am not a lawyer so you should double check.
For GPL, indeed the image as a whole would be GPL. If the personal project is more of an “executable”, it might be what you are looking for, any further image modification would have to be released under the GPL as well.
If the project is more of a “library”, you might or might not prefer the LGPL. In this case I feel like https://www.gnu.org/licenses/lgpl-java.en.html would apply similarly to Java. As long as you can load the image and change the original library code, other code is not restricted on the license.
I've had to edit typst recently and I used
https://codeberg.org/meow_king/typst-ts-mode
And the LSP: https://github.com/Myriad-Dreamin/tinymist
Specifically for doom, you'd add typst-ts-mode in your packages.el in a package! entry and check either eglot or lsp-mode doc for how to configure the LSP.
Didn't try it but it looks like they also provide an installable offline version under the AGPL: https://github.com/ONLYOFFICE/DesktopEditors
If I understand your reply correctly (the output of free would be clearer), having 80% of RAM used as cache would indicate that it is used for caching files such as map and chunk data. This is normal in Linux, and the game would lag more without this feature. The link I shared explains it better than I can.
If you feel this is still not the case, you can share info such as free output, list of open files, etc, while the issue occurs.
thanks for using Leebra!
go to feed...