festus

Not really, no. I used Ubuntu Touch for about a year a few years ago and the method for running Android apps is essentially to run an emulator layer on the phone (anBox), which in practice is nearly unusable. It may have improved somewhat since then but I suspect you're still going to need a relatively beefy phone at minimum to run whatever solutions there are at a decent speed.

I greatly despise all facial hair.

Disney+ (at least in Canada) gives a 15% discount if you pay for a year up-front.

Similar story. I was in the ER today and most staff weren't wearing masks, despite another patient just a few curtains down testing positive for Covid!

I think it's worth noting that news organizations are struggling not because less people are reading news but rather because advertising is so cheap now. When newspapers were the only advertising source they could charge high prices. Then TV came out which hurt them, but this was balanced by TV spending some money on journalism. Now with the internet the prices newspapers can charge for advertising is sooo much less than they could previously.

Anyway, I think it's worth noting this because there's this narrative that news organizations helped build up social media (and maybe deserve a cut). I mean really, how many people decided to make an Instagram account or Facebook account because CBC happened to have a page they could follow? Of the people I know who use Facebook or Instagram, none use it for news. This also means that utilizing social media to drive traffic may still be a good strategy - if the government hadn't effectively blocked that.

The bill penalizes Meta even if they link but do zero scraping. Regardless though, news organizations can breathe a sigh of relief as Meta is terminating the totally one-sided relationship where only Meta benefited at news organizations' expense.

And none the container names or link aliases conflict? Like you don't have multiple db containers? Perhaps try renaming the Nextcloud db to something like nextcloud_db if you aren't already.

No, because these licenses can't bind the copyright owner themselvess. AGPL is the terms that OwnCloud allows us access to it, but as it's their code they don't need a license to do whatever with it.

Let me put it another way - OwnCloud would be the only folks with standing to sue someone for violating the AGPL on their code. That means that the only people who could possibly sue OwnCloud for having a non-AGPL version is... OwnCloud. So even if the AGPL somehow claimed to bind the copyright owner it still wouldn't work legally as the copyright owner just has to not sue themselves.

Most of the items on that list (with the possible exception of the 'Enterprise Apps') are items that involve them either hosting an aspect for you (push notifications), training, or utilizing their OAuth credentials with Microsoft. Because they forked OwnCloud they're actually bound by the AGPL on that original code and legally can't license features in the main codebase as anything other than AGPL (less sure on those 'apps'), so they're limited in what features they can restrict to paying customers.

This is a good summary, but the Tl;DR is that Owncloud has a non-open source Enterprise version with extra features you need to pay for, while Nextcloud is a fully open source fork.

What name do you assign the DB for PostgreSQL in Docker and does it by chance happen to match the name of any other containers, possibly in other docker compose files?

I'm only mentioning it because I experienced weird inconsistent issues with a service I was running where it was sometimes having trouble connecting to its DB companion and I eventually realized that it was sometimes connecting to the other container. I was also finding that turning it off and on again was often 'fixing' the issue, at least for a while. Might be worth checking out. I'd also consider viewing the logs for Nextcloud (docker logs -f ) when you're unable to login and see if there are any errors. Frankly I've never had these specific issues with Nextcloud, and given that it's based on PHP (it only 'executes' on an HTTP request), it seems like restarting shouldn't help unless it's something else.

Two things:

1. Arch is very DIY and has very few defaults setup for the user - you're essentially building the OS to be exactly how you like it, as opposed to other distros where it's functional right away and you customize on top of that. I.e. when you boot off of an ISO for Arch you just get a terminal and have to install from there, choosing basically every package you're going to want from fonts, desktop environments, login screens, etc. I like it quite a bit because it really forced me to learn how my system works and to fix issues myself. To get a feel for what I'm talking about take a look at the Installation Guide.

2. The second thing about Arch is that they try to update packages ASAP from upstream; this is in contrast to other distros that might keep a certain version older for 'stability' reasons. IMHO I find other distros frustrating when I encounter a bug that I discover was already fixed a year ago upstream and won't be available in the distro until the next release - I think that does more to harm the user than keeping everything, including bugs, constant.

If you're going to play with Arch I suggest you try it in a VM first and see if you can get it functional before you mess with your main system.