I've been working with Terraform for a while now, and I've noticed that there are a few things that people keep asking me about. I thought it would be helpful to write a blog post about some of the most common questions I get asked and share some of the things I've learned along the way. This is not an exhaustive list, and, if you have any feedback or suggestions, please let me know!
Stuff discovered while analyzing the malware hidden in xz-utils 5.6.0 and 5.6.1.
Notes, honeypot, and exploit demo for the xz backdoor (CVE-2024-3094).
A privacy-first, self-hosted, fully open source personal knowledge management software, written in typescript and golang. Supports fine-grained block-level reference and Markdown WYSIWYG. The data is saved in the workspace data folder. Data synchronization through third-party synchronization disks is not supported, otherwise data may be corrupted. Although it does not support third-party sync disks, it supports connect with third-party cloud storage.
SilverBullet is an extensible, open source personal knowledge management system. Indeed, that’s fancy talk for “a note-taking app with links.” However, SilverBullet goes a bit beyond just that. Runs in any modern browser (including on mobile) as a PWA in two modes (online and synced), where the synced mode enables 100% offline operation, keeping a copy of content in the browser, syncing back to the server when a network connection is available.
Provides an enjoyable Markdown writing experience with a clean UI, rendering text using live preview, further reducing visual noise while still providing direct access to the underlying markdown syntax. Supports wiki-style page linking. Incoming links are indexed and appear as “Linked Mentions” at the bottom of the pages linked to thereby providing bi-directional linking. Optimized for keyboard-based operation. Plugins supported.
Surprisingly, it tries to make not-Docker installation a first-class citizen and specifically documents how to use Deno to set up and upgrade it periodically.
flatnotes is designed to be a distraction-free note-taking app that puts your note content first. This means:
Another key design principle is not to take your notes hostage. Your notes are just markdown files. There's no database, proprietary formatting, complicated folder structures or anything like that. You're free at any point to just move the files elsewhere and use another app.
Equally, the only thing flatnotes caches is the search index and that's incrementally synced on every search (and when flatnotes first starts). This means that you're free to add, edit & delete the markdown files outside of flatnotes even whilst flatnotes is running.
This is a repository to track all of my ongoing projects, research, thoughts, work, code snippets, etc. Some of it may be useful to you, most of it will likely be nonsense. This will hopefully replace, open browser tabs, Google Docs, Pocket, Trello, Evernote, Any.do, text files, wiki pages, and good old fashioned paper, creating one unified place for all of my notes.
This is the publicly-readable WikiLog Digital Garden (17k pages, starting from 2002) of Bill Seitz (a Product Manager and CTO). (You can get your own pair of garden/note-taking spaces from FluxGarden.)
Complete.Org is a personal project managed since 1994 by John Goerzen. Here you can find: John Goerzen’s projects, services hosted here, links, and other things.
Notes on how to use the minipro F/OSS chip programming software. Because the docs are missing important stuff, like how to use it.
Cloned to Windbringer.
Memos is an open source, self-hosted alternative to flomo. Built with Golang and React.
Poking at the online demo it seems pretty nice. API friendly, too.
As I haven't found a good source on archiving your personal collection of Atari software on floppy disk, I documented my own progress, so others might benefit from it.
I started looking for methods to copy my floppies to a PC so that when my 1050(s) break down, I still have some of my source code, letters, games, etc. As I only have recent hardware in the form of Apple, PC (intel) 'antiques' - albeit almost 20 years younger than my atari's - laptops from Y2k or a little bit more recent and several 'embedded' stuff in the form of Arduino and Raspberry Pi's, I started this journey by looking into the various methods that are available to hook up one of the aforementioned devices to my Atari and 1050 setup so I could start archiving.
A collection of useful information and tools pertaining to DTMF.
Notea is a privacy-first, open-source note-taking application. It supports Markdown syntax, sharing, responsive and more. Notea is self-hosted, so your data is safe in your hands. In a few steps, it can be deployed to Vercel or Netlify, or even your own server via docker. Notea does not require a database. Notes are stored in AWS S3 bucket or compatible APIs. This means you can use MinIO (self-hosted), Aliyun OSS (like AWS S3) or NAS to store your data. You can publish your content to the web. With beautiful typography and new upcoming features, you can share your docs, wikis, blogs and newsletters with others using Notea.
An open source self hosted notes and bookmarks taking web app. Looks like of like Pinterest and kind of like a kanban board. PHP, so it could be run in shared hosting. Can use MySQL or SQLite as its back-end.
Written as a PWA so in theory you can take it with you. Or at least the user interface, I don't know about the back-end database.
Simple self-hosted cloud journaling application. Uses SQLite as its back-end. Strictly time-limited; if you post on a day you can only put things in that day's entry. Posts aren't separated by time, only date. Very lightweight. It should expose all of the usual Flask features outside of the UI.
Edit your ~/.gitconfig
file and add the following:
[alias]
pushall = !git remote | xargs -L1 -P0 git push --all --follow-tags
To use it in a Git repository, git pushall
after committing changes to your local copy.
In this Github repository, I'm documenting my journey to write a self-compiling compiler for a subset of the C language. I'm also writing out the details so that, if you want to follow along, there will be an explanation of what I did, why, and with some references back to the theory of compilers.
But not too much theory, I want this to be a practical journey.
Notes and scripts for setting up (yet another) Raspberry Pi computing cluster. One master, at least one slave to do the actual work. The master implements a certain amount of infrastructure for the rest of the network. Includes greyprints for 3D printing a rack for the units. Uses k3s and Docker.
Documents describing half-baked ideas and their kin.