Загрузка видео...

Не удалось загрузить видео

На главную

Aptos Labs built the parallel execution design that other chains went on to adopt Running a block one transaction at a time does not scale. One slow transaction stalls everything queued behind it, and throughput collapses under load. One approach asks developers to list in advance every piece of...

BSCNews's profile picture

BSCN

1,372,639 subscribers

19,231 просмотров • 6 дней назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

A RUSSIAN MATHEMATICIAN BUILT A SYSTEM WHERE MEMORY AND EVAL WORK AS ONE PIPELINE NOT TWO SEPARATE TOOLS Most setups run memory and evaluation as separate systems that never actually talk to each other. He wired them into one loop instead, memory stores every past output, eval scores each one before it gets kept. Anything that scores low never enters memory at all, so nothing weak gets carried into future decisions. High scorers get tagged with the exact eval criteria they passed, not just a raw pass or fail. The next task pulls only memories that passed the same bar it's about to be judged on. See how the two systems feed each other below👇
0:14

A RUSSIAN MATHEMATICIAN BUILT A SYSTEM WHERE MEMORY AND EVAL WORK AS ONE PIPELINE NOT TWO SEPARATE TOOLS Most setups run memory and evaluation as separate systems that never actually talk to each other. He wired them into one loop instead, memory stores every past output, eval scores each one before it gets kept. Anything that scores low never enters memory at all, so nothing weak gets carried into future decisions. High scorers get tagged with the exact eval criteria they passed, not just a raw pass or fail. The next task pulls only memories that passed the same bar it's about to be judged on. See how the two systems feed each other below👇

wast3

39,872 просмотров • 1 месяц назад

Somewhere around sixty you get handed a new set of instructions. Lift lighter. Keep the reps high. Do not tax yourself too much. Put the saved effort into cardio. It is the exact reverse of what an ageing body needs, and the people handing it out have the mechanism sitting right in front of them. Recovery gets worse with age. Nobody argues with that. The older body clears fatigue more slowly, repairs more slowly, and tolerates far less accumulated work before progress stops entirely. Every GP, every physio, every trainer will nod along to that sentence. Then watch what gets prescribed on the back of it. High reps. Long burning sets. Circuits. Three sessions of cardio stacked on top. A protocol whose main product is fatigue, given to the person with the least capacity left to absorb any. They identified a recovery problem and prescribed more recovery cost. The answer runs the other way and it is not complicated. If your recovery budget has shrunk, you spend it on whatever returns the most growth per unit of fatigue, and that is a heavy set of five. Four to six reps, a handful of lifts, three minutes between sets, done inside the hour. Nearly every rep is a growth rep. Almost nothing goes on the burning, the sweating and the gasping, which build nothing at all and then bill you for four days. Twenty-five reps taken to failure is a fortnight of fatigue for a fraction of the stimulus. That is not the cautious option for a sixty-five-year-old. It is the most reckless thing on the timetable. Now the part that actually matters. Ageing is not one process. It is a list. Muscle wastes. Bone thins. Tendon softens. The fast fibres that catch you when the pavement arrives early vanish first while the slow ones sit there in perfect health. Motor units drop out. The nervous system stops asking for full effort because nothing has demanded full effort in fifteen years. Read that list back and tell me what heavy resistance training does. It builds muscle. It loads bone, which is the only language bone speaks. It stiffens tendon. It recruits the fast fibres, because that is what heavy means physiologically and there is no other route in. It forces the nervous system to ask for everything again. Every item on the list of what ageing takes is on the list of what a heavy set gives back. Nothing else on earth does that. Not a walk, not a class, not a pill, not twenty minutes on a machine with the paper open. You were told to go gently because somebody quietly decided you were finishing. Go heavy, because you are not.
0:19

Somewhere around sixty you get handed a new set of instructions. Lift lighter. Keep the reps high. Do not tax yourself too much. Put the saved effort into cardio. It is the exact reverse of what an ageing body needs, and the people handing it out have the mechanism sitting right in front of them. Recovery gets worse with age. Nobody argues with that. The older body clears fatigue more slowly, repairs more slowly, and tolerates far less accumulated work before progress stops entirely. Every GP, every physio, every trainer will nod along to that sentence. Then watch what gets prescribed on the back of it. High reps. Long burning sets. Circuits. Three sessions of cardio stacked on top. A protocol whose main product is fatigue, given to the person with the least capacity left to absorb any. They identified a recovery problem and prescribed more recovery cost. The answer runs the other way and it is not complicated. If your recovery budget has shrunk, you spend it on whatever returns the most growth per unit of fatigue, and that is a heavy set of five. Four to six reps, a handful of lifts, three minutes between sets, done inside the hour. Nearly every rep is a growth rep. Almost nothing goes on the burning, the sweating and the gasping, which build nothing at all and then bill you for four days. Twenty-five reps taken to failure is a fortnight of fatigue for a fraction of the stimulus. That is not the cautious option for a sixty-five-year-old. It is the most reckless thing on the timetable. Now the part that actually matters. Ageing is not one process. It is a list. Muscle wastes. Bone thins. Tendon softens. The fast fibres that catch you when the pavement arrives early vanish first while the slow ones sit there in perfect health. Motor units drop out. The nervous system stops asking for full effort because nothing has demanded full effort in fifteen years. Read that list back and tell me what heavy resistance training does. It builds muscle. It loads bone, which is the only language bone speaks. It stiffens tendon. It recruits the fast fibres, because that is what heavy means physiologically and there is no other route in. It forces the nervous system to ask for everything again. Every item on the list of what ageing takes is on the list of what a heavy set gives back. Nothing else on earth does that. Not a walk, not a class, not a pill, not twenty minutes on a machine with the paper open. You were told to go gently because somebody quietly decided you were finishing. Go heavy, because you are not.

