On Linux VA-API works really well for AMD video encoding. I have a small home server with an AMD Ryzen 5 5600G and my experience has been excellent.

The only downside is that some companies decided hardware decoding violated some patent and disabled hardware encoding in the default va-api package. You just need to switch to the freeworld version of va-api and everything works well.

But selling other peoples’ labor would introduce it to the capitalist system. Not saying that makes you a capitalist. Just saying some people might want to keep their art out of that system.

I think that’s best left up to the author. Sometimes someone might prefer that their art stay independent of capitalism. I think that is a respectable position.

With a NC license, the author still can sell the work and make money. It’s just that other people can’t.

deleted by creator

They changed the refund policy on the Linux phone that they sell.

At the time when the phone was under development they let people preorder in exchange for a small discount. Many people including myself wanted to support such a product and payed in. At the time the policy was you could get your money back any time before the phone shipped.

The phone was delayed for years and years and naturally people got impatient and demanded their money back.

Purism on the fly changed the policy and said you could only ask for your money back in a small window just before your phone shipped. Not before and if it shipped it was too late. They just refused to honor the original policy.

It was discovered that people could content the attorney General of California and the state would force them to honor the original policy. A lot of people, including myself did this.

The fact that it came to that makes them a shady company.

This all being said I am very happy they are profitable. While I would never preorder anything from them again, if they update the phone specs I would consider buying one.

More Linux first companies is a good thing.

You have to set each entry under the same domain to to match against “host” and you’re set.

Yes. The left side of the : in the volume is the file on the host. You can see this directory on the host. The right side of the : is where that directory is replicated into the docker container.

All you need to do is to interact with the directory on the host.

You should use volumes over bind. You just move your media into the volume location on the local host and try will show up in docker. You should never need to ssh or sftp into the container.

There is a lot here but I think the most important thing is that docker containers should always be disposable. Don’t put any data into the container ever.

All of your data and configuration should be done in volumes. Local disk to inside the container is all you really need.

By doing this you make updating any given docker container easy as just pulling the newest tagged version of the container. If you are using docker and not podman you can use tools like watchtower to do this automatically.

As for what distro, it depends on your goals. Do you want to learn and improve your skills? Stick with Fedora or Rocky or Debian or openSUSE. I recommend learning the command line as you go, but if you want a nice UI openSUSE has Yast which is a very robust tool.

If you want to just have a home NAS but don’t want to learn that’s a different question. In this case if you’re getting a proprietary NAS anyway you could just get one that supports docker (like synology) and kill 2 birds with 1 stone.

https://codeberg.org/forgejo/discussions/issues/67

The biggest issue is they require your to give them your rights as they pertain to copyrights.

That means even if you submit MIT or GPL licensed code they can just instantly say “we relicense this code as proprietary” and there is nothing anyone can do.

They rejected a bunch of valid PRs. Including the one linked here because the author refused to assigned their copyrights to the Gitea corporation.

Right now Forgejo is a drop in replacement. This article is them announcing that Forgejo will eventually not be one.

Because gitea is fully the victim of corporate capture. Any PRs that make gitea better in a way that would reduce the main corporate “sponsor” profit are rejected.

The company has a conflict of interest with the community and it shows. Forgejo is sponsored by a non profit open source cooperative.

+1 For Seafile. They put out a docker image that works well. It hasthe fastest sync I’ve ever seen and it has good clients.

This is the most pretentious thing I have read in a long while. Imagine comparing the holocaust to a copy left software license that mega corps find less profitable.

To be fair the license is not meant to cause this and has never been enforced like this. The license was written for software tooling.

The ambiguity is a valid concern. Hopefully the next version addresses this a bit better. This being said mega corps will call anything they can’t abuse for profit “extreme”. So if they think it’s extreme that just means we are on the right track.

For the record. The SSPL that Redis switched to while technically not recognized by the OSI really isn’t bad at all.

It’s exactly like the AGPL except even more “powerful”. Under the SSPL if you host redis as a paid service you would have to open source the tooling you use to manage those hosted instances of redis.

I don’t see why anyone but hyper scalers would object. It’s a shame that the OSI didn’t adopt it.

I think you should just go with whomever is cheapest. Get a domain you like and use it. RMS owns stallman.org I don’t see the need to overthink it.

No problem. It should be wayyy faster than sshfs for the record. Both NFS and WireGuard are best in class tools.