It would make sense to require a company to release the code for players to host their own servers, which has been done by many games in the past. Not to continue to run it themselves.
That counts as “working state”, assuming the published code is reasonable to operate (it must be FOSS, or at least permit open modification and distribution; and it must run in a server with specs that’s reasonable to have at the time of game publication)
Because to import old content, you have to respect the old license (or get every contributor of back-then to relicense). That would mean having a site with contents under differing licenses depending on date, which is something the corpos can use as an excuse to continue siphoning everything without consequence.
I’m fine with a mirror / archive of SO. But it shoudl very definitively be a different thing than an active SO alternative, and their users and data storages should be also different.
I said alternative to SO. As in, likely, a place to post new content (answers, comments). Nothing can really be done with the content OAI already got their hands on other than firing off a few well-placed EMP bombs.
Me dan risa todos los idiotas que se la han chupado a El Musko con los cybertruck. Literalmente es un ladrillo con ruedas pintado, no muy diferente a los juguetes de los niños en los años 60 excepto que más caro. ¿Qué más esperaban?
Feel free to explain then, because from here it looks like El Trumpo should have been thrown to jail 8 contempts ago, like any normal citizen. Right now if I was a US citizen I would be justified in citing precedent that I can’t be sent to jail or even threatened with jail time with only 6 contempts.
See here’s the thing: Creative Commons is not an exclusionary license. If I want to make commercial use of something that has a CC-NC license, I explicitly can ask the author for a secondary license limited to the usage and scope that I need. The important thing here is that the author still retains control, as well as a data point of who is profiting from their stuff and how.
And no, it wasn’t just the favicons feature that was removed (which like … is that really such a big privacy issue that you need to remove it from the binary?)
Fetching a favicon means raising a network connection with a predictable endpoint. That’s already three concerns (four on the modern internet) to handle security-wise, and it’s absolutely an unneeded feature. Favicons could just be shipped on something like keepassxc-data or keepassxc-contrib to handle locally, no need to raise a network call.
Storm in a teacup, as tends to be the norm on the internet.
Not only this is nothing new and nothing unexpected to happen in Sid of all places, but it’s also something that helps bring keepassxc more in line with packaging guidelines on Debian. They already have lots of packages, both of the mutually-exclusive kind and of the complementary kind, with “foo-full”, “foo-minimal”, “foo-data” etc naming. p7zip and nginx of all things are quite interesting examples.
Plus, the author of the post sensationalizes the title to brigade the issue.
All that said:
If the maintainer wishes to do this, “only” having two packages is a half-assed measure and that causes more issues in the long term. I’d expect three packages: keepassxc-minimal, keepassxc-full and the retained name keepassxc as a virtual package name.
Furthermore, a direct upgrade path should go from (previous) keepassxc to (proposed) keepassxc-full.
I don’t know enough of KeePassXC to know if something like keepassxc-data would be needed. Are there potential cases where one would want to switch between “-full” and “-minimal” or viceversa without the system seeing a software uninstallation in the meantime?
The “crap” rationale is definitively something we all can do without, but given how people tend to brigade developers who try to do things, I can completely understand and support raising shields and looking defensive because some damage is already going to be done.
Most responses are right in that the right place to discuss this is in the opened Debian bug report. The entire point is to see Debian (not KeepassXC) handle this before things get to Next Stable.
People who are looking to start a SE alternative but start with the idea of importing the original SE data dumps are already Doing It Wrong. Much of the issue that has led to the desire to fork SE comes due to the license of the posts and content, which lacks the NC (NonCommercial) component of Creative Commons. Without that component, any attempt to make a Fediverse alternative just ends up in Yet Another Endpoint that can be freely siphoned for data by corporations, for AIs, etc.
So, if I am understanding correctly, as a citizen I can threaten a judge 9 times, or threaten 9 different judges, and demand that I can only be held accountable for only one of them, or for all of them as a package only once?
La verdad esta noticia ha ido de mal en peor. Ciertamente un Antuco 2.0 y espero que conduzca a un cambio importante en la forma y la razón por la cual se entrena el servicio militar.
No están entrenando para la guerra y si lo estuvieran deberían estar usando capitalistas de blanco, no hay razón que resista lógica alguna de exponerlos al tipo de riesgo que implica una marcha del tipo de la de Putre, en las condiciones ambientales de Putre, con un “profe” al que le importa un vinilo en al raja sus vidas y con un sistema que no respeta ni la objeción de conciencia ni la capacidad de los reclutas de evaluar sus propias condiciones de riesgo.
Correct me but any pregraduate law student who hasn’t been skipping on their classes could get rich by filing for the obvious bias the judges have to allow 10 contempts of court, wouldn’t they?