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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Got flash banged by OpenCode recently? Yeah, that was me. Here's what happened: OpenCode/OpenTUI detects terminal theme mode (light or dark) by querying OSC 10/11 for the terminal’s foreground/background colors and deriving the mode from those values. OpenTUI also enables DEC Private Mode 2031 to receive theme-change notifications. When... that mode is enabled, terminals can send CSI 997 when the system theme changes. OpenTUI treated the 997 payload as authoritative and let it override the OSC 10/11-derived result. That turned out to be wrong. In some terminals, the 997 payload is simply unreliable: it can report light while the queried terminal colors clearly indicate a dark theme. That’s what caused the flash bangs. The fix seemed straightforward: stop trusting the 997 payload as the actual theme mode and use it only as a trigger to re-query OSC 10/11, then derive the mode from the returned foreground/background colors. That works great. Except OpenTUI had also started using OSC 11 to set the terminal’s default background color, so the terminal gutter around the drawn TUI matched the app background instead of the terminal’s own default background. This was introduced recently in OpenTUI. That created a new problem: if you use OSC 11 to override the terminal background, then later query OSC 11, you are just reading back your own override instead of the terminal’s real theme background. No problem. Reset the terminal background with OSC 111, query OSC 10/11, derive the mode, then restore the renderer background again. Oh wait. Turns out Ghostty has a bug. Once this background reset/override path is used, later OSC 11 background reporting can get stuck and stop tracking system theme changes correctly. Even though theme-change notifications still fire and OSC 10 foreground updates continue. This would cause further issues where the OSC 10/11 derivation would be wrong again. So for now: no using OSC 11 to set the terminal background color just to fill the gutter. TL;DR: OpenTUI must treat CSI 997 only as a hint that the terminal theme may have changed and rely exclusively on OSC 10/11 color queries for actual theme mode detection, while avoiding terminal background mutation via OSC 11/111 because that breaks correctness in some terminals like Ghostty.show more

kmdr

6,988 subscribers

30,311 просмотров • 4 месяцев назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

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

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

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

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

Ghostty now has light/dark-mode specific themes and reacts live to your system theme changing. The titlebar also now matches the background color of the focused terminal, including runtime palette changes (i.e. OSC 11). See the video for examples (sound explains). The titlebar one is another example of one of those "details matter" features. We only modify the titlebar color if the focused terminal borders the top of the window. If its a a split that is nested below the top border, we match the previously focused terminal that touched the top border.

Ghostty now has light/dark-mode specific themes and reacts live to your system theme changing. The titlebar also now matches the background color of the focused terminal, including runtime palette changes (i.e. OSC 11). See the video for examples (sound explains). The titlebar one is another example of one of those "details matter" features. We only modify the titlebar color if the focused terminal borders the top of the window. If its a a split that is nested below the top border, we match the previously focused terminal that touched the top border.

Mitchell Hashimoto

77,229 просмотров • 1 год назад

Dark mode prevents myopia (nearsightedness). Dr. Alexander Wunsch, German physician studying the effects of light on health for 30+ years: "Whenever the opportunity arises to read text white on black, we should do so." Here's the mechanism: Your retina has two cell systems — ON cells and OFF cells. Black letters on white background activate the OFF cell system. Chronic activation of the OFF cell system promotes the development of myopia. Dark mode — white text on black background — activates the ON cell system instead. This is the preventive mechanism. There is also a significant difference in total light load: > Standard display (white background, black text): 95% of screen light is emitted to display the page. Only 5% is the actual text. > Dark mode (black background, white text): only 5% of total light is needed to convey the same information. Less light from the screen. The correct cell system is activated. Lower myopia risk. The first computer screens were dark mode by default — black background, green or amber text. That was optimal. The shift to white backgrounds was aesthetic, not biological. University of Tübingen, 2018 — researchers developed a mathematical model analyzing image content for myopia risk potential. Their finding? Natural outdoor scenes have a neutral effect on the eye. Conventional text on white background promotes myopia development. Dark mode presentation does not. They then tested this in subjects. Black letters on white background produced measurable changes in the eye that promote myopia. In Europe, half of all students are already nearsighted. Myopia is the most common visual impairment among young people. The more a child reads — the higher the risk. The mechanisms are not yet fully understood in all details. But the consequences are clear. Wunsch: "Dark mode is recommended wherever it does not impair the workflow during screen work." "In the evening and at night, this should be the mandatory setting in order to keep the disruption of the internal clock and the possible damage to the retina as low as possible." Wunsch's advice to parents: "If children discover the joy of reading and develop into bookworms, it is certainly a good investment to provide them with an e-book reader that enables text display on a dark background." The original screen setting was black background. We changed it for aesthetics. The biology didn't change with it.