Sama Hoole

16,526 просмотров • 1 месяц назад

SOMEONE BUILT A TERMINAL TORRENT CLIENT THAT SEARCHES EVERY TRUSTED SOURCE AT ONCE AND DOWNLOADS STRAIGHT TO DISK finding a torrent in 2026 is miserable fake download buttons, popups that spawn three more tabs, and half the results are dead with zero seeders. so he built the opposite of all that: > type one query and it hits a curated set of trackers all at once > results stream back tagged with source, size and seeders as fast as each site answers > arrow to the one you want, press d, and it lands on your drive > if one source is down it just skips it and keeps searching the rest > downloads run in the background and pick up where they left off if you quit mid transfer the whole thing is one command. npx and youre running, all you need is node, no browser, no setup, nothing leaves your machine except the request itself. its called torlink, open source and mit. this is the kind of clean terminal tool that does one annoying thing perfectly
0:16

SOMEONE BUILT A TERMINAL TORRENT CLIENT THAT SEARCHES EVERY TRUSTED SOURCE AT ONCE AND DOWNLOADS STRAIGHT TO DISK finding a torrent in 2026 is miserable fake download buttons, popups that spawn three more tabs, and half the results are dead with zero seeders. so he built the opposite of all that: > type one query and it hits a curated set of trackers all at once > results stream back tagged with source, size and seeders as fast as each site answers > arrow to the one you want, press d, and it lands on your drive > if one source is down it just skips it and keeps searching the rest > downloads run in the background and pick up where they left off if you quit mid transfer the whole thing is one command. npx and youre running, all you need is node, no browser, no setup, nothing leaves your machine except the request itself. its called torlink, open source and mit. this is the kind of clean terminal tool that does one annoying thing perfectly

Om Patel

361,539 просмотров • 2 месяцев назад

bUT WhAt CaN YoU Do WiTh ThoSE PRoOfs ? Here you go: TrustMeBro is a showcase of a mini ZK-ready Bitcoin explorer where anyone can verify transaction and block validity right in their browser, instant, trustless, no middlemen. Think about it like TLS. 99.99% of people browsing the web have no clue how a secure session actually works, but they've all internalised that green lock meaning "you're safe." ZK can be the same. Run a local verification under the hood, flash a simple badge, verified or not, and boom! Starknet tech looking good from here. As I said many times, Bitcoin x STARKs is a math match made in heaven. Won't stop till the whole damn world is proven. One STARK at a time.
0:19

bUT WhAt CaN YoU Do WiTh ThoSE PRoOfs ? Here you go: TrustMeBro is a showcase of a mini ZK-ready Bitcoin explorer where anyone can verify transaction and block validity right in their browser, instant, trustless, no middlemen. Think about it like TLS. 99.99% of people browsing the web have no clue how a secure session actually works, but they've all internalised that green lock meaning "you're safe." ZK can be the same. Run a local verification under the hood, flash a simple badge, verified or not, and boom! Starknet tech looking good from here. As I said many times, Bitcoin x STARKs is a math match made in heaven. Won't stop till the whole damn world is proven. One STARK at a time.

abdel

32,110 просмотров • 11 месяцев назад

Here's an excellent video from Florian (follow) that shows charged water on the left and neutral water in the right. This is a visual confirmation of two known effects; Electrostatic induction and dielectric relaxation time. Electrostatic induction is like when a hair-rubbed balloon sticks to the wall, despite the wall being neutral; the balloon causes charges in the wall to polarize so the wall side near the balloon turns negative and the other side of the wall is positive. That's electrostatic induction and that's why you have raindrops that stick to a car window for hours of wind and gravity, rain has a small negative charge. Wouldn't work with tap water. Now, if you remove the balloon, the wall doesn't return to a neutral state immediately. It'd happen quickly if we had a balloon on the other side of the wall, but by itself this can take seconds, minutes, hours or even days, depending on the material and thickness. Glass is quite slow, and you can see the electric forces holding each other will hold off gravity for some time; and that the water greatly prefers not to be broken off, water is like an uncountable number of those walls in series, and they all cling to each other in proportion to how many balloons we have, ie how many excess electrons we have. Furthermore, when the water is extremely charged, it will not even leave the thin remnant layer of water that trails behind, as the cohesive internal forces outweigh those by induced to outside neutral surfaces.
0:17

