- @Echedenyan@lemmy.ml
- deleted by creator
I am a 23 years old vegan nyanya, System Administrator and Web Developer.
- 9 Posts
- 139 Comments
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?
Source? Because as a local I can tell you there aren’t any. Please share all those reports of protests all over Europe /s I wish there were some proper protests against the astonishing levels of bad governance here, but currently it isn’t happening.
As a local, living in the Canary Islands and watching the news every day as the only channel I see on TV or reading the local newspaper or even seeing the posts in semaphores and lamps in street, I can tell you that, at least in Spain and near countries, is happening.
The news also show similarities in Germany. It is true that, sometimes, other news eclipse this a lot.
Edited: take this answer only as a reply to that part of the discussion and not anything else.
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:
- workarounds are not solutions. this is only good when there is no alternative but this is not the case.
- rights are not guaranteed by making the user work more to get their rights back and just masking the issue (privacy, free software use, etc)
- that workaround works around certain web browsers, but not all, specially if they don’t support webextensions.
- the “can go off-line” argument is a bit of personal undermining to the projects itself. There are plenty instances managed by organizations working as teams where this could be very difficult. You don’t need to be Google or Cloudflare to reach an acceptable support. In fact, I can ask with another reply following that logic: why are you using that Lemmy instance?
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:
- showing visibility to other projects working towards getting hardware work with free software.
- helping new users to find such a hardware instead of falling in the fallacy of “If you don’t see it, it doesn’t exist”.
- contributing to the digital illiteracy lacked by even medium range users of GNU/Linux family and almost all in a general sense using a computer.
- respecting the digital rights of people instead of making a false declaration of failure.
- this also derivates in being example for other projects towards getting or developing free software used in hardware such as firmware.
- you still fit the purposes of the other part by setting the additional image in the most needed cases.
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.
Maybe is it worthy to make a smooth change to this in the future? https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions
Unsure that everything is gonna be fine but the calendar.
This world has a dependency on slavery of non-human people, to the point that the average alien films is a representation of ourselves towards other species (we are really represented at some point as the aliens) but this is more obvious in newer films.
Ranting over wasted resources, hypocrisy and double moral
There is something I don’t get at all and that also annoys me a lot.
Like a month ago a homeless person in my village took a food can in a local supermarket and some people started to scream at him for it.
The other day, I saw, like in any other recurrent day, people presuming of the last computer setup they did and how wasting more than 600€ or even 280€ in a graphics card, makes it cheap for gaming purposes.
Of course, some of them were likely validating each other and giving justification why they didn’t get the last or similar, like if this was some kind of society requirement.
Sometimes, I see certain people promoting accelerationist practices in software by deprecating support for certain working hardware and even promoting the last version because some wished feature which is not needed. Breaking compatibility with current systems and increasing the time involved to reach it which most times is not assumable in resources waster for it.
For the first case, no people offered him to pay the can, even when they could at minimum, or put in their place for a moment. In fact, most of them were even buying commodity food.
For the second case, some of them are the very same people who ask later for donations and/or which are not willing to give a cent to help a certain person in need to have a computer to study or work as they consider they matter more than the rest and which they justify as a “need”.
For the third thing, these developers are not going to help or support you in the migrations if you are in need. At most, they will reply with a wontfix while telling indirectly that is your fault.
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.