I am a 23 years old vegan nyanya, System Administrator and Web Developer.
I hope it will make the people who want to use a GNU/Linux OS daily, do not think of the codecs as reason to not switch.
I see your perspective, but not the usefulness of your approach.
I prefer telling them how it works and that is a way to make actual documentation accessible. I also adapt my explanations to each person and situation.
It is preferable to have people who know how to use an OS and not being hanging around without knowing what to do because they expect even the most simple things done.
That said, codecs work great with Debian stock, so I am unsure about the issues you mention.
I use stock Debian.
No problems here.
In the case you use GNOME desktop and has issues with the deprecated AVI format still used in some playes and with GNOME Video app, just install libavcodec-extra or use GNOME-MPV (now named in another name I always forget).
The case for OpenSuse. In reality, they do the right thing given that is an European OS. It is illegal in some European countries to distribute several codecs by default given the copyright holders.
Instead of calling for a negation for their package management you should call for content distributors not using well-deployed and available open formats / codecs as well as the copyright holders of the propietary ones for putting these nonsense as rules.
Maybe integrating both?
To be exact, tagging would be useful a lot for me or similar.
Do you imagine using Lemmy as comment system for torrent-csv.ml over the torrents?
You can always use the web redirector that is now redirect.invidious.io/ in the case you want to use Invidious, however, my point also covers PeerTube instances.
A link shared to a web redirector doesn’t cut rights to anyone in that sense. And every working Invidious instance includes a redirector too in the button “use other Invidious instance” or something similar :3
There is a problem with this:
for example, if you are an old fashioned investor, you want to block instances with people interested in cryptocurrencies and NFTs
I could also have other reasons and in fact other reasons are the most shared idea in the environment where I am.
he or she will see…
I guess here is where this person stands even if made a reference to LGBTQ+ before.
One thing I see is that this person doesn’t explain abbreviations like EDPS or GDPR like if the reader was gonna to understand at instant. The second word, maybe, but not the first.
Maybe a bit strategic as the first would cause doubts about the ideas in the post given that is the European Data Protection Supervisor…
It is, but Andi is still in development
Then it is not yet. :/
It does not make it Open Source in the moment they claim it. Open Source has requirements stated already by OSI. It is or it isn’t and there is no middle term.
Open Source requirements imply the same for Free Software plus some additional ones.
It is a bit sad they are only available using yet another nonFree platform.
GitHub is propietary software (which goes agaisnt this community).
GitLab.com instance runs GitLab Enterprise Edition which is propietary. TeDoMun offers an instance using the Community Edition which is FLOSS.
I would recommend SourceHut (sr.ht) or Gitea (codeberg.org, git.disroot.org, etc)
I think you don’t understand what is even an inalienable interest, a right and which are the rights violated here. Yes, there is damage, in freedom.
There is no rare thing for hardware in H-Node working. I would like you to check it and availability. It is less, but it is not a rare case.
The option may exists based on such a list and any of the both sides would be affected negatively. In the same way it saves you time or impossibility in some cases, it would prevent my rights being harmed and save my time yet.
It would involve an initial effort in development, that is right. This would also help more for these rights that failing in the way is doing right now.
poVoq, I already explained how that works. Almost all the hardware can load it and it is done automatically, not based on an H-Node list to know if it works without it or not, which could be an option. If it is available, will be loaded and executed with compatible hardware.
Debian doesn’t have the fault for what the hardware vendors do, but has the fault for enforcing the situation when other options existed.
Including some optional firmwares in the install boot-medium infringes zero rights of yours and none of the 4 software freedoms are impacted by this.
Loading at boot time the firmware involves execution in applied hardware of software I have no power in.
Complain with the hardware vendors for making these firmwares a requirement if you will, but better not buy such hardware in the first place.
Doesn’t exclude that Debian did the worse thing. Options existed as I introduced before, and very obvious ones. If they needed help, I have no issues to provide it.
First of all, thank you for the clarification.
Related to the inclusion of the installer, that is not what they meant AFAIK. The idea is loading and executing it when applicable, even if it is not needed (RTL 8188EE is an example) as was discussed previously in other voting or mailing list which I need to check.
Edited: it is also supported because, in offers to load the firmware, you must do it at boot time for the initialization of the hardware.
If you think I am throwing a RTFM I think you are not even reading the first part of my comment. So, in order to understand me correctly, I recommend you to read it carefully part by part.
I don’t see how the second parragraph applies wrongly here.
About your edition, I am unsure if you understand how rights exist. A right, or mostly a natural right while not being guaranteed, is deducible from inalienable interests. These are interests born of aware individuals and are as basic as “I need to eat”.
In this digital world, other inalienable interests are born, and new rights deduced from them. The “4 freedoms” about the software are no more than a build of these rights in the same way the letter of the human rights try to do the same. That is all, no more complex than that.
Rights are also not based on claim. An individual should not claim every time they want their right guaranteed, that is plainly impossible with all individuals. Rights are guaranteed first and get available even before you need them.
By loading, trying and executing propietary software in the devices I use you are violating these rights.
There are manufacturers doing that? Sure. That makes my fight useless because I already could have that being executed? No and pointing to that is a Nirvana fallacy itself: “as you are in shit, doesn’t matter what you do because everything would be like that”.
First, you confuse firmware with drivers.
Second, I am annoyed because I see this as a lack of respect for my digital rights. There was option to maintain both images or showing visibility to the other one.
Third, projects such as H-Node show that integration and help with the ecosystem could have worked by showing compatible hardware in first hand.
Forth, Debian was never for newbies and not for that, but because people don’t read manuals. A different aproach would have been educational promotion of the existing Debian manuals before even downloading and even focusing on usability and accesibility to them. Maybe even creating simple English version or a reduced set by chapters.
Fifth, any user should know which hardware is using and get familiar with it. The out of the box concept many people promote leads to the believe of black boxes as solution. A mixed approach is also an option by using H-Node for example.
This could have contributed to the following:
In some places, such as Cuba, people make their own Debian mirrors.
General guide is in https://www.debian.org/mirror/ftpmirror and there are more instructions in the general script used.
Then you can point your /etc/apt/sources.list
to it.
Another option, suggested in other comments, is downloading *.deb
files manually for each package and dependency and performing an installation with dpkg -i package.deb
.
In a more specific approach, you have https://wiki.debian.org/DebianRepository/Setup.
Do you remember when you install a new Debian system and you can get packages from the CD ROM or USB stick? Debian can point to a repository in physical media, including a directory.
Generally, you can sync a hard drive with it outside with one of the tools available for this in this last wiki page, attach it to your puter when you arrive at home and party.
I would like to interject here for one thing: individuals of other species have autonomous lifes, and we would be only responsible in the limits on which we have to take care of them as if they were our children or similar, which is mostly when we adopt them because they have no place in human society in an autonomous way.
Sentience is a feature of all animal species known with only two exceptions, one being sponges and another I don’t remember.
This was already measured, using even unethical methods, several years ago and received ratification in 2012, even when this was known since a long time ago.
This is to complement of what you mean.
About sexy_peach, there is a point, even if is just centric in animal welfarism (not caring about their inalienable interests and natural rights but just what allows you to maintain your consciousnesses clean while maintaining exploitation) having the first part partially right.
It is not that responsibility is a human-made concept itself, but one that applies to you, being in a certain state of knowledge and awareness, as a moral agent (moral judgment), whether this is not the case of individuals from other animal species which are moral subjects (as most humans in their infancy and in some hard situations).
https://www.postgresql.org/docs/current/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-MEMORY
Can be configured in the main PostgreSQL configuration file. It has a default value that is too small for basic use case even.