Here's an excellent video from Florian (follow) that shows charged water on the left and neutral water in the right. This is a visual confirmation of two known effects; Electrostatic induction and dielectric relaxation time. Electrostatic induction is like when a hair-rubbed balloon sticks to the wall, despite the wall being neutral; the balloon causes charges in the wall to polarize so the wall side near the balloon turns negative and the other side of the wall is positive. That's electrostatic induction and that's why you have raindrops that stick to a car window for hours of wind and gravity, rain has a small negative charge. Wouldn't work with tap water. Now, if you remove the balloon, the wall doesn't return to a neutral state immediately. It'd happen quickly if we had a balloon on the other side of the wall, but by itself this can take seconds, minutes, hours or even days, depending on the material and thickness. Glass is quite slow, and you can see the electric forces holding each other will hold off gravity for some time; and that the water greatly prefers not to be broken off, water is like an uncountable number of those walls in series, and they all cling to each other in proportion to how many balloons we have, ie how many excess electrons we have. Furthermore, when the water is extremely charged, it will not even leave the thin remnant layer of water that trails behind, as the cohesive internal forces outweigh those by induced to outside neutral surfaces.

N'Golo⚡Wizard.Talk

22,198 просмотров • 3 месяцев назад

Day 11/90 of Inference Engineering How does vLLM work and how is it used in production? Before we discuss how vLLM works internally, it helps to understand what vLLM is. At a high level, vLLM is an inference engine that is designed to serve LLMs to thousands of concurrent users efficiently while managing scarce compute and memory. The goal for vLLM is to maximize throughput and minimize latency; optimizing for the best inference economics and experience for end users. With every request from the end user, it eventually ends up in the engine core, gets scheduled alongside other requests from other concurrent users, executes on the GPU, and updates the KV cache with the new key and value vectors, and streams the tokens back to the user. The Scheduler decides what requests should execute next while continuously batching requests together to maximize GPU utilization. Continuous batching is an inference optimization that allows new requests to join a running batch as other requests finish generating tokens. This helps with keeping the GPU utilization high instead of letting it sit idle waiting for an entire batch to complete generating. After the scheduler dispatches the selected batch to the Model Executor, the Model Executor prepares the tensors and metadata required for inference, retrieves each request’s block table from KV Cache Manager, launches the optimized transformer forward pass on the GPU, computes the logits, updates the KV cache with the new key and value vectors, and finally returns the results for sampling and streaming. The KV Cache Manager uses the PagedAttention memory layout to allocate fixed-size cache blocks on demand and maintains a Free Block Queue on the CPU that tracks which blocks in the GPU’s Paged KV Cache are currently free. When a request needs additional KV cache space, the KV Cache manager takes a free block from the queue and assigns it to that request, thus avoiding an expensive search through GPU memory for available cache blocks. All of these components form the core of vLLM’s inference engine. The Scheduler determines what requests are executed, the Model Executor determines how those requests are executed, the KV Cache Manager determines where each request’s KV cache lives using the PagedAttention Memory Layout. This architecture enables vLLM to serve thousands of concurrent requests with high throughput, low latency, and efficient GPU memory utilization. Heres a little animation that visualizes everything! - I've also completed the forward pass for my mnist.c project. I had a nice chat with shrey birmiwal, such a knowledgeable guy. Excited to learn more about vLLM and implement a tiny-vLLM one day.
0:14

Day 11/90 of Inference Engineering How does vLLM work and how is it used in production? Before we discuss how vLLM works internally, it helps to understand what vLLM is. At a high level, vLLM is an inference engine that is designed to serve LLMs to thousands of concurrent users efficiently while managing scarce compute and memory. The goal for vLLM is to maximize throughput and minimize latency; optimizing for the best inference economics and experience for end users. With every request from the end user, it eventually ends up in the engine core, gets scheduled alongside other requests from other concurrent users, executes on the GPU, and updates the KV cache with the new key and value vectors, and streams the tokens back to the user. The Scheduler decides what requests should execute next while continuously batching requests together to maximize GPU utilization. Continuous batching is an inference optimization that allows new requests to join a running batch as other requests finish generating tokens. This helps with keeping the GPU utilization high instead of letting it sit idle waiting for an entire batch to complete generating. After the scheduler dispatches the selected batch to the Model Executor, the Model Executor prepares the tensors and metadata required for inference, retrieves each request’s block table from KV Cache Manager, launches the optimized transformer forward pass on the GPU, computes the logits, updates the KV cache with the new key and value vectors, and finally returns the results for sampling and streaming. The KV Cache Manager uses the PagedAttention memory layout to allocate fixed-size cache blocks on demand and maintains a Free Block Queue on the CPU that tracks which blocks in the GPU’s Paged KV Cache are currently free. When a request needs additional KV cache space, the KV Cache manager takes a free block from the queue and assigns it to that request, thus avoiding an expensive search through GPU memory for available cache blocks. All of these components form the core of vLLM’s inference engine. The Scheduler determines what requests are executed, the Model Executor determines how those requests are executed, the KV Cache Manager determines where each request’s KV cache lives using the PagedAttention Memory Layout. This architecture enables vLLM to serve thousands of concurrent requests with high throughput, low latency, and efficient GPU memory utilization. Heres a little animation that visualizes everything! - I've also completed the forward pass for my mnist.c project. I had a nice chat with shrey birmiwal, such a knowledgeable guy. Excited to learn more about vLLM and implement a tiny-vLLM one day.