Dark mode prevents myopia (nearsightedness). Dr. Alexander Wunsch, German physician studying the effects of light on health for 30+ years: "Whenever the opportunity arises to read text white on black, we should do so." Here's the mechanism: Your retina has two cell systems — ON cells and OFF cells. Black letters on white background activate the OFF cell system. Chronic activation of the OFF cell system promotes the development of myopia. Dark mode — white text on black background — activates the ON cell system instead. This is the preventive mechanism. There is also a significant difference in total light load: > Standard display (white background, black text): 95% of screen light is emitted to display the page. Only 5% is the actual text. > Dark mode (black background, white text): only 5% of total light is needed to convey the same information. Less light from the screen. The correct cell system is activated. Lower myopia risk. The first computer screens were dark mode by default — black background, green or amber text. That was optimal. The shift to white backgrounds was aesthetic, not biological. University of Tübingen, 2018 — researchers developed a mathematical model analyzing image content for myopia risk potential. Their finding? Natural outdoor scenes have a neutral effect on the eye. Conventional text on white background promotes myopia development. Dark mode presentation does not. They then tested this in subjects. Black letters on white background produced measurable changes in the eye that promote myopia. In Europe, half of all students are already nearsighted. Myopia is the most common visual impairment among young people. The more a child reads — the higher the risk. The mechanisms are not yet fully understood in all details. But the consequences are clear. Wunsch: "Dark mode is recommended wherever it does not impair the workflow during screen work." "In the evening and at night, this should be the mandatory setting in order to keep the disruption of the internal clock and the possible damage to the retina as low as possible." Wunsch's advice to parents: "If children discover the joy of reading and develop into bookworms, it is certainly a good investment to provide them with an e-book reader that enables text display on a dark background." The original screen setting was black background. We changed it for aesthetics. The biology didn't change with it.

no.mind

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

CSS Tip! ⭐️ You can use the lh (line-height) unit on background layers to emphasize multiple lines of text responsively without extra elements! ⚡️ h1 { background: linear-gradient(white, white), grey; background-size: 100% calc(var(--lines) * 1lh), 100% 100%; background-clip: text; color: transparent; } Here you emphasize the first two lines of the heading with white using a sized background-image layer It has a size of 2lh ✨ Then the rest of the element is colored with whatever other colors you want to use as layers. If you watch the video, you can see different colors used for different lines and then fade it out if you wish. You could do whatever you like with it 😎 Neat part is that it's responsive. The font-size is set with a clamp and you can resize the viewport or the element and the number of lines emphasized will remain 🤙 Last but not least, make sure to use background-clip: text and color: transparent so the background shines through 🔥 Also, note that if you're only looking to highlight the first line, you can still use the :first-line pseudo 🫶 Have a play with it and see what you can come up with! CodePen.IO link below! 👇

CSS Tip! ⭐️ You can use the lh (line-height) unit on background layers to emphasize multiple lines of text responsively without extra elements! ⚡️ h1 { background: linear-gradient(white, white), grey; background-size: 100% calc(var(--lines) * 1lh), 100% 100%; background-clip: text; color: transparent; } Here you emphasize the first two lines of the heading with white using a sized background-image layer It has a size of 2lh ✨ Then the rest of the element is colored with whatever other colors you want to use as layers. If you watch the video, you can see different colors used for different lines and then fade it out if you wish. You could do whatever you like with it 😎 Neat part is that it's responsive. The font-size is set with a clamp and you can resize the viewport or the element and the number of lines emphasized will remain 🤙 Last but not least, make sure to use background-clip: text and color: transparent so the background shines through 🔥 Also, note that if you're only looking to highlight the first line, you can still use the :first-line pseudo 🫶 Have a play with it and see what you can come up with! CodePen.IO link below! 👇

jhey ʕ•ᴥ•ʔ

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

CSS Trick 📜 You can trigger text highlights on scroll with scroll-driven animations 😎 mark { animation: highlight; animation-timeline: view(); } @keyframes highlight { to { --lit: 1; }} mark span { background-position: calc(var(--lit) * -110%) 0; transition: background 1s; } The trick is using a scroll-driven animation to flip a custom property on a element 🎚️ You flip the value between 0 and 1, and that transitions the background position of the element mark { --lit: 0; animation: highlight steps(1) both; animation-timeline: view(); animation-range: entry 100% cover 10%; } The background has to be applied on a child of the mark to see the change in the custom property 👀 mark span { background: linear-gradient( 120deg, yellow 50%, transparent 50%) 110% 0 / 220% 100% no-repeat; background-position: calc(var(--lit) * 110%) 0; transition: background-position 1s; } The trick is to set the background-size so that it's bigger than the element and then split the background-color in the middle using a linear-gradient 🤙 And the property flips fills in the color 🫶 That's it! If there isn't support for scroll-driven animations, use JavaScript's IntersectionObserver API. The code for this is in the demo 😎 Cool example of using CSS as an IntersectionObserver! CodePen.IO link below 👇

CSS Trick 📜 You can trigger text highlights on scroll with scroll-driven animations 😎 mark { animation: highlight; animation-timeline: view(); } @keyframes highlight { to { --lit: 1; }} mark span { background-position: calc(var(--lit) * -110%) 0; transition: background 1s; } The trick is using a scroll-driven animation to flip a custom property on a element 🎚️ You flip the value between 0 and 1, and that transitions the background position of the element mark { --lit: 0; animation: highlight steps(1) both; animation-timeline: view(); animation-range: entry 100% cover 10%; } The background has to be applied on a child of the mark to see the change in the custom property 👀 mark span { background: linear-gradient( 120deg, yellow 50%, transparent 50%) 110% 0 / 220% 100% no-repeat; background-position: calc(var(--lit) * 110%) 0; transition: background-position 1s; } The trick is to set the background-size so that it's bigger than the element and then split the background-color in the middle using a linear-gradient 🤙 And the property flips fills in the color 🫶 That's it! If there isn't support for scroll-driven animations, use JavaScript's IntersectionObserver API. The code for this is in the demo 😎 Cool example of using CSS as an IntersectionObserver! CodePen.IO link below 👇

