Namespaces version of the Bacon Muncher
October 17, 2024 at 7:06 PM
Namespaces version of the Bacon Muncher
Cargo's Law: As an online discussion about Cargo grows longer, the probability of namespaces being brought up approaches 1
January 28, 2025 at 6:34 PM
Cargo's Law: As an online discussion about Cargo grows longer, the probability of namespaces being brought up approaches 1
wrote up a little thing
AT Namespaces for Community Spaces
How should public community-controlled spaces be represented in atproto?
bnewbold.leaflet.pub
October 11, 2025 at 10:11 PM
wrote up a little thing
Kubernetes v1.33: User Namespaces enabled by default!-
Kubernetes v1.33: User Namespaces enabled by default!
In Kubernetes v1.33 support for user namespaces is enabled by default. This means that, when the stack requirements are met, pods can opt-in to use user namespaces. To use the feature there is no need...
kubernetes.io
April 25, 2025 at 7:52 PM
Kubernetes v1.33: User Namespaces enabled by default!-
Cgroups, namespaces, and anti-fascism: building the world we all want to live in.💕💜💗🧊🚫
Genuinely very funny to me that people who were apparently fine with me posting Fuck ICE and Chinga la Migra all day long unfollowed me when I started posting UNIX facts
September 13, 2026 at 6:21 PM
Cgroups, namespaces, and anti-fascism: building the world we all want to live in.💕💜💗🧊🚫
it's namespaces all the way down
April 28, 2023 at 1:10 PM
it's namespaces all the way down
starting the day by learning about XML namespaces
more effective than coffee
more effective than coffee
December 4, 2025 at 7:21 AM
starting the day by learning about XML namespaces
more effective than coffee
more effective than coffee
TypeScript offers two syntaxes for declaring namespaces.
module ns {...} // deprecated
namespace ns {...} // modern
TypeScript 6.0 will only support the second form.
module ns {...} // deprecated
namespace ns {...} // modern
TypeScript 6.0 will only support the second form.
TypeScript 6.0: use the namespace keyword instead of module (when appropriate)
🔫 we are no longer asking
🔫 we are no longer asking
December 11, 2025 at 6:54 AM
TypeScript offers two syntaxes for declaring namespaces.
module ns {...} // deprecated
namespace ns {...} // modern
TypeScript 6.0 will only support the second form.
module ns {...} // deprecated
namespace ns {...} // modern
TypeScript 6.0 will only support the second form.
private content is one of the top asks of atproto, we have some ideas. leading designs involve each user having multiple private repos. they differ from your public repo as they are access-controlled and not signed/redistributable. but they are still key->value, addressable, and of course they sync!
November 3, 2024 at 11:45 PM
private content is one of the top asks of atproto, we have some ideas. leading designs involve each user having multiple private repos. they differ from your public repo as they are access-controlled and not signed/redistributable. but they are still key->value, addressable, and of course they sync!
They didn't even change the class names or namespaces.
I'm so fuckin' tired, man.
I'm so fuckin' tired, man.
It's like... you do your due diligence, but then the modders find shit generated by ChatGPT in the code, and all you can do is just stare and laugh incredulously.
September 5, 2026 at 4:38 PM
They didn't even change the class names or namespaces.
I'm so fuckin' tired, man.
I'm so fuckin' tired, man.
Two updates to the Node/TS announcement:
- Node 22 WILL be getting TypeScript support by default.
- Type-only namespaces (which I actually have started using and quite like) will be supported by default.
www.totaltypescript.com/typescript-i...
- Node 22 WILL be getting TypeScript support by default.
- Type-only namespaces (which I actually have started using and quite like) will be supported by default.
www.totaltypescript.com/typescript-i...
December 28, 2024 at 9:51 AM
Two updates to the Node/TS announcement:
- Node 22 WILL be getting TypeScript support by default.
- Type-only namespaces (which I actually have started using and quite like) will be supported by default.
www.totaltypescript.com/typescript-i...
- Node 22 WILL be getting TypeScript support by default.
- Type-only namespaces (which I actually have started using and quite like) will be supported by default.
www.totaltypescript.com/typescript-i...
Federated Agentic Namespaces, an atproto native plan9 federated filesystem for tools and mcp:
an initial draft: gist.github.com/ewindisch/f1...
an initial draft: gist.github.com/ewindisch/f1...
Federated Agentic Namespaces Draft
Federated Agentic Namespaces Draft. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
May 27, 2026 at 9:09 PM
Federated Agentic Namespaces, an atproto native plan9 federated filesystem for tools and mcp:
an initial draft: gist.github.com/ewindisch/f1...
an initial draft: gist.github.com/ewindisch/f1...
Sigil
Sigil is a low-level container runtime written in Rust. It implements process supervision, Linux namespaces, filesystem isolation, and cgroups from scratch to demonstrate how containers actually work under the hood.
Sigil is a low-level container runtime written in Rust. It implements process supervision, Linux namespaces, filesystem isolation, and cgroups from scratch to demonstrate how containers actually work under the hood.
April 20, 2026 at 1:02 AM
Sigil
Sigil is a low-level container runtime written in Rust. It implements process supervision, Linux namespaces, filesystem isolation, and cgroups from scratch to demonstrate how containers actually work under the hood.
Sigil is a low-level container runtime written in Rust. It implements process supervision, Linux namespaces, filesystem isolation, and cgroups from scratch to demonstrate how containers actually work under the hood.
Namespaces 101
During the last days I have done an immersion into namespaces, the new big feature that is coming in Ruby.
Here's a digested mental model for you all.
gist.github.com/fxn/86ad8584...
During the last days I have done an immersion into namespaces, the new big feature that is coming in Ruby.
Here's a digested mental model for you all.
gist.github.com/fxn/86ad8584...
namespaces.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
May 15, 2025 at 12:03 PM
Namespaces 101
During the last days I have done an immersion into namespaces, the new big feature that is coming in Ruby.
Here's a digested mental model for you all.
gist.github.com/fxn/86ad8584...
During the last days I have done an immersion into namespaces, the new big feature that is coming in Ruby.
Here's a digested mental model for you all.
gist.github.com/fxn/86ad8584...
#atproto: let's do personal-private data right now
second repo adjacent to the public one with the same semantics but not published
oauth scopes for read/write access to various NSID namespaces
ezpz
second repo adjacent to the public one with the same semantics but not published
oauth scopes for read/write access to various NSID namespaces
ezpz
October 22, 2025 at 5:00 AM
#atproto: let's do personal-private data right now
second repo adjacent to the public one with the same semantics but not published
oauth scopes for read/write access to various NSID namespaces
ezpz
second repo adjacent to the public one with the same semantics but not published
oauth scopes for read/write access to various NSID namespaces
ezpz
Kubernetes v1.36: User Namespaces in Kubernetes are finally GA-
Kubernetes v1.36: User Namespaces in Kubernetes are finally GA
After several years of development, User Namespaces support in Kubernetes reached General Availability (GA) with the v1.36 release. This is a Linux-only feature. For those of us working on low level container...
kubernetes.io
April 24, 2026 at 7:52 PM
Kubernetes v1.36: User Namespaces in Kubernetes are finally GA-
My learning journey with #MicrosoftFabric
December 11, 2024 at 11:18 AM
My learning journey with #MicrosoftFabric
we should start a new superglobal namespaces for other root namespaces to be registered within, preventing namespace name collisions
July 12, 2023 at 12:18 PM
we should start a new superglobal namespaces for other root namespaces to be registered within, preventing namespace name collisions
A flag which bans TS features with runtime emit (enums, namespaces, experimental decorators, etc) will come in 5.8 to help people executing TS code via Node.js (or who want to avoid using those features for "reasons").
November 23, 2024 at 6:21 AM
A flag which bans TS features with runtime emit (enums, namespaces, experimental decorators, etc) will come in 5.8 to help people executing TS code via Node.js (or who want to avoid using those features for "reasons").
kinda sucks that some of the most nominally-trustworthy namespaces have some of the worst security posture
November 19, 2024 at 7:02 PM
kinda sucks that some of the most nominally-trustworthy namespaces have some of the worst security posture
