sexworker statistician/useful science sources namespace collision joke
aella.inference.net/embeddings
aella.inference.net/embeddings
November 12, 2025 at 10:12 PM
sexworker statistician/useful science sources namespace collision joke
aella.inference.net/embeddings
aella.inference.net/embeddings
The worst part is that most implementations of cstdint put the types in the global namespace anyways. see stackoverflow.com/questions/13...
November 11, 2025 at 10:15 AM
The worst part is that most implementations of cstdint put the types in the global namespace anyways. see stackoverflow.com/questions/13...
"Before `@layer` came along, CSS developers faced constant battles with specificity."
Sounds exaggerated.
Learning how selectors really work could prevent a lot of confusion around specificity I think, to me @layer feels a lot like adding a wrapper div to namespace styles.
Sounds exaggerated.
Learning how selectors really work could prevent a lot of confusion around specificity I think, to me @layer feels a lot like adding a wrapper div to namespace styles.
November 10, 2025 at 10:34 AM
"Before `@layer` came along, CSS developers faced constant battles with specificity."
Sounds exaggerated.
Learning how selectors really work could prevent a lot of confusion around specificity I think, to me @layer feels a lot like adding a wrapper div to namespace styles.
Sounds exaggerated.
Learning how selectors really work could prevent a lot of confusion around specificity I think, to me @layer feels a lot like adding a wrapper div to namespace styles.
i guess the argument is always 'dont pollute global namespace' and in a world of composable software libraries and mashing together code you don't own/understand or cant change, I guess that's good advice. but for reasons I can't quite articulate in <100 chars, I... choose to reject that world.
November 11, 2025 at 10:01 AM
i guess the argument is always 'dont pollute global namespace' and in a world of composable software libraries and mashing together code you don't own/understand or cant change, I guess that's good advice. but for reasons I can't quite articulate in <100 chars, I... choose to reject that world.
Bon, Laurent arrive et va vous pourrir votre chill devant une série avec cet article de touuuuuute beauté sur l'interne derrière Docker (unshare, namespace, ..).
Dites merci à Laurent pour votre insomnie.
Dites merci à Laurent pour votre insomnie.
Understanding Docker Internals: Building a minimal Container Runtime with Python on Linux using Namespaces, Control Groups and Filesystem Isolation #Docker #Linux muhammadraza.me/2024/buildin...
Understanding Docker Internals: Building a Container Runtime in Python | Muhammad
Breaking down container technology by building a simple container runtime from scratch using Python and Linux primitives like namespaces and cgroups
muhammadraza.me
October 30, 2025 at 9:08 PM
Bon, Laurent arrive et va vous pourrir votre chill devant une série avec cet article de touuuuuute beauté sur l'interne derrière Docker (unshare, namespace, ..).
Dites merci à Laurent pour votre insomnie.
Dites merci à Laurent pour votre insomnie.
so this means it requires good judgement calls on the side of whoever’s designing the spec — is it actually about global execution semantics? is it simple enough that it won’t need to evolve in incompatible ways? does the value to the ecosystem justify squatting a global namespace?
October 30, 2025 at 1:20 AM
so this means it requires good judgement calls on the side of whoever’s designing the spec — is it actually about global execution semantics? is it simple enough that it won’t need to evolve in incompatible ways? does the value to the ecosystem justify squatting a global namespace?
Hi I'm Dean. I'm 27, I like corn dogs, and my hobbies include cluttering the global namespace.
October 27, 2025 at 11:45 PM
Hi I'm Dean. I'm 27, I like corn dogs, and my hobbies include cluttering the global namespace.
If I had even remotely believed this trainwreck timeline would become real, I would have made skywitches.net into a namespace, then a PDS, then a full site, and engineered it that way from the beginning.
I should have listened to my intuition
I should have listened to my intuition
October 27, 2025 at 6:55 PM
If I had even remotely believed this trainwreck timeline would become real, I would have made skywitches.net into a namespace, then a PDS, then a full site, and engineered it that way from the beginning.
I should have listened to my intuition
I should have listened to my intuition
My parents put me in timeout for cluttering the global namespace. 😡
October 27, 2025 at 11:48 PM
My parents put me in timeout for cluttering the global namespace. 😡
Our users would rebel if we made them have separate closing tags. IIRC self-closing tags _are_ allowed outside the HTML namespace, so just think of these as being from the Svelte namespace
October 26, 2025 at 7:11 PM
Our users would rebel if we made them have separate closing tags. IIRC self-closing tags _are_ allowed outside the HTML namespace, so just think of these as being from the Svelte namespace
I've published a new issue of Behind the PowerShell Pipeline: A Namespace Scripting Solution
Become a premium member to read the entire article and get access to the catalog of content going back to 2022. #PowerShell
Become a premium member to read the entire article and get access to the catalog of content going back to 2022. #PowerShell
A Namespace Scripting Solution
buttondown.com
October 25, 2025 at 6:56 PM
I've published a new issue of Behind the PowerShell Pipeline: A Namespace Scripting Solution
Become a premium member to read the entire article and get access to the catalog of content going back to 2022. #PowerShell
Become a premium member to read the entire article and get access to the catalog of content going back to 2022. #PowerShell
My understanding is that 4.0 moniker is more to celebrate the 30 year anniversary than any breaking change. Ractors being stable (yet possibly still marked as experimental since the API may still change), ZJIT and the introduction of Namespace might end up being the headline features of 4.0.
October 24, 2025 at 8:54 PM
My understanding is that 4.0 moniker is more to celebrate the 30 year anniversary than any breaking change. Ractors being stable (yet possibly still marked as experimental since the API may still change), ZJIT and the introduction of Namespace might end up being the headline features of 4.0.
The irony is that Olivetti's series of Prodest models only seems to contain three models: PC128, PC128S and PC1 (which is the only directly IBM PC compatible and one that I used to own). So there should have been plenty of namespace within Prodest.
October 23, 2025 at 5:02 PM
The irony is that Olivetti's series of Prodest models only seems to contain three models: PC128, PC128S and PC1 (which is the only directly IBM PC compatible and one that I used to own). So there should have been plenty of namespace within Prodest.
One confusingly named one is the True Holy Rune, which, despite the name, is not a True Rune. It was both a bit of weird localization and namespace limitations, as the original Kanji translates to something like "True Divine Transportation Method Rune".
October 21, 2025 at 3:05 PM
One confusingly named one is the True Holy Rune, which, despite the name, is not a True Rune. It was both a bit of weird localization and namespace limitations, as the original Kanji translates to something like "True Divine Transportation Method Rune".
Shared feed generators: Right now, feed generators exist as records inside a particular PDS, typically owned by a single account. It feels awkward that something like a community curated feed must live under one person's namespace
October 18, 2025 at 12:53 AM
Shared feed generators: Right now, feed generators exist as records inside a particular PDS, typically owned by a single account. It feels awkward that something like a community curated feed must live under one person's namespace
this makes me remember that elements with an id are also just available in the window namespace anyway is that fucked up
October 17, 2025 at 8:02 PM
this makes me remember that elements with an id are also just available in the window namespace anyway is that fucked up
1. Use git (use GitHub)
Every analysis I've done in 2025 is a repo. GAME CHANGER.
2. Namespace everything
Every function should include pkg::fun. EVERY FUNCTION.
3. Use air formatter
Automatic formatting. IT DOES SAVE TIME.
🧵
Every analysis I've done in 2025 is a repo. GAME CHANGER.
2. Namespace everything
Every function should include pkg::fun. EVERY FUNCTION.
3. Use air formatter
Automatic formatting. IT DOES SAVE TIME.
🧵
October 16, 2025 at 5:18 PM
1. Use git (use GitHub)
Every analysis I've done in 2025 is a repo. GAME CHANGER.
2. Namespace everything
Every function should include pkg::fun. EVERY FUNCTION.
3. Use air formatter
Automatic formatting. IT DOES SAVE TIME.
🧵
Every analysis I've done in 2025 is a repo. GAME CHANGER.
2. Namespace everything
Every function should include pkg::fun. EVERY FUNCTION.
3. Use air formatter
Automatic formatting. IT DOES SAVE TIME.
🧵
Chybí ti tam středník, and winners don't do using namespace std;.
October 14, 2025 at 6:14 AM
Chybí ti tam středník, and winners don't do using namespace std;.
tbh ive never used the API docs ... i just read the lexicon. its typically more useful anyways + is the actual source of truth
though i feel like at least some of the com.atproto.* namespace should be spec at some point and/or migrated to a special case spec defined NSID
though i feel like at least some of the com.atproto.* namespace should be spec at some point and/or migrated to a special case spec defined NSID
October 14, 2025 at 10:14 AM
tbh ive never used the API docs ... i just read the lexicon. its typically more useful anyways + is the actual source of truth
though i feel like at least some of the com.atproto.* namespace should be spec at some point and/or migrated to a special case spec defined NSID
though i feel like at least some of the com.atproto.* namespace should be spec at some point and/or migrated to a special case spec defined NSID
new typelex release
there's a new @typelex/cli, which you can use to add typelex to any project with a single command: typelex.org#install
it now keeps track of the existing JSON lexicons/ outside your app's namespace and makes them available in your typelex files
there's a new @typelex/cli, which you can use to add typelex to any project with a single command: typelex.org#install
it now keeps track of the existing JSON lexicons/ outside your app's namespace and makes them available in your typelex files
October 10, 2025 at 8:39 PM
new typelex release
there's a new @typelex/cli, which you can use to add typelex to any project with a single command: typelex.org#install
it now keeps track of the existing JSON lexicons/ outside your app's namespace and makes them available in your typelex files
there's a new @typelex/cli, which you can use to add typelex to any project with a single command: typelex.org#install
it now keeps track of the existing JSON lexicons/ outside your app's namespace and makes them available in your typelex files
new feature in @typelex/[email protected]:
"externals"
namespaces tagged with @external are assumed to be coming from somewhere else (like JSON in your lexicons/ folder)
typelex wont't try to emit them in the output, but it will assume that each of these things exists (and won't error on them)
"externals"
namespaces tagged with @external are assumed to be coming from somewhere else (like JSON in your lexicons/ folder)
typelex wont't try to emit them in the output, but it will assume that each of these things exists (and won't error on them)
October 10, 2025 at 2:19 AM
new feature in @typelex/[email protected]:
"externals"
namespaces tagged with @external are assumed to be coming from somewhere else (like JSON in your lexicons/ folder)
typelex wont't try to emit them in the output, but it will assume that each of these things exists (and won't error on them)
"externals"
namespaces tagged with @external are assumed to be coming from somewhere else (like JSON in your lexicons/ folder)
typelex wont't try to emit them in the output, but it will assume that each of these things exists (and won't error on them)
This is possible though. Someone who is running an app on an entirely different namespace could easily moderate just the content that is relevant to their namespace.
October 8, 2025 at 6:54 PM
This is possible though. Someone who is running an app on an entirely different namespace could easily moderate just the content that is relevant to their namespace.
Effectively, the AppView winds up locally doing a logical JOIN across its copy of three kinds of data:
- raw content records
- matching label records
- user moderation config records
... with the last category acting as a namespace filter to only include records from specific labelers
- raw content records
- matching label records
- user moderation config records
... with the last category acting as a namespace filter to only include records from specific labelers
October 8, 2025 at 9:17 PM
Effectively, the AppView winds up locally doing a logical JOIN across its copy of three kinds of data:
- raw content records
- matching label records
- user moderation config records
... with the last category acting as a namespace filter to only include records from specific labelers
- raw content records
- matching label records
- user moderation config records
... with the last category acting as a namespace filter to only include records from specific labelers
this global namespace offers amazing reach to psyops and infowarriors. they want bad person to stop influencing impressionable low-information voters. i don't think the individuals-and-states framing is helpful here, moderation is all about the squishy social aggregation layers
October 7, 2025 at 7:12 AM
this global namespace offers amazing reach to psyops and infowarriors. they want bad person to stop influencing impressionable low-information voters. i don't think the individuals-and-states framing is helpful here, moderation is all about the squishy social aggregation layers