jhey ʕ•ᴥ•ʔ

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

Quick demo of Zero’s new background queries. Zero’s sync is query-based. Rather than specifying what data you want using rules or some other separate system, you just use queries. Right inside the client app, you do a query using a full sql-style language. You get filters, subqueries , limits, etc. Zero syncs the data backing these queries to the client. It’s important to realize Zero isn’t really a cache. It’s a replica. It’s eagerly replicating a precise snapshot of a slice of your database - the slice covered by the queries you have open. So there is never stale data in Zero. When you close a query we delete the rows uniquely returned by that query because we can no longer keep them up to date. Of course that kind of sucks for the common case of doing a query, navigating, then pressing “back”. Ideally we want that back nav to be fast. To address this Zero 0.17 adds background queries. You can add a ttl to a query and it will keep running and syncing in the background. This is much different than normal caching because this data stays up to date. If you make the same query again, the results will be *instantly* available *and already up to date with server*. If you make a different query the data from the background query is used client-side to answer the new query instantly if possible. This all happens completely automatically. Just by adding the ttl flag.

Quick demo of Zero’s new background queries. Zero’s sync is query-based. Rather than specifying what data you want using rules or some other separate system, you just use queries. Right inside the client app, you do a query using a full sql-style language. You get filters, subqueries , limits, etc. Zero syncs the data backing these queries to the client. It’s important to realize Zero isn’t really a cache. It’s a replica. It’s eagerly replicating a precise snapshot of a slice of your database - the slice covered by the queries you have open. So there is never stale data in Zero. When you close a query we delete the rows uniquely returned by that query because we can no longer keep them up to date. Of course that kind of sucks for the common case of doing a query, navigating, then pressing “back”. Ideally we want that back nav to be fast. To address this Zero 0.17 adds background queries. You can add a ttl to a query and it will keep running and syncing in the background. This is much different than normal caching because this data stays up to date. If you make the same query again, the results will be instantly available and already up to date with server. If you make a different query the data from the background query is used client-side to answer the new query instantly if possible. This all happens completely automatically. Just by adding the ttl flag.

Aaron Boodman

18,808 просмотров • 1 год назад

CSS Tip! ✨ You can lean into form control state and layered backgrounds to create input status strokes 😎 input:valid { --valid: 1; } input { background: var(--bg) padding-box, ..., var(--valid-bg) calc((1 - var(--valid)) * 100cqi) 0 / 100% 100% border-box; } The trick is to layer up backgrounds using background-clip to leave a border space 🤏 Applying a transparent border gives you the space for the layered background to transition in 🎞️ Then you can use custom properties to dictate the background-position of each layer. By default, the valid and invalid layers are positioned outside the bounding box. But when one of those states is active, the background layer transitions in to 0 0. To respect people's animations preferences, we can wrap that transition in a media query 🤙 @media (prefers-reduced-motion: no-preference) { input { transition: background-position: 0.5s; } } Was revisiting techniques around :has and :user-valid and it dawned that you could do it like this too! Hope you find it useful! p.s Don't rely on color to communicate form status. It's a cool trick though for an added touch ✨ CodePen.IO link below! 👇

CSS Tip! ✨ You can lean into form control state and layered backgrounds to create input status strokes 😎 input:valid { --valid: 1; } input { background: var(--bg) padding-box, ..., var(--valid-bg) calc((1 - var(--valid)) * 100cqi) 0 / 100% 100% border-box; } The trick is to layer up backgrounds using background-clip to leave a border space 🤏 Applying a transparent border gives you the space for the layered background to transition in 🎞️ Then you can use custom properties to dictate the background-position of each layer. By default, the valid and invalid layers are positioned outside the bounding box. But when one of those states is active, the background layer transitions in to 0 0. To respect people's animations preferences, we can wrap that transition in a media query 🤙 @media (prefers-reduced-motion: no-preference) { input { transition: background-position: 0.5s; } } Was revisiting techniques around :has and :user-valid and it dawned that you could do it like this too! Hope you find it useful! p.s Don't rely on color to communicate form status. It's a cool trick though for an added touch ✨ CodePen.IO link below! 👇

jhey ʕ•ᴥ•ʔ

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

