Oh, cool, they added that a few months ago; it only took them over 5 years to add it. I still don’t get why everybody likes it, it punishes you for building big and it has the slowest opening of all factory games I’ve ever played. I’d like to say I’d give it another try, but it runs like dog ass now, so I can’t play it anymore.
Is Satisfactory a franchise? I just don’t get it; it’s a worse Factorio. It’s poorly paced and it doesn’t have the tools you need to build big, like priority splitters.
Content ID is a major part of how copyright currently works.
It’s literally not a part of how Copyright currently works. It’s how Google automated copyright claims on their platforms.
None of my creative works are in Content ID. People are not being sued through Content ID. Content ID flags stuff and at worst removes it. It is up to the copyright holder to decide what they want to do.
No it doesn’t. It would work like Copyright currently works.
I don’t need my works to be in any database for them to be protected by copyright. I simply have to declare their license or have the license be assumed by not declaring it. That’s how it already works. You, the owner of the copyrighted works, has to sue the infringer. It’s not an automated process. Your ‘likeness’ doesn’t need to be in any database if you can prove they used your likeness. Content ID was an attempt by Google to automate the removal process on their platforms so they could wash their hands of the problem.
Is Google your government?
Do you also think all of your creative works are in a government database somewhere?
Yes, but you are mistaken if you think your data is safe on closed platforms.
If you post it on the internet, you have to assume it’s gonna be there forever.
LibreWolf is Firefox without the bullshit.
That’s awesome; I knew I’d seen it around!
what is that little pixel cat at the top? It also appears on https://katia.ripe.net/ is it referencing something?
reposotory
Firefox is in the same situation. Bloated umbrella org (Mozilla) that has dubious funding sources builds subpar products. Look at how much support implementing JPEG XL had, and how they just didn’t care and completely shut the conversation down when Google said no.
The Matrix foundation didn’t embrace and extend anything, as they were always in control of the spec.
EEE applies to when corporations (notably Microsoft) embraces projects that aren’t theirs and takes them under their wing, expands on functionality which attracts all the users and makes them the sole developer of that functionality, which kills the old, open forks. Microsoft then kills their version of it, and the whole thing dies.
and the backend is no longer fully open source
You have no idea how funny that is because I called it on a whim half a decade ago.
No; in the case of Matrix it’s because the spec is insanely bloated. Nobody wants to work on that, especially for free.
Not yet they haven’t
Instances have 3 options. Save it locally, proxy it, or do nothing. Saving every federated image is not feasible for small instances. It’s not a fault of the protocol that instance operators don’t want to pay a thousand dollars a month for storage. Matrix has this problem, and look what happened to them: tiny instances are expensive to run, so don’t flourish.
whatever die mad I’ll keep being more productive than I’ve ever been
You’re listening to hype bros when you should be listening to developers.
I’m sorry I hurt your feelings, that was not my intention, but I can’t interpret your message any other way, as all I did was say “I don’t like this popular thing”.
Also, no, look at the wiki. The priority splitters came out after 1.0.