That way you would be forced to keep it personal.. or suffer reduced sale price, as the new owner would need to backpay the minimums you were exempt from, or take on some risk merely leasing from you until the lock eventually expires - as you remain the true owner and all the payments and paperwork must cross your desk.

Purposefully making the distinction between things that are merely peculiar about German customs (old and new) on the one side, and things that are objectively the one true/correct/orderly way of doing things, and thus, must forfeit all claims of being "German". Many of the latter fall into the general categories of "rule of law" or "high-trust society", and once you compare how Denmark and Austria are doing, the most productive strategy is probably to stop attributing them to the peoples or states of Germany. And rather, consider them merely things easy to observe in Germany at this particular time. Use Germany as a spotlight to learn how to recognize how it looks and feels when they work, and more importantly: how to spot signs of them failing to work, then apply it globally. Und es mag am deutschen Wesen einmal noch die Welt genesen! Which is easier without bundling it up with customs that.. well.. would better remain localized to free state of thuringia.

We also figured out 20 years ago that SHA1 was not quite as strong as initially estimated, and not quite 10 years ago that generating two colliding documents was merely a matter of some serious computing power. A few projects went ahead and changed the name of their master branch, but SHA256 preference remains elusive.

While this may quantify how disruptive the change would be to those projects that are able to and do upload additional binaries to PyPI later, it fails to quantify how many projects already completely circumvent this block before it is even introduced.

e.g. If you tell pip to install from source.. the result may already be that you install a binary that PyPI never saw. A common hack for dealing with NVidia internals, which can explode into a large CUDA major version x GPU arch x platform x implementation x python_version cartesian product. The "extras" mechanism is not quite sufficient to model such combinations.

sample code: https://github.com/Dao-AILab/causal-conv1d/blob/4f6ae4e26ae5... https://pypi.org/project/causal-conv1d/

I order to know who actually requested it, information needs to be shared that previously was not. (I can think of technical schemes to limit this to less scary recipients and data, but however you do it, some necessary side-effect remains: Citizens of the EU who do not make such request cannot remain entirely unaffected.)

The negotiation is only necessitated by the insistence on making travel not a prerequisite for potential harm. The US requests to query information beyond the validity of documents they can prove to have been physically presented to US officers.

Never meant to be protected. I only contributed there because it specified in no uncertain terms that everything was going to be CC BY-SA licensed and posted in a public archive every now and then, so you do not need to scrape to use & redistribute if you intend to adhere to those terms. That would have been sufficient protection, if only governments had not u-turned from Walt-Disney-Copyright straight to "Open"AI-Copyright.

There was a few noteworthy company post, especially those after the mass layoffs / private equity takeover on the meta site that acknowledged the problem, so its certainly not a), even when you apply a strict standard about the terms in which to acknowledge the problem (which was well-known long before). Those company statements had some rather clear and well-received community commentary below that essentially questioned whether any of the suggestions on tackling the problem should even be tried. The very-much-not-welcoming onboarding experience, while it had great potential for improvements, was yet serving the sites unique needs quite well. Two weeks of persistence and reading the manual were not much of a detrimental filter.. not to those that would eventually go on to contribute back for many years. And those were the ones that ultimately mattered. Not those one-off solve-my-homework posts that only saw indifferent/annoyed moderation action. That probably still wonder why nobody took their hand and spent their evening guiding them through the steps necessary to make their post useful to anyone other than just the original author.

With a proper bank account, strong authentication with some dongle or code generator means if I have it, I can depend on being able to pay. No regard for the number of bots currently pestering them.

With PayPal trying to guess whether its me, maybe I can pay. Maybe I'll get a captcha loop. Maybe there will be a nondescript error message beginning with "Oops". Or maybe the error message will ask to call.. a rep that is not trained and/or authorized to do anything other than password resets. Which is not exactly a useful solution for account lockouts unrelated to the correctly entered, unique password.

I suspect besides objectively annoying flickering lights, the difference is primarily made in the immediate, subconscious and effortless recognition of ubiquitous patterns of function. Which happens in form and proportion first, and only to a lesser degree in color and contrast.

* this is the floor, this is the ceiling * through there, there is the entrance / exit * this is a reception desk

If it takes effort to filter out the noise, the glare to know such simple things, there is less capacity left in our brains to process other "essentially free" tasks.

So, we should make it easier to feed that reliability back upstream.

Probably the most useful thing you can do with these LLM-transpilations for now: If the transpiled version passes all original tests, I can run my application test suite against it and use it to discover test coverage deficiencies in the original!

If it crashes or otherwise observably misbehaves, I know the real project was missing regression tests for something. We could make upstream so much more resilient against accidentally breaking stuff in future updates, if only it becomes safe (offline + no side effects) and easy (if it crashes/locks, it is not from some memory safety bug from 25k transactions earlier) to run these transpiled projects as one row in our everyday integration matrix.