CSS Trick! ⚡️ You can use scroll-driven animation with background-attachment to create a dynamic glowing card scroller without JS 🔥 section { animation:vibe; animation-timeline:--list; } @keyframes vibe { to{--hue:320;}} .glow {background: hsl(var(--hue) 80% 50%);} Here's how! 🤙 You can use the background-attachment trick used in other glow card demos 😎 article { background-attachment: fixed; } The difference here is that you aren't going to update the fixed background position with your pointer this time. It can remain fixed. The magic part is that as you scroll, the background will leave the card that's leaving and enter the card that's entering ✨ For the extra background glow, you can use a fixed pseudo element on the list container itself 💪 Once that's in place, you're only task is to change the color of the background as you scroll 🤔 Create a custom property declaration for the --hue @property --base { inherits: true; syntax: ' '; initial-value: 0; } Then create an animation that updates this value @keyframes accent { to { --hue: 320; }} The last piece is hooking it up to scroll and there is a little trick in here 👀 First, you need an inline scroll-timeline on the list ul { scroll-timeline: --list inline; } Then you can use timeline-scope to hoist that scroll-timeline up so a parent can use it. You then animate the custom property on this element and let the value cascade down to the places that need it 🔥 section { timeline-scope: --list; animation: accent both linear; animation-timeline: --list; } For example, the glow uses the --hue this way [data-glow] { background-image: radial-gradient( 150px 150px at 50% 50%, hsl(var(--hue) 100% 70% / 0.25), transparent ); } Lastly, scroll-snap is optional of course but plays nice with the scroll-driven animation demos ✨ The key for that is ul { scroll-snap-type: x mandatory; } li { scroll-snap-align: center; } That's it! Pretty fun trick to play with! 🤓 Any questions, let me know! Should we add it to the video walkthrough list? CodePen.IO link below! 👇

CSS Trick! ⚡️ You can use scroll-driven animation with background-attachment to create a dynamic glowing card scroller without JS 🔥 section { animation:vibe; animation-timeline:--list; } @keyframes vibe { to{--hue:320;}} .glow {background: hsl(var(--hue) 80% 50%);} Here's how! 🤙 You can use the background-attachment trick used in other glow card demos 😎 article { background-attachment: fixed; } The difference here is that you aren't going to update the fixed background position with your pointer this time. It can remain fixed. The magic part is that as you scroll, the background will leave the card that's leaving and enter the card that's entering ✨ For the extra background glow, you can use a fixed pseudo element on the list container itself 💪 Once that's in place, you're only task is to change the color of the background as you scroll 🤔 Create a custom property declaration for the --hue @property --base { inherits: true; syntax: ' '; initial-value: 0; } Then create an animation that updates this value @keyframes accent { to { --hue: 320; }} The last piece is hooking it up to scroll and there is a little trick in here 👀 First, you need an inline scroll-timeline on the list ul { scroll-timeline: --list inline; } Then you can use timeline-scope to hoist that scroll-timeline up so a parent can use it. You then animate the custom property on this element and let the value cascade down to the places that need it 🔥 section { timeline-scope: --list; animation: accent both linear; animation-timeline: --list; } For example, the glow uses the --hue this way [data-glow] { background-image: radial-gradient( 150px 150px at 50% 50%, hsl(var(--hue) 100% 70% / 0.25), transparent ); } Lastly, scroll-snap is optional of course but plays nice with the scroll-driven animation demos ✨ The key for that is ul { scroll-snap-type: x mandatory; } li { scroll-snap-align: center; } That's it! Pretty fun trick to play with! 🤓 Any questions, let me know! Should we add it to the video walkthrough list? CodePen.IO link below! 👇

jhey ʕ•ᴥ•ʔ

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

** Parodius Update ** The team - Pyron , Vector Orbitex and I have all been flatout busy .. still we have had time to do some wee bits on Parodius for Sega Genesis. Since last update : More colors !! the background now uses Interupt trickery to have 19 colors so far (from 16) . Just got it working today as the lazer interupts colliding with the color change interupts had to be sorted out. So there are more 3 more blues shades in the background. You can see index 0 and index 11 in the CRAM viewer re-using color indexes on the RHS as the screen draws. Theres about 9 interupts driving lazers and background updates now, the cpu sorting / setup is costing about 8 %cpu but I'll live with it for now. Stage 1 track reworked by Vector, reduced vgm size to 101 KB ! ( xgm2 further reduces this to 53kb ) And it also includes the choirs, recreated in FM and PSG sound. He promises further enhancements to come too. Vic Viper Shot and Lazer SFX added , Speed-Up , Lazer Announcer speed samples added . I'm very happy with how the voices turned out in particular , Pyron has supplied modified samples to get better volume levels. Background collisions for the standard shot implemented , next I'll do the lazer . More of the vic viper power ups and Power up bar hud / animating water to add yet. #SGDK #Parodius #SegaMegadrive #SegaGenesis

Parodius Update The team - Pyron , Vector Orbitex and I have all been flatout busy .. still we have had time to do some wee bits on Parodius for Sega Genesis. Since last update : More colors !! the background now uses Interupt trickery to have 19 colors so far (from 16) . Just got it working today as the lazer interupts colliding with the color change interupts had to be sorted out. So there are more 3 more blues shades in the background. You can see index 0 and index 11 in the CRAM viewer re-using color indexes on the RHS as the screen draws. Theres about 9 interupts driving lazers and background updates now, the cpu sorting / setup is costing about 8 %cpu but I'll live with it for now. Stage 1 track reworked by Vector, reduced vgm size to 101 KB ! ( xgm2 further reduces this to 53kb ) And it also includes the choirs, recreated in FM and PSG sound. He promises further enhancements to come too. Vic Viper Shot and Lazer SFX added , Speed-Up , Lazer Announcer speed samples added . I'm very happy with how the voices turned out in particular , Pyron has supplied modified samples to get better volume levels. Background collisions for the standard shot implemented , next I'll do the lazer . More of the vic viper power ups and Power up bar hud / animating water to add yet. #SGDK #Parodius #SegaMegadrive #SegaGenesis

