Agreed, very suspicious. I would feel safe assuming that I can use the code under AGPL, but I would hesitate to use it for anything other than personal hobby because it would not surprise me if they closed their github account and never released any more code.

IANAL. I originally interpreted the license.txt as: all of the source code is AGPL (see lines 234-235), some of the source is also Apache 2.0, and the binaries are MIT; plus a trademark notice and contact info for getting a commercial license. After rereading it, my only conclusion is that this is a dumpster fire of a license.txt, and can be reasonably read several different ways.

At the copyright owner, they are within their rights to release the source code under the AGPL, and also sell it under other licenses. Anyone is free to use the code under the AGPL. Nobody who releases code under an open-source license is obligated to provide binaries.

As the copyright owner, they are free to use the code along with other non-open-source code (e.g.: SSO integrations) to build a non-free product.

Mattermost is licensed under the AGPL. How are they enforcing a 250 user limit?

Edit: the commercial version with additional features (e.g.: SSO) is limited. Obviously the open-source version is unlimited.

9

I think you are looking for SSH certificates.

I would advise to not do personal stuff on your work computer.

I used to have a UDM Pro, a Unifi rack mount switch, four APs, three cameras, and two mini POE switches. I sold it all when I moved recently, and now I just have 3 cheapish routers running OpenWRT.

I wish I kept all the Unifi stuff.

Do it.

But how can I trust you?

You can’t.

Can you trust me?

No.

Use https://www.passwordstore.org/. Sync it to a trusted person’s git server. Put the gpg key on a usb stick and give it to them. Write the password to the GPG key on a piece of paper and give it to your lawyer with instructions to give it to your trusted person in the event of your death.

spamassassin

I use Debian stable and subscribe to the debian-security-announce mailing list, so I update each time I get an email from it.

I have 5 docker-compose-based services. I wrote a shell script:

#!/usr/bin/env bash
for y in $(find /etc/ -name docker-compose.yml); do
  cd $(dirname $y)
  docker compose pull
  systemctl restart $y
done

(edit: spelling; thanks Unquote0270)

0. Consider getting a VPS to play around with to learn how this stuff works before you expose your data to the internet.
1. Learn about how DNS works. You will create an A record (and possibly also an AAAA recordy) for your domain pointing to your home IP (or VPS).
2. If SquareSpace does not let you set records (and will only allow you to use Squarespace-hosted services) you will need to migrate your domain to another provider. I like gandi.net.
3. Learn how your router does port forwarding. You will forward port(s) for the calendar service from your router to your home PC. (Or learn how to do firewalls on your VPS.)
4. Before you actually connect to it with credentials over the internet, set up SSL/TLS certificates with LetsEncrypt.

I use tmux or screen, and set the status bar in different remotes to different colors.

Lots of things seem like they would work until you try them.

gandi.net

markdown files in git

email.

They added:

10. None of the Work may be used in any form as part, or whole, of an integration, plugin or app that integrates with Atlassian’s Confluence or Jira products.

Can’t you just not use their cloud services? It makes you create an account for setup, but once setup was done I never touched it.