max fu

70,797 просмотров • 1 месяц назад

Every man lives two lives. The second begins when he realises that he can max out hypertrophy in 15 second sets. Four or five reps build muscle. The last four or five, where the bar slows on its own whether you like it or not. That is where the high-threshold motor units finally get called up. Where the cross-bridges are attached in maximum number at once. Where the fibre takes the tension it has been waiting all set for. Mechanical tension is the only language the muscle reads. It does not have a second one. Everything either side of that is filler, and somebody is paid to sell you filler. Tempo is filler. You are 30 to 50 per cent stronger lowering a weight than lifting it, so no descent on earth is slow enough to threaten you. Drag it out and all you have done is put a lighter weight on the half that counted. The pump is filler. Lactate infused straight into the blood grows nothing. Blood flow restricted on a resting muscle grows nothing. Swelling is a feeling and it gets no vote. The mind-muscle connection is filler. You cannot instruct a muscle in which fibres to use. You tell it to contract. The load decides the rest. So: a weight where the fourth rep slows by itself. Drive it. Stop one short. Rack it. Fifteen seconds. That set has already delivered everything your three sets of twelve spent forty minutes promising. Nobody has ever built a business on fifteen seconds of hard work, so they built one on everything you could bolt onto it.
0:16

Every man lives two lives. The second begins when he realises that he can max out hypertrophy in 15 second sets. Four or five reps build muscle. The last four or five, where the bar slows on its own whether you like it or not. That is where the high-threshold motor units finally get called up. Where the cross-bridges are attached in maximum number at once. Where the fibre takes the tension it has been waiting all set for. Mechanical tension is the only language the muscle reads. It does not have a second one. Everything either side of that is filler, and somebody is paid to sell you filler. Tempo is filler. You are 30 to 50 per cent stronger lowering a weight than lifting it, so no descent on earth is slow enough to threaten you. Drag it out and all you have done is put a lighter weight on the half that counted. The pump is filler. Lactate infused straight into the blood grows nothing. Blood flow restricted on a resting muscle grows nothing. Swelling is a feeling and it gets no vote. The mind-muscle connection is filler. You cannot instruct a muscle in which fibres to use. You tell it to contract. The load decides the rest. So: a weight where the fourth rep slows by itself. Drive it. Stop one short. Rack it. Fifteen seconds. That set has already delivered everything your three sets of twelve spent forty minutes promising. Nobody has ever built a business on fifteen seconds of hard work, so they built one on everything you could bolt onto it.

Sama Hoole

17,080 просмотров • 1 месяц назад

The renovation of Belleair CC’s East Course involves moving some seriously mature trees. The process and planning for moving these trees is very thorough. The result- a completely renovated golf course with a seasoned feel to it. Unlike the restoration of our West course, the East is only restoring about a third of Ross’ design. Why not restore it all? It was an impossible task- back in the 1980s our current clubhouse was built over the original driving range. At that time we built a new driving range and lost two par threes and the opening holes of the East. Around that same time the club needed a irrigation pond for the 36 holes, which ate up a good portion of Ross’ East Course design on the other side of the road. The result of that redesign was a course which had 6 subpar golf holes. This renovation will create a better golf course designed to challenge all skill levels. I am very excited to have a better East Course!
0:13

The renovation of Belleair CC’s East Course involves moving some seriously mature trees. The process and planning for moving these trees is very thorough. The result- a completely renovated golf course with a seasoned feel to it. Unlike the restoration of our West course, the East is only restoring about a third of Ross’ design. Why not restore it all? It was an impossible task- back in the 1980s our current clubhouse was built over the original driving range. At that time we built a new driving range and lost two par threes and the opening holes of the East. Around that same time the club needed a irrigation pond for the 36 holes, which ate up a good portion of Ross’ East Course design on the other side of the road. The result of that redesign was a course which had 6 subpar golf holes. This renovation will create a better golf course designed to challenge all skill levels. I am very excited to have a better East Course!

Society of Golf Historians

15,030 просмотров • 4 месяцев назад

Bruh I felt so embarrassed when the guy told the other guy to not come in front of the camera. I specifically kept the camera in a corner so that no one could see it and get awkward. You could see the embarrassment on my face, although it was in a light mood as those guys keep pulling each other's legs at the Gym all the time. But I still made it clear so no one else feels that way because he was so damn loud with “oye camera hai”. You don't own the gym, it's a public gym, so chill.
0:13

Bruh I felt so embarrassed when the guy told the other guy to not come in front of the camera. I specifically kept the camera in a corner so that no one could see it and get awkward. You could see the embarrassment on my face, although it was in a light mood as those guys keep pulling each other's legs at the Gym all the time. But I still made it clear so no one else feels that way because he was so damn loud with “oye camera hai”. You don't own the gym, it's a public gym, so chill.

Aanchal

13,005 просмотров • 2 лет назад