Shannon Birt

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

how beginners build WEBSITES vs higgsfield ai plugin... most people treat ai website builders as faster templates. you pick a theme, swap the copy, change the background image, and ship something someone else designed. the fable 5/claude build works differently because of what's connected to it. the higgsfield mcp gives claude direct access to nano banana pro and seedance 2.0 during the build. it generates the stills and the video clips itself, in the same session, and drops them straight into the page without downloading assets and reuploading them somewhere else. having that access changes the order it works in. it produces the images first and writes the code after, because scroll frames get sliced out of visuals that already exist. it figured out that dependency before it started. the wix tutorial is a beginner level of exactly that. where to click, how to add a section, how to change a background, how to hide an element on mobile. halfway through, it tells you to avoid customizing too much because the design will break. every color in that template was picked to sit next to every other color, so your own taste is a liability inside it. you're editing someone's existing template. changing an asset after the build is one prompt. the mcp regenerates it, the code updates around it, nothing else in the page moves. inside a template that same change means rebuilding the section.

how beginners build WEBSITES vs higgsfield ai plugin... most people treat ai website builders as faster templates. you pick a theme, swap the copy, change the background image, and ship something someone else designed. the fable 5/claude build works differently because of what's connected to it. the higgsfield mcp gives claude direct access to nano banana pro and seedance 2.0 during the build. it generates the stills and the video clips itself, in the same session, and drops them straight into the page without downloading assets and reuploading them somewhere else. having that access changes the order it works in. it produces the images first and writes the code after, because scroll frames get sliced out of visuals that already exist. it figured out that dependency before it started. the wix tutorial is a beginner level of exactly that. where to click, how to add a section, how to change a background, how to hide an element on mobile. halfway through, it tells you to avoid customizing too much because the design will break. every color in that template was picked to sit next to every other color, so your own taste is a liability inside it. you're editing someone's existing template. changing an asset after the build is one prompt. the mcp regenerates it, the code updates around it, nothing else in the page moves. inside a template that same change means rebuilding the section.

Sulfur

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

long time no posting, here's some of the stuff we released in helium recently: - customizable keyboard shortcuts on all platforms - automatic updates on windows - frameless mode (previously zen mode), with floating sidebar, is now out of beta and included in settings by default - improved fingerprint noising: fixed the canvas noising algorithm and added protections against analysis attacks (thank you Cynthia 🐈 for your report, research, and assistance) - tab URL copying, one or multiple, formatted as a list with line breaks - manual tab hibernation, with an option to hibernate all tabs except for selected/active ones - an option to close tabs to the left (or above, in vertical layout) - redesigned toast notifications, now anchored to the active web page, and no longer blinding in dark mode - toast notification about newly opened background tabs in frameless mode (can be disabled in settings) - redesigned the infobar, it no longer looks out of place - improved QR code generation, now it's actually useful - downloads bubble is now shown instead of the full page whenever applicable - kagi search now supports reverse image search from image context menu - frameless mode animations are now smoother - better color contrast in light and dark modes - a lot of bug fixes and other minor improvements all of these changes are present in the latest version of helium. if you're using helium on windows, please update to the latest version, so your browser can be updated automatically from now on!

long time no posting, here's some of the stuff we released in helium recently: - customizable keyboard shortcuts on all platforms - automatic updates on windows - frameless mode (previously zen mode), with floating sidebar, is now out of beta and included in settings by default - improved fingerprint noising: fixed the canvas noising algorithm and added protections against analysis attacks (thank you Cynthia 🐈 for your report, research, and assistance) - tab URL copying, one or multiple, formatted as a list with line breaks - manual tab hibernation, with an option to hibernate all tabs except for selected/active ones - an option to close tabs to the left (or above, in vertical layout) - redesigned toast notifications, now anchored to the active web page, and no longer blinding in dark mode - toast notification about newly opened background tabs in frameless mode (can be disabled in settings) - redesigned the infobar, it no longer looks out of place - improved QR code generation, now it's actually useful - downloads bubble is now shown instead of the full page whenever applicable - kagi search now supports reverse image search from image context menu - frameless mode animations are now smoother - better color contrast in light and dark modes - a lot of bug fixes and other minor improvements all of these changes are present in the latest version of helium. if you're using helium on windows, please update to the latest version, so your browser can be updated automatically from now on!

Helium

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

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

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

** Sega Genesis 3D engine update 8.5 ** A smaller update - Scrolling left or right of the sprite based background is implemented along with X camera shifting of the 3d plane. The Exodus emulator has been used with sprite boxing enabled so you can see the background sprites making up the object ( their outlines ) and how they move to tilt the image . The background is made up of 112 sprites (51 are multiplexed in that number as the Genesis is limited to 80 without mulitplexing eg basically re-using sprite hardware as the screen is being drawn ) . In a 6 x 17 sprite grid of 16x32 pixel high sprites. If the tilt affect was not neccessary or only 1/2 the angle of tilt effect was needed, I could get away with 1/2 the number of sprites and just used 32x32 sprites instead. I think the tilt effect adds a bit to movement however. This is very similar to how a Neo Geo would build its backgrounds up - in 16 pixel strips however its sprites are tall as the screen or more but the concept of making backgrounds up in 16 pixel wide strips is similar. The NG uses sprites to build any background layers required. Here on the Genesis the reason is rendering is much faster using both the 3d planes and using a total sprite background for this engine. Initially i had a lot of things breaking when I tried to move the camera in the X dimension much , as i'd optimised the vertex transform path heavily and once beyond a certain camera offset the X value was wrapping around causing a lot of breakage in the rendering. Thankfully solved that issue without marginal impact to cpu . It still needs work , perspectives are a bit wrong etc but it won't be hard to fix. Also found some rendering speeds ups, about 8% by optimising fully onscreen quads and optimising the clearing of the frame buffers more efficiently. Toni Gálvez - Megastyle - BG. has been hard at work on HUD elements and more 3d models so will have something to show for that soon. #SGDK #SegaMegadrive #SegaGenesis

