Azura The Spellkissed

Afaik you don’t need the depends_on at all, it’s basically implied. If you configure the container to use gluetun’s network, it shouldn’t just bypass it even if there’s any problem with the gluetun container. The gluetun documentation also says to just use network_mode: container:gluetun, even when connecting from a divergent compose.yaml. if you want to be sure, maybe test out what happens if that gluetun is down.

“I built”

Not a GUI/webapp, but I like to use ncdu snapshots (“exports”). ncdu is an interactive file browser / disk usage analyzer with a terminal UI, which allow for convenient browsing but also, y’know, figuring out what to delete in case of storage cleanups.

creating a snapshot (“exporting”):
ncdu /pathyouwanttoscan -2 --one-file-system --compress -o snapshot_ncdu.json.zstd

(-2 enables progress bar and error messages during the scan)

reading (“importing”):
ncdu -f snapshot_ncdu.json.zstd

Why do you ask what “made it look like slop” instead of being honest about it?

That would be great. Though I’ve had that not work as expected at the beginning of 2026, but maybe you are right.

Note that you are likely leaking a list of all your subdomains in certificate transparency logs. Some users might not want that to happen, in that case using a wildcard certificate can help, but it’s either more tedious to set up (generating the cert outside of caddy) or less readable (using a Caddyfile with a single domain block for the wildcard containing a handle block per subdomains).

Given that this issue has been shared online and is currently getting quite a few visitors, here’s some additional context.

Rust’s type system is intended to prevent memory unsafety. Upholding this promise is something we take very seriously, which is why we’ve been working on things like the next-generation trait solver, the region constraint rework, and more generally Project Zero. It is a large priority of the Types Team to fix all type system unsoundnesses and to work towards there being a solid foundation to minimize the risk of unknown ones.

This bug is a P-high issue and would have been P-critical regardless of whether people encountered it in the wild. The reason that it is “only P-high” is that it’s 11 years old. A bug like this which has not been found during the last 11 years cannot actually be that easy to hit.

Looking at the bug itself, it is also very likely that this unsoundness has not caused memory unsafety by accident. While it looks easy to trigger, to exploit this you need an intentionally malicious Drop implementation.

Eating pizza like this is quite doable and fun. I even had success ordering a pizza pre-cut like that. However, the very last part (center of the pizza) can be a bit tricky so you you might not be able to slurp the whole thing, depending on the details.

I’m not saying that’s great news, but it doesn’t sound like the self destruction move that some OSS companies have done recently. I wouldn’t migrate away just because of that change. In the end, they have to find a sustainable mode of operation.

Short answer: It depends.

I had no clue 🤯🤯🤯

As always, people overreacting in the comments (of the linked forum). So the current plan is that the core remains OSS, but upcoming features are partially not. To me that sounds similar to Chrome’s or VSCode’s approach.

Ah, right its stored as (rather basic) html instead of markdown.

I love ghost’s UI and feature set.

What complex data format are you taking about? Last time I checked, it was plain markdown in a database (even supporting sqlite).

What I’d recommend though, is coupling it with a static site generator and only using the ghost server for the administration / authoring (guides). That way, serving the blog to visitors is basically free in terms of resources (at last as low as it gets). You could even push these static builds to a CDN (yes yes, selfhost community, I’m just saying it for completeness)

It might be some hassle to set this up somehow, but you could even have the container stopped unless you actively need it. You could even run the server application on your computer instead of the server, unless you want to access is from a smartphone/tablet.

If you really want an alternative to Ghost and don’t need user management and an online WYSIWYG editor, you could go straight to an SSG and feed itraw it markdown files.

Maybe Microsoft devs also sometimes lose focus

Tbf, the MS Team’s search hasn’t failed me yet. Unlike outlook which wouldn’t find an email when searching for the exact subject line, even while I have the email open in another window just to be sure I’m not hallucinating how bad the search is.

Okay, hear me out: what if you click on a contact in your contact list and start typing a message, but instead of writing in the message field, it instead focused a random contact in your contract list whose name starts with the last letter you typed. Anyone? People love this feature, right?

I’m not too convinced FLOSS devs are mentally flexible enough to implement all of the glory of MS Teams.

Doesn’t sound like a technical issue, but a social one

This post describes the construction of an Aho-Corasick automaton for the simultaneous matching of substrings within a sequence. I’m fond of this algorithm because it constructs an automaton from an existing tree data structure in a rather pleasant way.

You would still need to know what you’re looking for, whether that’s an ID (repo name / full IRL) or some (unspecified part of a) repo header. It’s surprising why someone of your skill level asks such an odd, unspecified question. Why do you being up a random idea and ask the community any that’s good or bad? Shouldn’t you offer some arguments as to why you think it’s good from the start, unless it obvious?

The only advantage I can think of would be to more easily find forks or even the same content on different hosts without having to know / verify possibly differing the repo names. But that brings is to the largest downside: security. Git hosters over namespaced repos with configurable access control. Your idea would be susceptible to impersonation, unless you being signing and some novel way to manage trust and verify signatures. Quite some hassle with little benefits 🤔

Why roff? Why not LaTeX or typst? No reason, I just wanted to flex. Also, I believe roff still in 2026 generates PDFs faster than any other markup system by a couple of milliseconds. So one must respect the early UNIX gurus.