**Traditional Engine Order Telegraphs:** The bridge unit and the engine-room unit are connected by two chains (or wire cables) that run through conduits over sprockets, forming a continuous loop. When the bridge officer moves the handle, it turns a sprocket that pulls the chain, which in turn turns the corresponding sprocket and pointer in the engine room. This classic system does not require electricity; it relies on a direct physical linkage, ensuring that both dials always mirror each other. Here’s a typical sequence of operations: The bridge officer grabs the handle and swings it to the command position, for example, "Half Ahead." This movement not only moves the engine-room pointer but also rings a bell or gong to alert the engineers. The engineers then adjust their own handle to match the position indicated by the bridge officer; this movement serves as an acknowledgment and rings the bell back on the bridge, confirming that the order has been received and understood. Only after this acknowledgment do the engineers work the throttle and reversing gear to carry out the order. It is common practice to first execute a full sweep of the handle, moving it all the way to one extreme and back before settling on the actual command position. This exaggerated motion serves two purposes: it rings the gong loudly and unmistakably, ensuring everyone is aware that a new order is coming, and it checks that the mechanism and chains are not stuck or slack. On some ships, this full sweep also signifies an important or urgent change (such as switching from ahead to astern), emphasizing to the crew that they need to pay attention because the situation is critical. After completing this sweep, the handle is adjusted to the desired position. This telegraph is from the Steamship Shieldhall (video credit as well). Go check her out on
0:10

**Traditional Engine Order Telegraphs:** The bridge unit and the engine-room unit are connected by two chains (or wire cables) that run through conduits over sprockets, forming a continuous loop. When the bridge officer moves the handle, it turns a sprocket that pulls the chain, which in turn turns the corresponding sprocket and pointer in the engine room. This classic system does not require electricity; it relies on a direct physical linkage, ensuring that both dials always mirror each other. Here’s a typical sequence of operations: The bridge officer grabs the handle and swings it to the command position, for example, "Half Ahead." This movement not only moves the engine-room pointer but also rings a bell or gong to alert the engineers. The engineers then adjust their own handle to match the position indicated by the bridge officer; this movement serves as an acknowledgment and rings the bell back on the bridge, confirming that the order has been received and understood. Only after this acknowledgment do the engineers work the throttle and reversing gear to carry out the order. It is common practice to first execute a full sweep of the handle, moving it all the way to one extreme and back before settling on the actual command position. This exaggerated motion serves two purposes: it rings the gong loudly and unmistakably, ensuring everyone is aware that a new order is coming, and it checks that the mechanism and chains are not stuck or slack. On some ships, this full sweep also signifies an important or urgent change (such as switching from ahead to astern), emphasizing to the crew that they need to pay attention because the situation is critical. After completing this sweep, the handle is adjusted to the desired position. This telegraph is from the Steamship Shieldhall (video credit as well). Go check her out on

Bart 🌊⚓️

107,644 просмотров • 1 месяц назад

When the C219 CLS launched in 2004, it invented a body style that every other manufacturer spent the next decade trying to copy. Four doors, a fastback roofline, no B-pillar, and frameless windows, none of which existed together in one car before this. The CLS 500 came with the 5.0L M113 V8, 306 HP and 460 Nm, fitted with two spark plugs per cylinder for a more even burn across the combustion cycle. It was built on the W211 E-Class platform but with completely different proportions and a lower, more aggressive seating position with 4 seats, not 5. That made it feel like a different car entirely. Most buyers chose the diesel because it was cheaper to run. The ones who chose the V8 got the engine the car was always meant to have.
0:18

When the C219 CLS launched in 2004, it invented a body style that every other manufacturer spent the next decade trying to copy. Four doors, a fastback roofline, no B-pillar, and frameless windows, none of which existed together in one car before this. The CLS 500 came with the 5.0L M113 V8, 306 HP and 460 Nm, fitted with two spark plugs per cylinder for a more even burn across the combustion cycle. It was built on the W211 E-Class platform but with completely different proportions and a lower, more aggressive seating position with 4 seats, not 5. That made it feel like a different car entirely. Most buyers chose the diesel because it was cheaper to run. The ones who chose the V8 got the engine the car was always meant to have.

Autowelt

50,175 просмотров • 3 месяцев назад

I’m probably one of the only Teslanaires out there, if not one of the very few, still cutting my own hair. I cut my own hair again today, and it reminded me that becoming a multi-millionaire usually isn’t a random coincidence. People see the $ and think it just happened. What they usually don’t see are the small habits behind it. Of course, I could go spend $25–$50 on a haircut that probably looks better than the one I give myself. But that’s not really what matters to me. I don’t care that much about looking perfect. I care about controlling my time. I care about staying grounded. I care about keeping the kind of habits that helped me build wealth in the first place. And honestly, I enjoy doing it. I’ve been cutting my own hair for so many years that I don’t even think about going to the barber anymore. It’s just normal to me now. It saves time, keeps me frugal, and reminds me that wealth is usually built in the small choices nobody claps for. That’s the part people miss. A lot of people see wealth and assume it was luck. But a lot of the time, it’s really the result of small disciplined habits repeated for years. Not wasting $ just bc you can. Not wasting time just bc other people do. And the funny part is, one day my fleet of Tesla Bots will probably be doing it for me anyway. But until then, I’m good doing it myself. Bc to me, being wealthy was never about trying to look rich. It was about building a mindset. A mindset that values time, discipline, and freedom more than appearances. And once you really live that way, it shows up in a lot of things, even something as simple as cutting your own hair.
0:11

