I am a 22 years old vegan nyanya, System Administrator and Web Developer.
You also even upgraded to a recent Debian Sid-based Ubuntu release.
BugUbuntu 22.04 cannot even be considered LTS given that they just got software from Debian unstable release branch.
I still don’t understand why BugUbuntu developers do this, being always basing their releases in a snapshot of Debian unstable release branch and just upgrading LTS ones at all until software gets frozen while still promoting it during this time as a full release and LTS.
Where you could not see it? in a Docker container using default Docker images for several OSes including Debian family. But you don’t usually check man there but in the outside OS in which you edit the source code containing that README in order to prepare your custom Docker container or image with it.
That was there. I recognized this in Docker.
Howerver, in Docker, Alpine is not the only nor the main provider of images nor almost the main used.
There are quite a lot based in Debian as I use it even as base for custom images and download images using it.
Please, don’t use aggressive language here, no-one is attacking you.
There is no such thing as markdown Reader. Markdown can be read by cat command.
For the first thing, there is but I put it explicitly in Woefucks section.
For the second, you can also use a cat
to read a README
written in groff
and the result could be similar to reading a markdown based one, which is having difficulties to differenciate some sections which could be debatable because it is true that markdown is simpler and most HTML tags for extension purposes are known by some people.
It doesn’t. See the link i posted in previous reply. Also windows.
Discarding Woefucks here as it was covered before, yeah, they come. Most server OSes are custom images by IaaS providers with them.
Main OSes in servers also come with it as result of main software used, and other times as secondary software in dependencies.
Best example are Red Hat and Debian families. Suse one can also come with it. I work on this.
Where you could not see it? in a Docker container using default Docker images for several OSes including Debian family. But you don’t usually check man
there but in the outside OS in which you edit the source code containing that README
in order to prepare your custom Docker container or image with it.
In production servers, you don’t usually install anything you don’t need to run the services as it increases the attack surface.
However, manpages is something that comes preinstalled in most server OSes with a few cases out there.
Sometimes it also comes as dependency of one of the software you need to install by default so, these little cases are even less.
And, applying the own definition to “install what you need” you would need the man pages and you would install it and it comes in the OS so this doesn’t even make sense.
About the example of Woefucks, I don’t think that is an example of a case which doesn’t as it also doesn’t come with Markdown reader preinstalled and, in any case, doesn’t matter at all.
Coming from a family with members having issues with addiction, one of them being my intelectually disabled brother for which companies have no mercy in their games and ads, I don’t see how these little benefits over maintaining people on a routine are reliable enough to maintain a behaviour that can be abused easily and, specially, when people get used to it.
Thankfully, I am not the only one knowing that.
https://github.com/wger-project
You also have the application in main F-Droid repository.
About the gamification:
That will be difficult to be seen in independent projects as the idea behind it is to make people using the service or app adicted to it.
This makes easier for non-ethical services to maintain a fixed userbase to get unlimited income.
First, the kind of war you try to represent with public domain and copyleft is not, in anyway comparable.
Public domain content doesn’t have almost any kind of protection agaisnt some entity (personal or not) claiming property.
In copyleft world, you don’t have only to rely in yourself, you can create a collective, organization or rely in third party collectives dedicated to that, which exist and are not a few.
The “lore” gets closed in that world since the moment that a propietary copy gets famous and doesn’t contribute back to the original, which, in fact, has no central point of avaliability but it is almost a just 1-release version that in the moment you stop, it will become difficult to track.
Here I see confusion between openness and freedom.
The freedom is in the possibility you have to get each avaliable option, and not in the number of options which is the case in openness.
In the moment that there is a possibility to choose an option which prevents choosing the rest, the freedom is gone.
Do you want avaliability almost forever? It is preferable that you mount a collective or find an entity big enough to handle it.
What is the point of an Open Narrative Framework if anyone can hide your original public domain version by attributing themselves the work and distributing it closed?
This could be made easily through SEO nowadays.
It also involves that derivatives could “improve” without giving back, which could help to other people’s needs.
Basically, what someone already pointed here about maintaining it open.
They even mention yr.no to be some derivative in that page:
In collaboration with NRK, ready-to-use solutions have been developed in order to retrieve data and products: Yr (solution created in collaboration with NRK. This data must be credited in accordance with the instructions on yr.no)
Additionally, in their blog they mention that they provide(d) their own service different from met.no at https://hjelp.yr.no/hc/en-us/articles/360001940793-Free-weather-data-service-from-Yr
You can use https://f-droid.org/packages/com.oF2pks.classyshark3xodus/ for that and is not needed if you use F-Droid official repositories itself as information is already notified in app.