I catch a lot of shit for my distaste of GPL. I don’t think I should be able to tell you what you can and can’t do with my source code. I’ve released it into the wild. If I put caveats on it it’s not really free.

Just alias pdoman=podman. I do that with all my common typos.

All of these packaging systems have plenty of tutorials. Speaking from experience, many maintainers were not developers when they started maintaining packages for distros other than the official distros. I have worked with several maintainers who do work in tech and know socially several who had no background. This could be a great place for you to start!

You bother because FOSS is as much paying it forward as it is getting shit for free.

I mean it’s FOSS. Have you considered opening a PR to contribute what’s missing? You can be the change you want to see. I wouldn’t normally comment something like this. Your emphasis on “still” raised my hackles a little bit and led me to ask why you still haven’t made your own.

A problem so common it has an official page

If a repo is very popular, it should have a lot of forks. The higher the upstream popularity, the higher the downstream popularity. When a dev makes a claim that there are a ton of malicious forks stealing IP, we can vet that claim by looking at the forks that respect the upstream. Big projects have a big community with big forks with many stars. The popular downstreams drive traffic to the upstream.

In this case, we have a couple hundred direct forks. That’s not a ton. Out of those, only three have stars. All of them only have one star. At face value, that could imply a few things: the repo is not very popular, the community is centralized around the upstream, or something else along those lines. Comparing this to other open source projects, our initial conclusion is that this is not a hugely popular repo and does not get a lot of development outside of its incredibly niche community.

Occam’s razor is a tool, not objective truth. Based on the facts as we can see them, this focus on forking from the dev is much more indicative of a burnout spiral, incredibly common in the FOSS community, than nefarious actors. If we see receipts, eg a collection of takedown requests on malicious forks attempting to claim ownership of the code, our analysis falls apart. That’s still a possibility, however remote.

There were forks that wanted to hide the fact that they were Floorp forks, forks that did not want to contribute to Floorp at all, forks that used the code for life and just changed the name of Floorp, and many other forks were born.

There are three visible forks that have any stars. All of them have one star. You’re telling me that a project that is so widely and maliciously repackaged has no normal forks with more than one star? Is this tech that only bad actors want to use and has no following in the open source community?

Where are these evil forks, how do we actually know they’re forks, and why are they still up if they’re breaking license?

Edit: Here is a fork with 200+ stars that isn’t a direct GH fork. Given its premise is an opinionated and branded Floorp, is it morally wrong for its maintainers to not contribute to Floorp (assuming they don’t only for the sake of argument)? Does your answer apply to fediverse server owners (eg Mastodon, Lemmy) whose premise is hosting an opinionated and branded instance often explicitly without the technical skill to suggest patches?

You really shouldn’t apply a CC license to code. Someone who does that after saying what the dev said about not forking their open source code has no fucking clue what they’re talking about and is either about to spiral out or build something really dumb (or both).

Edit: yeah the dev seems pretty delusional

If you want convenience, Google Books is pretty solid. Just make sure you have all of your books and are only uploading to Google. If you buy from Google, you’ll run into the same problem. I organize via Calibre and use it to push to both Google and a Kobo.

I personally have all my ebooks and use Google Books to read on all my devices. It’s more convenient than trying to self host stuff. When Google eventually drops Google Books I will have to figure out what to use.

This picture is kinda wimpy. Zaslav had led the company through a total stock drop of almost $16 per share yet his comp has gone up almost 100% based on the figures I’ve been able to find. Granted he’s not getting the lucrative options he started with but that doesn’t seem to stop the other comp from going up.

It’s also offered as part of the installation process at least for Ubuntu server. If you don’t know better it bites you real quick.

The issue here is that Canonical pushed the snap install without warning about its reduced functionality. I don’t think highlighting a wildly different experience between a snap install and the Docker experience people are used to from the standard package install is “bashing it just because it’s popular to hate on snap.” For example, if you take a fresh Ubuntu server 22 install and use the snap package, not realizing that snaps have serious limitations which are not explicitly called out when the snap is offered in the installation process, you’re going to be confused unless you already have that knowledge. It also very helpfully masks everything so debugging is incredibly difficult if you are not already aware of the snap limitations.

This is really dependent on whether or not you want to interact with mounted volumes. In a production setting, containers are ephemeral and should essentially never be touched. Data is abstracted into stores like a database or object storage. If you’re interacting with mounted volumes, it’s usually through a different layer of abstraction like Kibana reading Elastic indices. In a self-hosted setting, you might be sidestepping dependency hell on a local system by containerizing. Data is often tightly coupled to the local filesystem. It is much easier to match the container user to the desired local user to avoid constant sudo calls.

I had to check the community before responding. Since we’re talking self-hosted, your advice is largely overkill.

In all fairness to Pocket Casts, the yearly cost in the US is $40, which is about the monthly cost of the three things you mentioned together. If your country gives you yearly Google Play Pass, YouTube Premium, and Spotify Premium for less than $40 US, that’s a fucking steal.

In all fuck you to Pocket Casts, Basic App functionality like folders shouldn’t be behind a subscription. I can understand a one-time unlock fee for app functionality or ongoing subscription costs to cover cloud storage and sync capabilities. I cannot fucking understand why folders would cost me $40 US a year.

What about infrastructure costs? Are you comfortable making someone else pay for your access? What about the design and implementation of the API? Should all software be free?

Please note that I’m not trying to support this decision at all. I personally feel like API access is similar to SSO for enterprise stuff (check out sso.tax). I also feel like there should be some level of compensation and even profit so people can focus on building stuff like this. It’s really hard to define what that is, especially without transparent costs, which I don’t believe OpenSubtitles shares? Also they use super predatory ads so I don’t think they have any high ground to even suggest what I’m talking about.

Moving to AGPL means enterprises stop using your software and improving it in-house with the possibility of patches “leaking” out when there isn’t a clear OSS contribution model. Going AGPL does prevent AWS from turning Matrix into Opentrix, but it also just focuses the major hosts on platforming your community product instead of improving your product. Their inspiration is Grafana. Time will tell if that’s going to pan out. The enterprises I’ve consulted for use hosted Grafana like Amazon Managed Grafana, not Grafana Cloud.

I personally am very wary of any AGPL project in any corporate setting. I’ve convinced companies to move the other way, from AGPL to Apache, because I also warn companies AGPL poses a compliance risk.

If you’re only on Linux and don’t ever touch containers on Windows or Mac, podman can work fairly well. You need to be comfortable with orchestration tools like k8s to replace compose (or just do a ton of containers) and you can’t use a lot of COTS that has hardcoded dockerisms (localstack, for example, does not work well with podman).

If you have to use Windows or Mac, podman makes life really difficult because you’re running through a VM and it’s just not worth it yet.

I worked at one of the majors pre-Microsoft acquisition. “Highly skilled” is actually a relative comparison to the security teams at gaming companies, not an industry benchmark comparison. The bar for highly skilled plummets once you include things like social platforms, launchers, and telemetry.

You can get free offers from most places. If you juggle accounts and don’t do a ton, you can use AWS for free perpetually without dealing with this odd idle fandango.

What about Oracle made it work for you over others? Have you looked at the minors like Linode or DigitalOcean?