I’m probably one of the only Teslanaires out there, if not one of the very few, still cutting my own hair. I cut my own hair again today, and it reminded me that becoming a multi-millionaire usually isn’t a random coincidence. People see the $ and think it just happened. What they usually don’t see are the small habits behind it. Of course, I could go spend $25–$50 on a haircut that probably looks better than the one I give myself. But that’s not really what matters to me. I don’t care that much about looking perfect. I care about controlling my time. I care about staying grounded. I care about keeping the kind of habits that helped me build wealth in the first place. And honestly, I enjoy doing it. I’ve been cutting my own hair for so many years that I don’t even think about going to the barber anymore. It’s just normal to me now. It saves time, keeps me frugal, and reminds me that wealth is usually built in the small choices nobody claps for. That’s the part people miss. A lot of people see wealth and assume it was luck. But a lot of the time, it’s really the result of small disciplined habits repeated for years. Not wasting $ just bc you can. Not wasting time just bc other people do. And the funny part is, one day my fleet of Tesla Bots will probably be doing it for me anyway. But until then, I’m good doing it myself. Bc to me, being wealthy was never about trying to look rich. It was about building a mindset. A mindset that values time, discipline, and freedom more than appearances. And once you really live that way, it shows up in a lot of things, even something as simple as cutting your own hair.

Teslaconomics

16,514 просмотров • 5 месяцев назад

Andrew’s been to Turkey several times. On our first trip there, Andrew was stopped upon arrival because of a TACA Warrant. I asked the authorities if I could go to airport jail with him, and off we went. That Extradition Warrant is the same one he’s being held on now, in American Jail. Turkey took one look at it and understood that the UK and Romania had an agreement not to extradite Andrew until the Romanian case closed. And off to beautiful Bodrum we went. Every other country he’s traveled to understands that extradition is stayed during the pendency of Romanian Proceedings. America needs to understand the same. Andrew and Tristan have met every release requirement since being given permission to travel. They are not a flight risk. They should not be in jail. Turkey understood this in an afternoon. America has had them far longer and reached the wrong answer. Follow the agreement. Let them out.
0:16

Andrew’s been to Turkey several times. On our first trip there, Andrew was stopped upon arrival because of a TACA Warrant. I asked the authorities if I could go to airport jail with him, and off we went. That Extradition Warrant is the same one he’s being held on now, in American Jail. Turkey took one look at it and understood that the UK and Romania had an agreement not to extradite Andrew until the Romanian case closed. And off to beautiful Bodrum we went. Every other country he’s traveled to understands that extradition is stayed during the pendency of Romanian Proceedings. America needs to understand the same. Andrew and Tristan have met every release requirement since being given permission to travel. They are not a flight risk. They should not be in jail. Turkey understood this in an afternoon. America has had them far longer and reached the wrong answer. Follow the agreement. Let them out.

Joe McBride

171,924 просмотров • 1 месяц назад

i just open sourced the workflow behind $2M AI video productions... i built 7 skills that run the pipeline end to end, built for Seedance 2.5 and they work in Claude Code, Codex, Hermes or any harness (works best with 1080p using Higgsfield CLI) here's how to use them, in order: /setup writes which image and video models you run into your project, once, so every skill reads the same stack /studio-init scaffolds the whole studio as a file tree from one question, the project name /film-breakdown walks your script scene by scene and writes a 22-field card for every shot /reference-board locks your references into a visual bible, a caption on every image and a ban list for the rest /asset-passport writes the exhaustive descriptor every later prompt will quote word for word /stress-test combat-tests each asset and flips it to locked only at 10 out of 10 repeatability /shot-prompt refuses to run until everything in frame is locked, then writes the 15-block prompt and logs every attempt get access to the skills and full breakdown of the pipeline in the article below:
0:12

i just open sourced the workflow behind $2M AI video productions... i built 7 skills that run the pipeline end to end, built for Seedance 2.5 and they work in Claude Code, Codex, Hermes or any harness (works best with 1080p using Higgsfield CLI) here's how to use them, in order: /setup writes which image and video models you run into your project, once, so every skill reads the same stack /studio-init scaffolds the whole studio as a file tree from one question, the project name /film-breakdown walks your script scene by scene and writes a 22-field card for every shot /reference-board locks your references into a visual bible, a caption on every image and a ban list for the rest /asset-passport writes the exhaustive descriptor every later prompt will quote word for word /stress-test combat-tests each asset and flips it to locked only at 10 out of 10 repeatability /shot-prompt refuses to run until everything in frame is locked, then writes the 15-block prompt and logs every attempt get access to the skills and full breakdown of the pipeline in the article below:

Machina

59,905 просмотров • 25 дней назад

