Foster Hangdaan

In other news: Jeff Bezos is now the richest person in the world.

I would be careful using this service. This service stores wallet addresses as DNS records and can potentially store many of them, making it a honeypot for hackers. Anyone who can gain access to the DNS records will be able to reroute transactions by changing the addresses of the aliases.

For people who already own a domain, you don’t need this service, since you can easily setup OpenAlias yourself by adding the necessary TXT records. That is all that this service does for you.

Every app in this space tends to get enshittified, so I just use shell scripts to do API calls nowadays. I used Insomnia and Postman in the past.

For sans-serif, I use Mona Sans. For monospace, I use Monaspace. I think it’s a good-looking combination.

I’d also like to add that you can save an image to a local file using docker image save and load them back using docker image load. So, along with the options mentioned above, you have plenty of options to backup images for offline use.

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.

Just bookmark the repos you like; no Github account needed.

Definitely best to get that done ASAP. Forgejo being a drop-in replacement for Gitea won’t be guaranteed ever since the hard fork:

To continue living by that statement, a decision was made in early 2024 to become a hard fork. By doing so, Forgejo is no longer bound to Gitea, and can forge its own path going forward, allowing maintainers and contributors to reduce tech debt at a much higher pace, and implement changes - whether they’re new features or bug fixes - that would otherwise have a high risk of conflicting with changes made in Gitea.

I’m in the same boat and also looking for a privacy-respecting platform for communicating with family and friends. So I’d also like to add items that are not yet mentioned to the list of suggestions:

• Jami
• Peer Calls - can be selfhosted; you can try it out straight away using their flagship instance located here.

I wonder sometimes if the advice against pointing DNS records to your own residential IP amounts to a big scare. Like you say, if it’s just a static page served on an up to date and minimal web server, there’s less leverage for an attacker to abuse.

That advice is a bit old-fashioned in my opinion. There are many tools nowadays that will get you a very secure setup without much effort:

• Using a reverse proxy with automatic SSL certs like Caddy.
• Sandboxing services with Podman.
• Mitigating DoS attacks by using a WAF such as Bunkerweb.

And of course, besides all these tools, the simplest way of securing public services is to keep them updated.

I’ve found that ISPs too often block port 80 and 443. Did you luck out with a decent one?

Rogers has been my ISP for several years and have no issue receiving HTTP/S traffic. The only issue, like with most providers, is that they block port 25 (SMTP). It’s the only thing keeping me from self-hosting my own email server and have to rely on a VPS.

I’m running RetroPie on a Debian laptop and I’m able to map all the buttons of my 8BitDo Pro 2 controller; no issues at all. I was also able to connect and configure an Xbox 360 controller just fine.

You might want to try getting help on the RetroPie forums if you don’t get any luck here.