Ferk

someone painting him as a morally righteous

The first thing @seSvxR3ull7LHaEZFIjM said was: "Assange is a bit of a scumbag" ...

The closest thing to "righteousness" said was: "his efforts for freedom of information should not land him in US torture prisons like many others."

Which, being true, it's absolutely not challenged or contradicted by anything you said in response.

Note that "freedom of information" is totally compatible with "picking and choosing" the manner in which you exercise that freedom. In fact, I'd argue that the freedom of "picking and choosing" what's published without external pressure is fundamentally what the freedom of press is about.

Assagne (like any other journalist) should have the freedom of "picking and choosing" what facts he wants to expose, as long as they are not fabrications. If they are shown to be intentionally fabricated then that's when things would be different... but if he's just informing, a mouthpiece, even if the information is filtered based on an editorial, then that's just journalism. That's a freedom that should be protected, instead of attacking him because he's publishing (or not publishing) this or that.

The packager always should "explicitly require" what are the dependencies in a Nix package... it's not like it's a choice, if there are missing dependencies then that'd be a bug.

If the package is not declaring its dependencies properly then it might not run properly in NixOS, since there are no "system libraries" in that OS other than the ones that were installed from Nix packages.

And one of its advantages over AppImages is that instead of bundling everything together causing redundancies and inefficient use of resources, you actually have shared libraries with Nix (not the system ones, but Nix dependencies). If you have multiple AppImages that bundle the same libraries you can end up having the exact same version of the library installed multiple times (or loaded in memory, when running). Appimages do not scale, you would be wasting a lot of resources if you were to make heavy use of them, whereas with Nix you can run an entire OS built with Nix packages.

Huh? as far as I know it has its own libraries and dependency system. What do you mean?

The nice thing about Nix/Guix is that each version of a library only needs to be installed once and it wont really be "bundled" with the app itself. So it would be a lot easier to hunt down the packages that are depending on a bad library.

Flatpak still depends on runtimes though, I have a few different runtimes I had to install just because of one or two flatpaks that required them (like for example I have both the gnome and kde flatpak runtimes, despite not running either of those desktop environments)... and they can depend on specific versions of runtimes too! I remember one time flatpak recommended me to uninstall one flatpak program I had because it depended on a deprecated runtime that was no longer supported.

Also, some flatpaks can depend on another flatpak, like how for Godot they are preparing a "parent" flatpak (I don't remember the terminology) that godot games can depend on in order to reduce redundancies when having multiple godot games installed.

Because of those things, you are still likely to require a flatpak remote configured and an internet connection when you install a flatpak. It's not really a fully self contained thing.

Appimages are more self contained.. but even those might make assumptions on what libraries the system might have, which makes them not as universal as they might seem. That or the file needs to be really big, unnecessarily so. Usually, a combination or compromise between both problems, at the discretion of the dev doing the packaging.

The advantage with Nix is that it's more efficient with the users space (because it makes sure you don't get the exact same version of a library installed twice), while making it impossible to have a dependency conflict regardless of how old or new is what you wanna install (which is something the package manager from your typical distro can't do).

From the actual regulation text:

the concept of ‘illegal content’ should broadly reflect the existing rules in the offline environment. In particular, the concept of ‘illegal content’ should be defined broadly to cover information relating to illegal content, products, services and activities. In particular, that concept should be understood to refer to information, irrespective of its form, that under the applicable law is either itself illegal, such as illegal hate speech or terrorist content and unlawful discriminatory content, or that the applicable rules render illegal in view of the fact that it relates to illegal activities. Illustrative examples include the sharing of images depicting child sexual abuse, the unlawful non-consensual sharing of private images, online stalking, the sale of non-compliant or counterfeit products, the sale of products or the provision of services in infringement of consumer protection law, the non-authorised use of copyright protected material, the illegal offer of accommodation services or the illegal sale of live animals. In contrast, an eyewitness video of a potential crime should not be considered to constitute illegal content, merely because it depicts an illegal act, where recording or disseminating such a video to the public is not illegal under national or Union law. In this regard, it is immaterial whether the illegality of the information or activity results from Union law or from national law that is in compliance with Union law and what the precise nature or subject matter is of the law in question.

So, both.

Were the earlier series not focused on shared values to more or less a similar extent too?
Kirk has usually been given the reputation of being a rule-breaker, often ignoring Starfleet rules when they are in conflict with his values. Even off-camera (in DS9 I think) they attribute him 17 temporal violations, and I think he has been accused of violating the prime directive multiple times.

+1, either cull them from the union or cull them from the free trade deals.
What makes no sense is to let them decide to not enforce the EU rules while at the same time treating them as if they are a valid compliant member when it comes to trading with other countries in the union.

Yes.. honestly, I don't see this approach being worthwhile...

It's better to search for full open source alternatives, front end and backend... like Lemmy/kbin for or reddit, peertube/lbry for YouTube, etc.

But C syntax clearly hints to int *p being the expected format.

Otherwise you would only need to do int* p, q to declare two pointers... however doing that only declares p as pointer. You are actually required to type * in front of each variable name intended to hold a pointer in the declaration: int *p, *q;

That's even harder. Specially if we aspire to have a community that protects privacy & anonymity.

Keep in mind "rich" does not necessarily mean "famous".
For all anyone knows, you and me could be part of the wealthy, yet nobody here would know, no online service would deny us service. Being forced to live an anonymous and private life is not really much of a punishment, at least it wouldn't be for me... if I were part of that wealthy I'd just lay low.. I'd get a reasonably humble but comfortable house in a reasonably neighborhood where people mind their own business, dressing modestly and living life without having to "really" work a day of my life, while my companies / assets / investments keep making money so I can go on modest trips and have some nice hobbies that are not necessarily really that expensive anyway. Anyone who figures it out, I set them up. It'd still be worth it to live that life.

I feel it's a balance. Each operation has a purpose.

Rebasing makes sense when you are working in a feature branch together with other people so you rebase your own commits to keep the feature branch lean before you finally merge it into the main branch, instead of polluting the history with a hard to follow mess of sub branches for each person. Or when you yourself ended up needing to rewrite (or squash) some commits to clean up / reorganize related changes for the same feature. Or when you already committed something locally without realizing you were not on sync with the latest version of a remote branch you are working on and you don't wanna have it as a 1-single-commit branch that has to be merged.

Squashing with git merge --squash is also very situational.. ideally you wouldn't need it if your commits are not messy/tiny/redundant enough that combining them together makes it better.