I wanted a place to journal wines and share with friends, so I made one: Chateau St. Émilion.
You're the second to see it. My sister was the first.
Personal logs are private to yourself and the groups you share them with. Guest reviews and articles are public. The web site is for fun -- don't take it too seriously, but if you'd like to contribute a guest review or article, let me know.
(Yes, I know the name is pretentious. Also, I'm a programmer, not a designer, so please cut a little slack.)
Since I've been laid off, I finally have time to work on my static website generator called Markerator. It ingests markdown files, and images, and spits out a website that is pure HTML and CSS, no javascript. I recently added Open Graph support so that links appear correctly as cards when shared on social media, and am just about ready to push a big set of changes that add unit testing, as well as user-definable pagination for the News/Updates/Blog pages.
My next steps are to document the CSS format so that people can add their own themes, as well as come up with some more default themes that ship with Markerator. Once that is done, I'm going to write some more documentation that walk users step-by-step through using it, as well as how to automate deployment using Github actions. That'll be the 1.0.0 release.
I'm finally feeling inspired again. If you want to see what Markerator can produce, I use it for my personal website, Bengineering. Markerator probably isn't ready for primetime yet, but I'm finally getting there. Check it out if you're morbidly curious.
For work I’m tryna make a replicable Azeroth core deployment that uses llm backends for player bots so we can pull data from the eks cluster and the llm interactions.
I'm attempting to monitize my side project (first time, wish me luck!). It's a daily work tracker I've always wished existed - offline, no data in the cloud (unless you want it), no account required, day focused, automatic movement of tasks not completed, power-user friendly, and infinitely nestable/collapsible. I know a lot about software, a little bit about running a business, but nothing about the nitty gritty stuff it takes to actually launch a product.. so that's been fun figuring all that out. If you want to check it out:
did you use a library for the onboarding layer and the positioning of those cards? I thought maybe you used Anchor Positioning, but dev tools doesn't show that, so curious if it's library or you made it work yourself.
I stole that one from the first ever job I ever worked :)
No library - The x/y coordinates get calculated to place an appropriate sized div over whatever I'm highlighting and the screen dim around it is created by adding a massive dropshadow around it.
Edit: just realized you were talking about the cards! Those are also just computed and fixed. We know the x/y bounds of the screen so can just push them around to the other side if they don't fit in the default position.
The state of building secure software is rife with pitfalls. It's super easy to forget some flag or config, unintentionally leave some door open or not act quickly enough on the latest CVEs. You can even do most things right, but due to the tech stack you build on having vulnerabilities attackers can exfiltrate data in unexpected ways or gain a foothold to execute arbitrary commands in your infrastructure.
Over a few months I've been building a stack for secure software. It strictly limits what you can do and locks down the execution environment. At the core sits an orchestrator that listens for https connections. It sniffs the connection for the domain to pass the connection too and starts a VM in tens of milliseconds that's associated with that domain. The VM processes the request and sticks around for a few seconds (since requests are often "bursty") after which it gets stopped.
The app VM is very limited; no file system and no network stack (the request/response is mediated over vsock). Each app runs on boot without any other binaries installed so you'd have to pull off a hypervisor escape from within a unikernel in order to gain the a permanent foothold. The VM boots with certificates it uses for the https-connection so the orchestrator only ever sees the encrypted traffic. I ended up needing to make calls to external services so for that I mediated the calls through the orchestrator. The orchestrator checks an app specific allow-list to see if that ip/host is explicitly trusted before setting up a TCP connection. So the app is prevented to talk to anyone which you haven't explicitly allowed.
The above approach works great for stateless servers! But, most apps need a database. You could set this up via allowing connections to an external db, but I figured it would be nice with a similarly locked down approach to persiatence. So I ended up creating a small Linux application that starts on boot and launches postgres. This VM has access to an encrypted disk, but again no network. Instead it just runs on the same host as the VM app. The app-db communication is mediated over vsock (needed a small patch to postgres for this), which incidentally removes all network latency! I ended up setting up an encrypted export of the WAL and feed that asynchronously into a standby postgres on another node. That way data loss is unlikely, but I'm not sure if I should keep this part. The redundancy is nice, but it's quite a bit of code necessary to mediate the transfer and also a bunch to handle failovers etc... I might end up slimming the whole project down a bit.
Still working on my proof of human project, one part is easy, the key management is hard :(
I got sidetracked by problem on my homelab network and then used some AI to slop out a DHCP/DNS and Zeroconf integrated service. Adding NTP next. It's actually been a bit better than I expected.
bearpaw | a day ago
I wanted a place to journal wines and share with friends, so I made one: Chateau St. Émilion.
You're the second to see it. My sister was the first.
Personal logs are private to yourself and the groups you share them with. Guest reviews and articles are public. The web site is for fun -- don't take it too seriously, but if you'd like to contribute a guest review or article, let me know.
(Yes, I know the name is pretentious. Also, I'm a programmer, not a designer, so please cut a little slack.)
benpocalypse | 9 hours ago
Since I've been laid off, I finally have time to work on my static website generator called Markerator. It ingests markdown files, and images, and spits out a website that is pure HTML and CSS, no javascript. I recently added Open Graph support so that links appear correctly as cards when shared on social media, and am just about ready to push a big set of changes that add unit testing, as well as user-definable pagination for the News/Updates/Blog pages.
My next steps are to document the CSS format so that people can add their own themes, as well as come up with some more default themes that ship with Markerator. Once that is done, I'm going to write some more documentation that walk users step-by-step through using it, as well as how to automate deployment using Github actions. That'll be the 1.0.0 release.
I'm finally feeling inspired again. If you want to see what Markerator can produce, I use it for my personal website, Bengineering. Markerator probably isn't ready for primetime yet, but I'm finally getting there. Check it out if you're morbidly curious.
jmpavlec | 4 hours ago
Cool project!
Will you also add mobile responsiveness? I checked out your site, didn't zoom/scale super well on my phone browser.
xk3 | 4 hours ago
I feel like classless CSS as much as possible might make a lot of sense here
Sunbutt23 | a day ago
For work I’m tryna make a replicable Azeroth core deployment that uses llm backends for player bots so we can pull data from the eks cluster and the llm interactions.
pete_the_paper_boat | 15 hours ago
What do you hope to learn from the LLM interactions?
Sunbutt23 | 7 hours ago
Nothing at all. I work for a telemetry company. I hope to generate massive amounts of data on infra and llm usage that can populate some dashboards.
Then I’ll tear it down and make it repeatable so we have the ability to populate those dashboards on demand.
All the while I get to play WoW for work J
HiddenTig | 22 hours ago
I'm attempting to monitize my side project (first time, wish me luck!). It's a daily work tracker I've always wished existed - offline, no data in the cloud (unless you want it), no account required, day focused, automatic movement of tasks not completed, power-user friendly, and infinitely nestable/collapsible. I know a lot about software, a little bit about running a business, but nothing about the nitty gritty stuff it takes to actually launch a product.. so that's been fun figuring all that out. If you want to check it out:
https://app.truetodo.com/
If anyone would like the "pro" features just message me here or DM and I'll send you a code to make it free (feedback much appreciated!)
Gazook89 | 20 hours ago
did you use a library for the onboarding layer and the positioning of those cards? I thought maybe you used Anchor Positioning, but dev tools doesn't show that, so curious if it's library or you made it work yourself.
HiddenTig | 19 hours ago
I stole that one from the first ever job I ever worked :)
No library - The x/y coordinates get calculated to place an appropriate sized div over whatever I'm highlighting and the screen dim around it is created by adding a massive dropshadow around it.
Edit: just realized you were talking about the cards! Those are also just computed and fixed. We know the x/y bounds of the screen so can just push them around to the other side if they don't fit in the default position.
Gazook89 | 9 hours ago
You should check out Anchor Positioning plus Popover APIs. All built into the browser these days
archevel | 9 hours ago
The state of building secure software is rife with pitfalls. It's super easy to forget some flag or config, unintentionally leave some door open or not act quickly enough on the latest CVEs. You can even do most things right, but due to the tech stack you build on having vulnerabilities attackers can exfiltrate data in unexpected ways or gain a foothold to execute arbitrary commands in your infrastructure.
Over a few months I've been building a stack for secure software. It strictly limits what you can do and locks down the execution environment. At the core sits an orchestrator that listens for https connections. It sniffs the connection for the domain to pass the connection too and starts a VM in tens of milliseconds that's associated with that domain. The VM processes the request and sticks around for a few seconds (since requests are often "bursty") after which it gets stopped.
The app VM is very limited; no file system and no network stack (the request/response is mediated over vsock). Each app runs on boot without any other binaries installed so you'd have to pull off a hypervisor escape from within a unikernel in order to gain the a permanent foothold. The VM boots with certificates it uses for the https-connection so the orchestrator only ever sees the encrypted traffic. I ended up needing to make calls to external services so for that I mediated the calls through the orchestrator. The orchestrator checks an app specific allow-list to see if that ip/host is explicitly trusted before setting up a TCP connection. So the app is prevented to talk to anyone which you haven't explicitly allowed.
The above approach works great for stateless servers! But, most apps need a database. You could set this up via allowing connections to an external db, but I figured it would be nice with a similarly locked down approach to persiatence. So I ended up creating a small Linux application that starts on boot and launches postgres. This VM has access to an encrypted disk, but again no network. Instead it just runs on the same host as the VM app. The app-db communication is mediated over vsock (needed a small patch to postgres for this), which incidentally removes all network latency! I ended up setting up an encrypted export of the WAL and feed that asynchronously into a standby postgres on another node. That way data loss is unlikely, but I'm not sure if I should keep this part. The redundancy is nice, but it's quite a bit of code necessary to mediate the transfer and also a bunch to handle failovers etc... I might end up slimming the whole project down a bit.
edoceo | 19 hours ago
Still working on my proof of human project, one part is easy, the key management is hard :(
I got sidetracked by problem on my homelab network and then used some AI to slop out a DHCP/DNS and Zeroconf integrated service. Adding NTP next. It's actually been a bit better than I expected.
kru | 19 hours ago
Are you attempting something akin to what C2PA is doing?
edoceo | 7 hours ago
Similar goal, different approach
HiddenTig | 19 hours ago
Like a captcha type thing? I might be out of the loop
edoceo | 7 hours ago
No, captcha don't work anymore. You need an identity that can be verified but still anonymous.