DEEPSEEK V4 FLASH AND QWEN3.6 ARE FREE ON AMD'S OWN CLOUD AT $10 OF USAGE A DAY • AMD Token Factory > DeepSeek V4 Flash, Qwen3.6 35B, MiniCPM5 and MiniCPM-V46 at zero cost: > $10 every day, not once -- the counter resets daily. > Everything outside that list runs on Firework AI credits. • SuperGrok, seven days > Grok's paid tier free for a week: > A card is required and it renews on its own, so set the reminder the moment you start. > Availability still depends on your region. AMD built this the way NVIDIA built NIM -> the chip vendors are handing out inference now, because what they are really buying is which silicon you learn on. One of these resets every morning. The other one you only get once ↓
0:12

DEEPSEEK V4 FLASH AND QWEN3.6 ARE FREE ON AMD'S OWN CLOUD AT $10 OF USAGE A DAY • AMD Token Factory > DeepSeek V4 Flash, Qwen3.6 35B, MiniCPM5 and MiniCPM-V46 at zero cost: > $10 every day, not once -- the counter resets daily. > Everything outside that list runs on Firework AI credits. • SuperGrok, seven days > Grok's paid tier free for a week: > A card is required and it renews on its own, so set the reminder the moment you start. > Availability still depends on your region. AMD built this the way NVIDIA built NIM -> the chip vendors are handing out inference now, because what they are really buying is which silicon you learn on. One of these resets every morning. The other one you only get once ↓

slash1s

73,760 просмотров • 1 месяц назад