Sega Genesis 3D engine update 8.5 A smaller update - Scrolling left or right of the sprite based background is implemented along with X camera shifting of the 3d plane. The Exodus emulator has been used with sprite boxing enabled so you can see the background sprites making up the object ( their outlines ) and how they move to tilt the image . The background is made up of 112 sprites (51 are multiplexed in that number as the Genesis is limited to 80 without mulitplexing eg basically re-using sprite hardware as the screen is being drawn ) . In a 6 x 17 sprite grid of 16x32 pixel high sprites. If the tilt affect was not neccessary or only 1/2 the angle of tilt effect was needed, I could get away with 1/2 the number of sprites and just used 32x32 sprites instead. I think the tilt effect adds a bit to movement however. This is very similar to how a Neo Geo would build its backgrounds up - in 16 pixel strips however its sprites are tall as the screen or more but the concept of making backgrounds up in 16 pixel wide strips is similar. The NG uses sprites to build any background layers required. Here on the Genesis the reason is rendering is much faster using both the 3d planes and using a total sprite background for this engine. Initially i had a lot of things breaking when I tried to move the camera in the X dimension much , as i'd optimised the vertex transform path heavily and once beyond a certain camera offset the X value was wrapping around causing a lot of breakage in the rendering. Thankfully solved that issue without marginal impact to cpu . It still needs work , perspectives are a bit wrong etc but it won't be hard to fix. Also found some rendering speeds ups, about 8% by optimising fully onscreen quads and optimising the clearing of the frame buffers more efficiently. Toni Gálvez - Megastyle - BG. has been hard at work on HUD elements and more 3d models so will have something to show for that soon. #SGDK #SegaMegadrive #SegaGenesis

Shannon Birt

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

I've built an AI agent that generates a logline of its choosing, creates text-to-video clips via 'scenes' it prompts with Luma, and then stitches them together automatically—even adding background music if you happen to have some present! At first, I let the model run wild—no direction, just "generate an interesting logline & prompts", basically. The results were quite interesting, but style was a bit all over the place (which was kinda cool in some ways actually). Then, I refined the prompt it was using to create the content—attempting to focus on cinematic feeling, character consistency (age, hair, ethnicity, name), and visual style. The idea is to build it out so that it can (hopefully) stick to genre, director influence, and a cohesive color palette. That will take some time, though. The agent is fully autonomous. It: Writes a story/logline and then the corresponding prompts Generates video clips Downloads them Stitches them into a final video (Optional) Adds background music all in one shot (it just takes ~5-10 minutes, and generates 17 clips or so at this time - I was using 30 as well but shortened it to test). You can upload your own background music to merge seamlessly, too. I'm working on more integrations to refine the output even further. Right now, I want everyone to try it out, but you'll likely need to upload your own API keys (because I'm broke 😂). Still figuring out the best way to share it! I'll have to explore Replit or Gradio, but that will be a little bit either tonight or tomorrow. The final video below shows where it's at as of right now. And in the comments, I’ve included different outputs—some completely chaotic, others more polished after prompt tuning.

I've built an AI agent that generates a logline of its choosing, creates text-to-video clips via 'scenes' it prompts with Luma, and then stitches them together automatically—even adding background music if you happen to have some present! At first, I let the model run wild—no direction, just "generate an interesting logline & prompts", basically. The results were quite interesting, but style was a bit all over the place (which was kinda cool in some ways actually). Then, I refined the prompt it was using to create the content—attempting to focus on cinematic feeling, character consistency (age, hair, ethnicity, name), and visual style. The idea is to build it out so that it can (hopefully) stick to genre, director influence, and a cohesive color palette. That will take some time, though. The agent is fully autonomous. It: Writes a story/logline and then the corresponding prompts Generates video clips Downloads them Stitches them into a final video (Optional) Adds background music all in one shot (it just takes ~5-10 minutes, and generates 17 clips or so at this time - I was using 30 as well but shortened it to test). You can upload your own background music to merge seamlessly, too. I'm working on more integrations to refine the output even further. Right now, I want everyone to try it out, but you'll likely need to upload your own API keys (because I'm broke 😂). Still figuring out the best way to share it! I'll have to explore Replit or Gradio, but that will be a little bit either tonight or tomorrow. The final video below shows where it's at as of right now. And in the comments, I’ve included different outputs—some completely chaotic, others more polished after prompt tuning.

Kiri

69,476 просмотров • 1 год назад

