Replying to @LynAldenContact
@LynAldenContact I read much of your analysis of Lightning. While much is on-target, and an excellent summary of crypto philosophy, you go exactly where led and no further, begging a discerning reader to connect the dots.
For example, you seem to agree that the higher layers (liquid, lightning, etc) are tradeoffs (volume vs permissionless, identity vs volume, etc). But you do not weigh these tradeoffs verses allowing more activity on L0. And you do not consider technological improvement.
Just want to observe that on Ubuntu getting your ip is "ip address" and on the mac its "ipconfig getifaddr en0".
ClaudeAI is like an idiot savant golden retriever: "oh oh oh can I please access a maven repo, unzip this jar file, decompile this code, and analyze it to figure out what APIs to call!?! Just type 1 to let me gnaw on that!"
Uhh, sure but you know you could just look at the API docs.
Andrew Stone retweeted
It is much more than that.
If you don’t know how to fight in the Balkans, you’ll be taken advantage of in countless ways. That’s simply the reality of life for many people here. From an early age, you’re expected to stand your ground, defend yourself, and grow up fast. You face hardships and situations that many people in the Western world may never experience.
Those experiences shape you. You learn to read people, sense danger, and think several steps ahead because you often have no other choice. Your intuition becomes razor sharp, your instincts become second nature, and you learn to adapt to almost any situation. The struggles and traumas you go through can leave scars, but they can also forge resilience, discipline, and a mindset that helps you withstand whatever life throws at you.
You learn early that complaining rarely changes your circumstances. Instead, you become your own source of strength. You rely on yourself, focus on solutions instead of problems, and learn to think quickly under pressure. When life keeps testing you, you either freeze or adapt. For many people, adapting becomes second nature. You stop expecting life to be fair and start finding a way forward, no matter what’s in front of you.
Prior AI conversations will comprise the majority of the training data for subsequent generations. This privately owned and held data will greatly reduce the internet's role to as a universal and globally accessible information source, and create a huge barrier to entry for new AIs.
Why in modern API design do the simplest, most common things have to have the longest names? kotlin.time.Clock.System.now().toEpochMilliseconds()
UI design philosophy: UI "detailing" acts to increase comprehension and usability. However once an app achieves a certain level in that, detailing becomes a sales tool -- it is meant to catch the eye and encourage use through rewards, excitement, and beauty. There are 3 fundamental tools for that -- novelty, movement, and contrast. Movement and contrast are well known to activate primitive attention circuits in humans (for evolutionary survival reasons). Novelty activates interest due to curiosity (also a primitive neural circuit). However, it is possible to over-activate these circuits, resulting in user fatigue. And if UI elements delay interaction too much, experienced users may become impatient and bored.
When multiple inputs are pulled into a transaction, there is no connection between a particular satoshi coming in and one going out. You could choose an arbitrary ordering (like Ordinals does), but that is just a convention. Very early, people were calculating "taint" which is the idea of spreading all inputs across all outputs, proportionally.
In contrast, most fiat bills have a serial number.
Features/functionality (needs!) should drive upgrading technology. Technology should not drive its own upgrade.
Developing a crypto contract language as a @kotlin DSL (domain specific language) has interesting advantages. You can have an instruction either actually calc the results or generate code depending on whether all inputs are known. This lets your compiler pre-calc any constants.
But here's the cool part: if you define EVERY input, your compiler becomes an interpreter, and you can use the kotlin IDE source debugger to step thru your code, use the test infra to make unit tests, etc. @NexaMoney leverages any IDE (@jetbrains IDEA for example) for contract dev and debug!
The more I look at the web dev space, the more it feels like people making problems for themselves. Take the front end/back end separation. Why invite this CORS config hell? Everything from cloudflare to apache wants to cache and serve your front end anyway. Your back end will not see that traffic -- except for one important time: during dev when its super convenient serve them all from one executable.
The Nexa VM (extended from Bitcoin/Satoshi) is a stack based language. This means that instructions apply to the top of the stack, not registers. So compilers must efficiently reorder the stack before instruction execution and are presented with transformation problems like (0,1,2,3,4) -> (2,3,0,1,4).
We could manually write xform code, but that typically gives inefficient results, and is tricky work. Instead we seed a DB with the basic opcodes and randomly combine entries to construct programs, always picking the shortest program for each xform. After a minute or so we have 20M short programs, which covers almost all needed xforms!
According to the @NYtimes and @yaffebellany being treated equivalently is "...advanc[ing] the crypto industry's agenda." nytimes.com/2025/07/30/techn…, not financial freedom. However, WRT the environment they "...hoped it would send a signal to the world." nytimes.com/2024/12/19/clima…