Talking with someone the other day that estimated they had about 25,000 idle connections to Postgres. My actual response to them: "holy shit". They double checked, it was only about 12,000 Same day had a conversation with someone saying they didn't need pgbouncer because of activerecord's connection pooling. Let's dig into connection pooling in Postgres. Prior to Postgres 14 every connection to the database consumed memory, roughly 10MB, it may be slightly less but it still wasn't free. Even beyond Postgres 14 there is still various contention that happens when Postgres starts to use a connection. An application pooler maintains a set of connections and hands them out when needed on the application side. These are idle and real connections against the database that indeed do impact performance negatively. In contrast pgbouncer speaks the wire protocol, waits for the begin part of the transaction and then uses a connection. It more strictly manages how many idle ones it's having instead of per web server you're running. pgbouncer up until recently really needed to be run in transaction mode (which meant disabling prepared statements in your application framework). prepared_statement support in pgbouncer was added recently, and now you don't have to disable. Even when running with an older version of pgbouncer with prepared_statements disabled you'd still see a big performance gain. A quick check to know if you'd benefit from pgbouncer, run this query: SELECT count(*), state FROM pg_stat_activity GROUP BY 2; If you're idle account is high (yes this is dependent on your view, but to me if it's above 25-30 range, and especially if active is until half that) then you'd already start to benefit from pgbouncer. If it's at 10,000 then post haste get pgbouncer in place. Finally, you don't have to not use a framework pooler, they're fine, but don't think it replaces a native Postgres connection pooler.
0:17

Talking with someone the other day that estimated they had about 25,000 idle connections to Postgres. My actual response to them: "holy shit". They double checked, it was only about 12,000 Same day had a conversation with someone saying they didn't need pgbouncer because of activerecord's connection pooling. Let's dig into connection pooling in Postgres. Prior to Postgres 14 every connection to the database consumed memory, roughly 10MB, it may be slightly less but it still wasn't free. Even beyond Postgres 14 there is still various contention that happens when Postgres starts to use a connection. An application pooler maintains a set of connections and hands them out when needed on the application side. These are idle and real connections against the database that indeed do impact performance negatively. In contrast pgbouncer speaks the wire protocol, waits for the begin part of the transaction and then uses a connection. It more strictly manages how many idle ones it's having instead of per web server you're running. pgbouncer up until recently really needed to be run in transaction mode (which meant disabling prepared statements in your application framework). prepared_statement support in pgbouncer was added recently, and now you don't have to disable. Even when running with an older version of pgbouncer with prepared_statements disabled you'd still see a big performance gain. A quick check to know if you'd benefit from pgbouncer, run this query: SELECT count(*), state FROM pg_stat_activity GROUP BY 2; If you're idle account is high (yes this is dependent on your view, but to me if it's above 25-30 range, and especially if active is until half that) then you'd already start to benefit from pgbouncer. If it's at 10,000 then post haste get pgbouncer in place. Finally, you don't have to not use a framework pooler, they're fine, but don't think it replaces a native Postgres connection pooler.

Craig Kerstiens

12,411 просмотров • 1 год назад

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.
0:16

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.

elvis

11,303 просмотров • 22 дней назад

It is important that the Mark Rutte is with us in Ukraine at such a brutal moment of this war, when the Russians have once again disregarded the efforts of the American side. Today, Russia carried out a record strike in terms of the use of ballistic missiles. There were 28 cruise missiles, as well as 43 missiles of various types that approach their targets along a ballistic trajectory and can be intercepted only by Patriot systems. This means that missiles for these systems are needed and that deliveries must be prompt. I discussed this with Mark today, and I hope we will be able to implement everything we agreed on. Thank you, Mark, for your support.
0:19

It is important that the Mark Rutte is with us in Ukraine at such a brutal moment of this war, when the Russians have once again disregarded the efforts of the American side. Today, Russia carried out a record strike in terms of the use of ballistic missiles. There were 28 cruise missiles, as well as 43 missiles of various types that approach their targets along a ballistic trajectory and can be intercepted only by Patriot systems. This means that missiles for these systems are needed and that deliveries must be prompt. I discussed this with Mark today, and I hope we will be able to implement everything we agreed on. Thank you, Mark, for your support.

Volodymyr Zelenskyy / Володимир Зеленський

177,758 просмотров • 7 месяцев назад

Robinson Ortiz...Atta Baby! Ortiz had a HUGE year this past season, and got rewarded by being placed on the Dodgers' 40-man roster. Ortiz posted an ERA of 2.73, an average against of just .207, and had 72 Ks in 59.1 innings. And ALL of that is great. And, while the "execution" piece is still THE focus, keep in mind, he, in essence, hadn't pitched since 2021, due to Tommy John. Ortiz was a HIGHLY thought of prospect back in 2021, before his Tommy John, and came back to start 2024, but was shut down after just 6 outings and 11 innings in May of 2024. So, for him to be able to post 59.1 innings and have 48 appearances was HUGE in terms of showing that he's BACK. Then, to have the success on top of that, after such a long layoff, just goes to show how good his stuff is. Ortiz features a HUGE sweeping slider that starts well behind the back of a left-hander, and breaks from one side of the earth to the other. Trying to decipher whether that pitch is going to land "in the zone" or not is VERY difficult, even for hitters that have a LOT of MLB experience like he faced at OKC. His fastball is firm, and he can hit 6s and 7s, so those 2 pitches play well off of each other. Welcome aboard, Robinson. It's been a LONG road, one you've navigated successfully. Keep killin' it, my man. #dodgers
0:07

Robinson Ortiz...Atta Baby! Ortiz had a HUGE year this past season, and got rewarded by being placed on the Dodgers' 40-man roster. Ortiz posted an ERA of 2.73, an average against of just .207, and had 72 Ks in 59.1 innings. And ALL of that is great. And, while the "execution" piece is still THE focus, keep in mind, he, in essence, hadn't pitched since 2021, due to Tommy John. Ortiz was a HIGHLY thought of prospect back in 2021, before his Tommy John, and came back to start 2024, but was shut down after just 6 outings and 11 innings in May of 2024. So, for him to be able to post 59.1 innings and have 48 appearances was HUGE in terms of showing that he's BACK. Then, to have the success on top of that, after such a long layoff, just goes to show how good his stuff is. Ortiz features a HUGE sweeping slider that starts well behind the back of a left-hander, and breaks from one side of the earth to the other. Trying to decipher whether that pitch is going to land "in the zone" or not is VERY difficult, even for hitters that have a LOT of MLB experience like he faced at OKC. His fastball is firm, and he can hit 6s and 7s, so those 2 pitches play well off of each other. Welcome aboard, Robinson. It's been a LONG road, one you've navigated successfully. Keep killin' it, my man. #dodgers

Dodgers Daily

17,525 просмотров • 10 месяцев назад

For a long time, staking usually meant one thing: Lock your tokens and wait 🤷‍♂️ But some newer models are trying to connect staking with actual network activity. Wanchain 's xWAN system is an interesting example of that 👇 👉 Convert WAN into xWAN 👉 Stake xWAN 👉 Become part of the bridge ecosystem What caught my attention is that the idea isn't only about holding tokens. The bridge is being used every day as assets move between different chains, and staking is tied to that broader activity. As more users move funds across networks, infrastructure becomes increasingly important 🔥 Because today's crypto user rarely stays in one place: 👉 A transaction starts on one chain 👉 Continues on another 👉 Ends somewhere completely different Cross-chain movement is slowly becoming a normal part of crypto. And when that happens, the infrastructure behind those transfers matters more than ever. It's interesting to see staking evolving from a passive activity into something more connected to real network usage. Do you think staking models tied to actual ecosystem activity are the future? 🤔 👉
0:10

For a long time, staking usually meant one thing: Lock your tokens and wait 🤷‍♂️ But some newer models are trying to connect staking with actual network activity. Wanchain 's xWAN system is an interesting example of that 👇 👉 Convert WAN into xWAN 👉 Stake xWAN 👉 Become part of the bridge ecosystem What caught my attention is that the idea isn't only about holding tokens. The bridge is being used every day as assets move between different chains, and staking is tied to that broader activity. As more users move funds across networks, infrastructure becomes increasingly important 🔥 Because today's crypto user rarely stays in one place: 👉 A transaction starts on one chain 👉 Continues on another 👉 Ends somewhere completely different Cross-chain movement is slowly becoming a normal part of crypto. And when that happens, the infrastructure behind those transfers matters more than ever. It's interesting to see staking evolving from a passive activity into something more connected to real network usage. Do you think staking models tied to actual ecosystem activity are the future? 🤔 👉

Han.eth🌿☀️

14,751 просмотров • 1 месяц назад