Bauke's recent activity
-
Comment on Home network help part 2, SSH and Server in ~comp
-
Comment on Nested noise collapse test in ~test
-
Comment on How do you keep track of detailed work activities? in ~talk
Bauke (edited )LinkI'm in a fairly similar boat, where the platform we use doesn't have a proper backend language (only SQL Server 2016 is available, or older in some cases) and the "backend" is more of a low-code...I'm in a fairly similar boat, where the platform we use doesn't have a proper backend language (only SQL Server 2016 is available, or older in some cases) and the "backend" is more of a low-code flowchart type of builder. So here's some stream of consciousness stuff that may be useful:
Most of my notes end up looking something like this, where I use Obsidian and this custom checkbox theme. The screenshot in Markdown would be this:
- [x] Updated stuff - [?] What do I do with X, Y and Z? Ask Person A - [P] Do the thing this and that way - [!] Not yet updated in production - [b] See [[Other]] note - [T] Waiting on feedback from Person B - [ ] Remaining todos: - [ ] More stuff - [ ] And more stuff - [ ] Endless amounts of stuff
Sometimes I'll copy over snippets of code into Obsidian I find them important or if I know I'll need them later. If I'll be making a lot of changes to those code snippets I'll version control them in git, though that's usually just so I can get easy diffs later on (particularly for HTML). And for me too they will never be executed outside of the platform and will also be modified by others, so it isn't perfect but it can be useful, especially if you need to make a certain change in a lot of places.
Typically if I need to change something what I'll do is duplicate what I need from production so I can do tests safely, and then once I'm satisfied with my changes/they've been reviewed by someone else, then I'll move it to production and document on a high level what was changed. I also name all my test stuff with "Test YYYY-MM-DD" so other people don't get confused if they're searching around.
If I have any inkling that I may want to roll back to a previous version I will just swap my test copy into production and call it "version N+1". Then if I ever want to roll back I can just swap back to version N (it's not always that simple, but it's an option sometimes). And after some time has passed with everything going smoothly version N can be deleted during a cleanup if needed.
Sometimes I'll take screenshots of stuff before and after changes and put those into Obsidian. Other times if I'm gonna do a big SQL query on a table I'll take a backup of it as a CSV and put that in Obsidian if it's small enough, or version control it if it doesn't have sensitive data, or just keep it on my PC if the file is too big.
I also have a knowledge base folder in Obsidian together with a "Documentation TODO" note where I'll just add stuff that I want to document because I want to refer back to them in the future, but I don't have the time to document them now. So any time I have some downtime I'll check my documentation todo and work on that.
The knowledge base is super simple where I just make the note title something I would search for, like "Internal tables in SQL server" or "Search stored procedure definitions" and then in those notes I'll just put whatever relevant information is useful.
Those are generally the way I do things. I think the biggest tip I could give though is just to write stuff down in a way that makes sense for you. It may take a while to figure out what that looks like but the more you do it the better you'll get at it. My notes from a year ago compared to my notes today are a complete night and day difference.
And the second biggest tip I can give is to have an Archive folder where you can dump old notes in and forget all about them. And also don't be afraid of leaving notes unfinished, I have sooo many notes that are like half filled in because I didn't "complete" them, but it doesn't matter since all the work that needed to be done has been done. But do keep them, you know, just in case.
Hopefully that's somewhat useful. :D
-
Comment on Tildes Minecraft Hardcore - Live at 20:00 UTC today in ~games
Bauke LinkMade it about an hour before almost dying of starvation, then finding some pigs thinking I'd be saved, only for a creeper to sneak up behind me while cooking and I couldn't react quick enough. :D...Made it about an hour before almost dying of starvation, then finding some pigs thinking I'd be saved, only for a creeper to sneak up behind me while cooking and I couldn't react quick enough. :D
-
Comment on Possible site bug: Cannot send PM with moose emoji as the subject in ~tildes
Bauke (edited )Link ParentYou are correct! Specifically this section is removing our moose friend. In [6]: from tildes.lib.string import simplify_string In [7]: simplify_string("") Debug: Category Cn Out[7]: '' <-- Empty...but I think something's processing the title before it gets to the length check code.
You are correct! Specifically this section is removing our moose friend.
In [6]: from tildes.lib.string import simplify_string In [7]: simplify_string("🫎") Debug: Category Cn Out[7]: '' <-- Empty title! OopsThe moose is falling under the
CnUnicode category in that function and is being filtered out of the string.While for example our frog friend falls under the
Socategory and doesn't get filtered out.In [8]: simplify_string("🐸") Debug: Category So Out[8]: '🐸'I've made an issue for it in GitLab: #831
-
Comment on Can Bearblog links show authors? in ~tildes
Bauke Link ParentAhh right, so the actual API call to Embedly can be found here (this is also how it gets stored in the database) and then how that data actually gets used can be found here and in the HTML here....Ahh right, so the actual API call to Embedly can be found here (this is also how it gets stored in the database) and then how that data actually gets used can be found here and in the HTML here.
Also this might be why it doesn't show the title for some cases.
-
Comment on Can Bearblog links show authors? in ~tildes
Bauke Link ParentTildes uses Embedly's Extract API behind the scenes to grab that information, you can actually try this out yourself here and see the results:...Tildes uses Embedly's Extract API behind the scenes to grab that information, you can actually try this out yourself here and see the results:
- https://embed.ly/docs/explore/extract?url=https%3A%2F%2Fomeru.bearblog.dev%2Flifestyle%2F
- https://embed.ly/docs/explore/extract?url=https%3A%2F%2Faphoenix.ca%2Fblog%2F2025%2Fthe-butterfly-effect%2F
In the omeru.bearblog.dev example it doesn't grab any authors (presumably because it lacks any kind of author indication in the meta tags) but with your blog it does grab "Andrew Phoenix".
You can also see the other data from the
og:...and other meta tags Embedly can grab. -
Comment on How I setup the open-source paperless-ngx to manage documents in ~tech
Bauke LinkGreat article! Paperless-ngx is so cool, I've been using it for a little while now myself but only for digital documents for now. But I recently migrated my setup to a local system and with that I...Great article!
Paperless-ngx is so cool, I've been using it for a little while now myself but only for digital documents for now. But I recently migrated my setup to a local system and with that I explored the email processing feature a little more and I came up with a pretty nice little automated workflow.
The first thing I did was I created a dedicated email address for Paperless, just so I don't have to worry about anything getting imported that shouldn't. And then I made the Mail Rule in Paperless check for only emails coming from my personal email address with PDF attachments. This is pretty standard I think for automated mail importing.
But then in my mail client of choice, Thunderbird, I added this message filter. So when I archive an email and it has an attachment, and the sender is in my "Paperless Correspondents" address book in Thunderbird, it'll forward that email to the Paperless address and get automatically imported. Isn't that so cool!! I found it so neat when I figured out Thunderbird can do all this in an easy way.
I also run my setup with the consume directory available via Samba so should I want to bulk import something it's easy enough to do it there. Though the web UI works too in limited numbers.
-
Comment on My most painful Linux experience in ~comp
Bauke LinkI had the exact same crash happen two weeks ago when I added an old hard drive to my NAS, put the UUID into my fstab, formatted the drive to btrfs (which I believe caused the UUID to change) and...Ultimately, I had an invalid /etc/fstab entry for a secondary drive (NTFS extra storage, not boot-critical).
I had the exact same crash happen two weeks ago when I added an old hard drive to my NAS, put the UUID into my fstab, formatted the drive to btrfs (which I believe caused the UUID to change) and then on mount the system crashed.
Fortunately for me I'm running NixOS! So the fix was simply to boot into the previous generation, update the UUID to the new correct one and rebuild my configuration. First time I ever saw the emergency mode screen in Linux though, so that was fun! :D
-
Comment on ssh git@sr.ht is asking password and denies me in ~comp
Bauke LinkHave you tried cloning a repository via SSH or are you specifically trying to do ssh git@sr.ht? I know GitHub shows a message when you do ssh git@github.com but as far as I can tell Sourcehut...Have you tried cloning a repository via SSH or are you specifically trying to do
ssh git@sr.ht?I know GitHub shows a message when you do
ssh git@github.combut as far as I can tell Sourcehut doesn't have this. I get the same password prompt when I try to dossh git@sr.htbut I can clone repositories just fine. -
Comment on Anyone sucessfully self-hosted Tildes instance? in ~tildes
Bauke Link ParentThank you! I'm happy it (mostly ;)) worked out of the box. :D I also created a video last weekend for anyone wanting to see the process, I'll be adding this to the guide when I get to the long... -
Comment on Datastar: web framework for the future? in ~comp
Bauke Link ParentDefinitely agree on that. Simpler ways are possible and the fewer constantly updating parts in the stack the better, in my opinion.I mentioned Tildes as it is a showcase that you can have website in the modern day and age without having all sorts of abstractions tacked on abstraction on to abstractions.
Definitely agree on that. Simpler ways are possible and the fewer constantly updating parts in the stack the better, in my opinion.
-
Comment on Datastar: web framework for the future? in ~comp
Bauke Link ParentNot to diminish your point or anything, but Tildes actually uses Intercooler.js which is the predecessor to HTMX. So in a way it uses this same style of web development already. :D But I do also...But commenting this on Tildes, a website fully functional in 2025 using "ancient" technologies like server side rendering, jQuery and plain css, really makes me sceptical in this regard.
Not to diminish your point or anything, but Tildes actually uses Intercooler.js which is the predecessor to HTMX. So in a way it uses this same style of web development already. :D
But I do also agree with you, Datastar needs a whole SDK to make its magic happen. At least with HTMX you can just plop in HTML from whatever route. I think a middle ground could exist between these two that requires no server magic like Datastar and is simpler than HTMX.
I personally really like the idea of keeping everything on the server and rendering the HTML in fragments but I've also tried a few things with HTMX and it's certainly not as easy and simple as it could be.
-
Comment on Anyone sucessfully self-hosted Tildes instance? in ~tildes
Bauke (edited )Link ParentI've created a first pass on a guide together with the Ansible playbooks needed. I still need to write out the long version of the guide but for now anyone can give it a try if they like. :D You...I've created a first pass on a guide together with the Ansible playbooks needed. I still need to write out the long version of the guide but for now anyone can give it a try if they like. :D
You can find it here: https://gitlab.com/tildes-community/tildes-setup-guide
I highly highly highly recommend anyone wanting to try these out that you do it on a completely new server. And if you're going to do it on an existing server, read through every single role before you do it and understand what each step does! And make changes to it what you don't want/need, especially the initial-server-setup playbook.
Happy hosting!
Edit: I'll also create a proper topic for this once I'm fully done with it. :)
-
Comment on Anyone sucessfully self-hosted Tildes instance? in ~tildes
Bauke (edited )LinkI've been working on adapting the Ansible playbook that's in the Tildes repository so anyone could run it on a fresh Debian server and have a working Tildes instance after it finishes. I'd say...- Exemplary
I've been working on adapting the Ansible playbook that's in the Tildes repository so anyone could run it on a fresh Debian server and have a working Tildes instance after it finishes. I'd say it's about 25% complete right now but I will also mention that it kind of assumes you're going to be running a Debian 12 server and nothing else apart from Tildes on it (which I know from my own self-hosting is unusual :P).
I'll also add that there's a bunch of things that are currently hardcoded for tildes.net (like for example the tild.es shortlinker), so if those are things you want to work you'd have to manually change them in the code.
But! If you really really want to give it a shot, it is possible to piece it all together using this old comment from Deimos, the Ansible playbook and the General Development Info docs. Though I'll add these tips:
- Ignore anything about SaltStack and Pillar, those have been replaced with Ansible
- If you want to set up a production instance ignore anything about Vagrant or VirtualBox
journalctl -fexu <unit name>.serviceis your friend- If you use a VPS to test on, check if they have snapshots and rollbacks (for cheap!) so you can break stuff and rollback easily (if you want my recommendation, Hetzner is easy to do this with)
I'll try to write up an up-to-date guide this weekend that includes a base Ansible playbook you could run and have a fresh Tildes instance ready to go!
-
Comment on Update on Tildes codebase: Less community fork, more official maintainers in ~tildes
Bauke Link ParentPoints for originality! Haven't heard that one before. :DPoints for originality! Haven't heard that one before. :D
-
Comment on Books I read during 2024 that were published during 2024 in ~books
Bauke (edited )Link ParentDid you ever use the blue J image anywhere else on your site? It's possible Embedly (which is what Tildes uses behind the scenes to figure out the icons) grabbed that image when it couldn't find a...Did you ever use the blue J image anywhere else on your site? It's possible Embedly (which is what Tildes uses behind the scenes to figure out the icons) grabbed that image when it couldn't find a favicon for some reason and it has been saved like that on Tildes ever since.
Edit: Ah, it likely came from this topic and the way Tildes saves icons I believe doesn't take subdomains into account.
-
Catbus Collective - Shiki no Uta (from Samurai Champloo) (Live at Clement’s Place) (2024)
4 votes -
Comment on Paperless NGX vs ??? in ~tech
Bauke LinkThe awesome-selfhosted list has a document management section if you're looking for alternatives, but honestly I think you should just try Paperless-ngx. It's very good and the UI is excellent. It...The awesome-selfhosted list has a document management section if you're looking for alternatives, but honestly I think you should just try Paperless-ngx. It's very good and the UI is excellent.
It takes a little bit of setup and manual work in the beginning before it starts recognizing the metadata and which documents belong to what correspondent/document type but once that's all done it is really nice. I highly recommend starting off uploading just one document at a time and manually entering the metadata, and then after a couple if you can see it automatically get things correct you're probably fine hooking it up with your scanner (which there are a lot of options for).
The documentation is excellent by the way, everything you need is in there.
-
Comment on Self-hosting a podcast server in ~tech
Bauke LinkLast week I was playing around with AzuraCast which is more for doing web radio stuff but I think it does also have some podcast features. It was easy enough to get set up with Docker and the...Last week I was playing around with AzuraCast which is more for doing web radio stuff but I think it does also have some podcast features. It was easy enough to get set up with Docker and the documentation is pretty good too.
Fixed!