💎 Obsidian set up tutorial 💎 Complete walk through from start to finish of how to recreate my obsidian vault + why I use Obsidian as well as useful tips for those just getting started. This took a fair bit of effort to make so if you found some value here please take the time to drop a like or repost to help this reach more people. 🤝 🚨 This is a scheduled post and I am not currently on this account. As part of my monk mode I am temporarily residing on a burner account to cut out noise so please understand I will not see or reply to any questions. If you are really stuck with something please DM and I will get back to you in ~3 weeks when I am back on this account LINK FOR BACKGROUND PLUGIN: FYI you can customise the background you with your own image and do not just have to use the default though I like it. How to do so can be found here:

💎 Obsidian set up tutorial 💎 Complete walk through from start to finish of how to recreate my obsidian vault + why I use Obsidian as well as useful tips for those just getting started. This took a fair bit of effort to make so if you found some value here please take the time to drop a like or repost to help this reach more people. 🤝 🚨 This is a scheduled post and I am not currently on this account. As part of my monk mode I am temporarily residing on a burner account to cut out noise so please understand I will not see or reply to any questions. If you are really stuck with something please DM and I will get back to you in ~3 weeks when I am back on this account LINK FOR BACKGROUND PLUGIN: FYI you can customise the background you with your own image and do not just have to use the default though I like it. How to do so can be found here:

Ace

14,895 просмотров • 1 год назад

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

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

There is a strategy for Claude Max users that will 3-5X productivity and vibe coding learning curve. Which most vibe coders don't utilize! Most people using Claude Code just sit and watch the terminal while their prompt cooks. That’s dead time. If you’re on Claude Max, you’re paying for parallel capacity you’re probably not using fully. And tokens get wasted. Here’s a methodology to fix that and boost the way you use Claude forever: The Setup & Workflow 1. Add the repos you’re actively working on to your workspace from your IDE 2. Click “new terminal” and open 3-4 terminal instances, each pointed at a different project 3. Toggle between them on the right side of your terminal panel 4. When one terminal is cooking a prompt, look at the others 5. Use the time Claude is working to prompt the next project 6. Continuously rotate and ship across 3-4 projects like this 7. Use your tokens effectively, build more, learn faster The Result You ship 3-4 projects simultaneously. You burn through your token allocation on actual output instead of letting it sit unused. You learn faster because you’re getting more reps in the same amount of time, too. As long as you work on different projects at the same time like this, it will only be a boost in productivity, with no chance for code to get spaghetti. In the video, you can see where to find add workspace, run new terminal, and change between terminals:

There is a strategy for Claude Max users that will 3-5X productivity and vibe coding learning curve. Which most vibe coders don't utilize! Most people using Claude Code just sit and watch the terminal while their prompt cooks. That’s dead time. If you’re on Claude Max, you’re paying for parallel capacity you’re probably not using fully. And tokens get wasted. Here’s a methodology to fix that and boost the way you use Claude forever: The Setup & Workflow 1. Add the repos you’re actively working on to your workspace from your IDE 2. Click “new terminal” and open 3-4 terminal instances, each pointed at a different project 3. Toggle between them on the right side of your terminal panel 4. When one terminal is cooking a prompt, look at the others 5. Use the time Claude is working to prompt the next project 6. Continuously rotate and ship across 3-4 projects like this 7. Use your tokens effectively, build more, learn faster The Result You ship 3-4 projects simultaneously. You burn through your token allocation on actual output instead of letting it sit unused. You learn faster because you’re getting more reps in the same amount of time, too. As long as you work on different projects at the same time like this, it will only be a boost in productivity, with no chance for code to get spaghetti. In the video, you can see where to find add workspace, run new terminal, and change between terminals:

Meta Alchemist

82,000 просмотров • 8 месяцев назад

