foster

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.