Foster Hangdaan

I use Arch for personal and gaming, Debian for self hosting and hacking, Alpine for containerized cloud deployments.

Pretty much the same for me: bleeding-edge Arch for my workstation, rock-stable Debian for my server.

No license?

I maintain a rule that all files above the repo must be inside a folder, with one exception: a README file. Including the code folder, this typically results in no more than 5 folders; the project folder itself is kept organized and uncluttered.

Don’t forget: entrepreneur, playboy, philanthropist.

They are the project’s subfolders (outside of the Git repo):

• code contains the source code; version-controlled with Git.
• wiki contains documentation and also version-controlled.
• designs contains GIMP, Inkscape or Krita save files.

This structure works for me since software projects involve more things than just the code, and you can add more subfolders according to your liking such as notes, pkgbuild (for Arch Linux), or releases.

I tend to follow this structure:

Projects
├── personal
│   └── project-name
│       ├── code
│       ├── designs
│       └── wiki
└── work
    └── project-name
        ├── code
        ├── designs
        └── wiki

From a time when websites used <table> or position: absolute; to place elements on the screen. That website is just one big table.

• Free Software Foundation
• GNU
• Richard Stallman’s Personal Blog
• Savannah

And pretty much the rest of the FSF and GNU websites.

Where the dotfiles at?

I recommend Peer Calls as an alternative. Peer Calls uses peer-to-peer communication similar to Jami. You can check out Peer Calls on Github for more info.

So, in short, the things I really like about it:

• Simple to selfhost - Only one Docker container with no dependencies (database, storage, etc.) and you only need to forward HTTP/S traffic.
• Lightweight - You get voice and text chat; screen and file sharing. All of it directly P2P.
• Private - Selfhosting the signaling server will grant you control over the only step which requires a central server during the WebRTC connection process.
• No accounts - Just start using, no accounts are involved.