The 15 rules of Filmmaking for comedy movies by Zucker, Abrahams and Zucker (ZAZ): "1. JOKE ON A JOKE: Two jokes at the same time cancel each other out. If the joke is in the background, the foreground action should be serious, and vice versa. Focus on one joke at a time. 2. ACKNOWLEDGEMENT: Sometimes referred to as “winking.” Don’t acknowledge the joke, or that you made a joke. Actors in the foreground must ignore jokes happening behind them. 3. MERELY CLEVER: A “clever” joke isn’t good enough. It has to get a laugh. 4. BREAKING THE FRAME: Don’t remind the audience they’re watching a movie. Jokes about the movie itself, the movie business, or comedy itself are a strict no-no, although it’s possible to sneak one in if you don’t dwell on it. See Rule #11: That didn’t happen. 5. TRIVIA: A joke using references so arcane that few people will ever get it. 6. JERRY LEWIS: A comedian who is doing every possible crazy thing he can to get a laugh. As a result, when something was over the top, we would just say, “Jerry Lewis.” 7. AXE GRINDING: When the joke is overshadowed by some message, it gets unfunny fast. 8. KNOCKING DOWN THE POSTS: Conceptual jokes are fine, but people don’t laugh at concepts; they laugh at verbal or visual punch lines. In 'Airplane!' (1980) the gag of the soldier leaning out the door as his girlfriend runs alongside is merely referencing the same scene we’ve seen in hundreds of films where it makes sense—or a train. Fortunately, we decided to put old-style railroad posts on the runway and have the girl knock them over. People clearly get the concept of the scene, but they don’t laugh until she knocks down the posts. 9. STRAW DUMMY: A hollow setup for a joke where the target has been invented by the writer. You can’t satirize something that doesn’t exist. Like a block-long, nuclear-powered bus. 10. CAN YOU LIVE WITH IT?: Once a joke is made, it can’t be allowed to hang around (Rule #14). Like a personalized license plate, how long can “LV2FART” be funny? 11. THAT DIDN’T HAPPEN: Something that totally defies all logic but is on and off the screen so fast that we get away with it. Robert Stack in 'Airplane!' yells, “They’re on instruments!” Cut to the cockpit—the actors are playing musical instruments. Seconds later, the saxophone and clarinets have disappeared. If it’s done right, no one in the audience will ask where the instruments went. 12. UNRELATED BACKGROUND: A joke happening in the background, though unacknowledged, still needs to be related in some way to the action in the foreground. This rule was put into effect after the release of Airplane!, when we desperately trying to figure out why no one laughed at the spear striking the wall behind Robert Stack and a watermelon crashing on the table behind Lloyd Bridges. It made us laugh so hard when we wrote it, filmed it, saw it in dailies, as well as the finished film. Unfortunately we were the only ones. It was craziness without an actual joke. We left it in, and probably in some way it adds to the irreverent tone of the film, but it never gets a laugh. 13. TECHNICAL PIZZAZZ: Special effects and big action don’t necessarily mean funny. 14. HANGING ON: Don’t play a joke too long. When it reaches its peak, get out. The film should move off a joke before the audience does. 15. THERE ARE NO RULES: We try to follow these rules as closely as possible, realizing that perhaps what is most important is knowing when to ignore them." ("Surely You Can't be Serious - The True Story of Airplane!", ZAZ interviewed by Will Harris, 2023) P.S: On this day, 46 years ago, "Airplane!" (1980) was released in the USA.

The 15 rules of Filmmaking for comedy movies by Zucker, Abrahams and Zucker (ZAZ): "1. JOKE ON A JOKE: Two jokes at the same time cancel each other out. If the joke is in the background, the foreground action should be serious, and vice versa. Focus on one joke at a time. 2. ACKNOWLEDGEMENT: Sometimes referred to as “winking.” Don’t acknowledge the joke, or that you made a joke. Actors in the foreground must ignore jokes happening behind them. 3. MERELY CLEVER: A “clever” joke isn’t good enough. It has to get a laugh. 4. BREAKING THE FRAME: Don’t remind the audience they’re watching a movie. Jokes about the movie itself, the movie business, or comedy itself are a strict no-no, although it’s possible to sneak one in if you don’t dwell on it. See Rule #11: That didn’t happen. 5. TRIVIA: A joke using references so arcane that few people will ever get it. 6. JERRY LEWIS: A comedian who is doing every possible crazy thing he can to get a laugh. As a result, when something was over the top, we would just say, “Jerry Lewis.” 7. AXE GRINDING: When the joke is overshadowed by some message, it gets unfunny fast. 8. KNOCKING DOWN THE POSTS: Conceptual jokes are fine, but people don’t laugh at concepts; they laugh at verbal or visual punch lines. In 'Airplane!' (1980) the gag of the soldier leaning out the door as his girlfriend runs alongside is merely referencing the same scene we’ve seen in hundreds of films where it makes sense—or a train. Fortunately, we decided to put old-style railroad posts on the runway and have the girl knock them over. People clearly get the concept of the scene, but they don’t laugh until she knocks down the posts. 9. STRAW DUMMY: A hollow setup for a joke where the target has been invented by the writer. You can’t satirize something that doesn’t exist. Like a block-long, nuclear-powered bus. 10. CAN YOU LIVE WITH IT?: Once a joke is made, it can’t be allowed to hang around (Rule #14). Like a personalized license plate, how long can “LV2FART” be funny? 11. THAT DIDN’T HAPPEN: Something that totally defies all logic but is on and off the screen so fast that we get away with it. Robert Stack in 'Airplane!' yells, “They’re on instruments!” Cut to the cockpit—the actors are playing musical instruments. Seconds later, the saxophone and clarinets have disappeared. If it’s done right, no one in the audience will ask where the instruments went. 12. UNRELATED BACKGROUND: A joke happening in the background, though unacknowledged, still needs to be related in some way to the action in the foreground. This rule was put into effect after the release of Airplane!, when we desperately trying to figure out why no one laughed at the spear striking the wall behind Robert Stack and a watermelon crashing on the table behind Lloyd Bridges. It made us laugh so hard when we wrote it, filmed it, saw it in dailies, as well as the finished film. Unfortunately we were the only ones. It was craziness without an actual joke. We left it in, and probably in some way it adds to the irreverent tone of the film, but it never gets a laugh. 13. TECHNICAL PIZZAZZ: Special effects and big action don’t necessarily mean funny. 14. HANGING ON: Don’t play a joke too long. When it reaches its peak, get out. The film should move off a joke before the audience does. 15. THERE ARE NO RULES: We try to follow these rules as closely as possible, realizing that perhaps what is most important is knowing when to ignore them." ("Surely You Can't be Serious - The True Story of Airplane!", ZAZ interviewed by Will Harris, 2023) P.S: On this day, 46 years ago, "Airplane!" (1980) was released in the USA.

DepressedBergman

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